I think the issue here is the default plot bin width -- I'll pass it along to the team working on Plot! At the size below, the rects are invisible... observablehq.com/d/6a6eda0758fd402b

Ok, thanx

Still an open issue: https://github.com/observablehq/plot/issues/417

Got it. Thanks for the reference to the issue

This was an interesting one! I am placing a tick at the minimum of the *data*, which isn't necessarily the minimum of the bins. Again, I'll reach out to the team for some guidance.

Ok, great!

Fixed! I was wrong about the issue here! In case you're interested, my code used d3.min(data, d => +d[column]), and the "+" was converting null values to a 0 (expanding the range to include 0!).

I see! It looks like there is still something weird in min ticks for the `lat` and `long` histogram

Or maybe not. Aren't min ticks supposed to start from the very beginning of the x-axis?

Yea -- strange... long looks ok, but lat has a min that is below everything else. Let me change that calculation....

Same issue! This is interesting -- I didn't know that the plus sign in this code: `d3.mean(data, d => +d[col])` would convert null to 0 (hence the mean being so low!). Again, *really* appreciate the feedback, I learned something and helped make this work better!

It's anything, really, I'm glad if this helps! Just a side note for more polish: some min/max ticks (e.g., 37 and 7 of lat and long) seem still slightly shifted respect to the start / end of the x axis. At least, it happens here on Chrome for MacOS. E.g,. see 37 of the lat histogram this is shifted: <g class="tick" opacity="1" transform="translate(22.55289755102042,0)"><line stroke="currentColor" y2="6"></line><text fill="currentColor" y="9" dy="0.71em">37</text></g> this instead would be centered on the start of x-axis <g class="tick" opacity="1" transform="translate(20.0,0)"><line stroke="currentColor" y2="6"></line><text fill="currentColor" y="9" dy="0.71em">37</text></g>

Interesting! Thanks for the attention to detail -- looking into it!