You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is "2" grey or light blue? Totally ambiguous. They need to move the labels to the middle of the corresponding color swatch. Ironically the Trump administration map, which the article so painstakingly picked apart, made it much clearer what each color means.
But I realized that, while we make discrete colorbars for contour maps (though in that case you really do want to place the label the boundary, and that's what we do), we actually don't have this ability with heatmaps and choropleths, we can only do continuous gradations for these types. We should support that, and perhaps even default to it when the data values are discrete like this.
The text was updated successfully, but these errors were encountered:
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson
I was reading https://www.vox.com/policy-and-politics/2017/6/13/15792276/trump-obamacare-map and got annoyed by the colorbar:
Is "2" grey or light blue? Totally ambiguous. They need to move the labels to the middle of the corresponding color swatch. Ironically the Trump administration map, which the article so painstakingly picked apart, made it much clearer what each color means.
But I realized that, while we make discrete colorbars for contour maps (though in that case you really do want to place the label the boundary, and that's what we do), we actually don't have this ability with heatmaps and choropleths, we can only do continuous gradations for these types. We should support that, and perhaps even default to it when the data values are discrete like this.
The text was updated successfully, but these errors were encountered: