JaredHawkins
commented
9 years ago User problem We have a large database of geotagged tweets (approaching 6 billion). We want to be able to efficiently search tweets based on time/location/text and display this in a user-friendly and interactive visualization. Ideally, we also want to be able to automatically detect clusters of tweets in space/time.
Use cases
- Public health: Identifying outbreaks and tracking their spread, in close to real-time (this is my interest, and the inspiration for this project!). more to come
Functionality (note: ranked with a score from 1-6, with 1 - very important and main functionality and 6 - nice thing to have).
- 3 - I would like to be able to visualize tweet text (presumably a small random subset of tweets). This should be presented in a clean UI.
- 1 - I would like to track tweets geo-temporally, with the goal of being able to visualize the construction of a network over time. One example would be tweets marked by GPS pins, with an network connecting them (perhaps using an animation?).
- 2 - It would be great to automatically detect (and visualize) clusters, as defined by a close proximity in space and/or time (parameters set by user).
- 4 - Population density differs widely across different regions. It would be great to normalize aggregated results (e.g., a heat map) based on known population values (for example, in the US this could be done with census data).
anvk
I think this project is missing a Project Scope. Before jumping into actual development or designs or UI it would be great to outline main functionality we are trying to achieve here. We need to highlight main functionality and think of the ways how they would help to resolve "real-life problems" for users who will be using TweetGeoViz
Jared is it possible for you to formulate and to write down user problems and use cases for TweetGeoViz. What exactly this project is help to resolve? How it can be helpful to others? What examples and use cases for the project you foresee?
After you have user problems, could you to think of the main functionality points of the App and listed them here. Also rank them from 1 to 6 from (1 - very important and main functionality and 6 - nice thing to have).
Once we have this preliminary set we can discuss it during our next online meetup and try to figure out the first milestone with its features. This will spec out what EXACTLY we are trying to build and what UI, tools, components and modules we need to build.