-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show time slice when (only?) map is displayed #817
Comments
I believe this is currently being worked on by Ian Johnson |
I've started mocking a solution for this issue in this notebook: I hope I captured the problem and illustrated a reasonable direction to go in. I'll continue to add to the notebook with prototypes that can be reviewed before I jump into the codebase. |
I've put in a bit of work prototyping Kent's ideas, they aren't fully realized yet but some progress. You can see what the streamgraphs look like with real data, and the challenge we will face doing tooltips for divisions. You can interact with them in the notebook. |
So @kenthuth and I have made some iterations on the prototype and I think it's time to start on a branch in auspice. We'd like to invite some feedback on what we have, and think that further considerations will be easier to make once we can see the legend in use (i.e. in a narrative, or in the main app with data filtered) We are thinking that this stacked histogram: And that tooltips are aggregated to Regions if the histogram is showing location data (such as Division or Country): |
Amazing. Will look at this today 😄 |
The map was implicitly designed to be shown next to a tree. Thus when animating, you see the selected time slice moving though the tree & have a feeling for how time is progressing.
Now it's becoming common to display the map by itself, both while interacting with normal auspice and especially while in narrative mode. There should be some sort of visual indication of the currently selected time period during an animation (and perhaps outside of an animation also? To explore).
The text was updated successfully, but these errors were encountered: