-
Notifications
You must be signed in to change notification settings - Fork 2
UI: spatially binned heatmap for messages too #144
Comments
This was requested to me too. People wanted to know the density of message activity. |
(though they did not always understand the term "binned heatmap") |
@zachmullen suggested just calling it a heatmap without the word binned (I On Tue, Jun 30, 2015 at 9:45 AM, Jamie Snape [email protected]
David Manthey |
I was thinking that too. The UI element with number of bins should only activated be activated when heat map is selected to maintain the associate with the heat map. That UI element should always have a value in it so people know what the default is. Also, I would suggest "heat map" rather than "heatmap". |
Again we have an issue where I think we need to disambiguate (in the display options) what data set we are working on, especially if both datasets can be viewed as heatmaps, which we obviously don't want to do simultaneously. Just like with the filtering, I think we may need separate display options UIs for taxi vs. message data. |
I updated the app so that the number of bins is a slider, and you no longer On Tue, Jun 30, 2015 at 9:54 AM, Jamie Snape [email protected]
David Manthey |
That is good. Is the slider enabled when heat map is not selected? |
No. If you are on the VPN, you can see the change on the XDATA instance. On Tue, Jun 30, 2015 at 10:00 AM, Jamie Snape [email protected]
David Manthey |
Will check it out. |
Two users asked specifically for a heat map of the messages. Knowing the density of messages was an important use case for them. |
We have it for taxis currently, but not for messages.
The text was updated successfully, but these errors were encountered: