display data range for histogram hover text
See original GitHub issueIn this histogram, my data is binned by month. However, when I hover over a bar, I see the midpoint of the data. I wasn’t sure whether to interpret this as the midpoint of the histogram bar or the start of the histogram bar. I would prefer if this was more explicit and said: October 1-September 1
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Hover text and formatting in Python - Plotly
Over 17 examples of Hover Text and Formatting including changing color, size, log axes, and more in Python.
Read more >Histogram with tooltips and bars highlighted on mouse over
The following blocks are an edit of Jianan Li's "Basic tooltip" ; bins = d3.histogram() .domain(x.domain()) ;.thresholds(x.ticks(40)). (data).
Read more >Histogram with tooltip in d3.js
This post shows how to use d3.js to create an histogram with tooltips. It provides explanations and reproducible code. Example with code (d3.js...
Read more >Histogram | Charts - Google Developers
A histogram is a chart that groups numeric data into bins, displaying the bins as segmented columns. They're used to depict the distribution...
Read more >How to add hovering annotations to a plot - Stack Overflow
from matplotlib.pyplot import figure, show import numpy as npy from ... lambda event: hover(event, line_info)) # Your data values to plot x1 =...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I agree here. Although showing the data range might very useful, making this the default hover behavior is bound to confuse users. Showing the bin range feels less confusing to me.
I agree. It feels acceptable for the first cut. But we should start thinking about those future attributes now. I’m thinking of putting them in the
xbins
/ybins
containers:I prefer
0 - 0.99
as long as we use unicode minuses (not simple-
dash) to show negative numbers.closed by #2113