Micro visualisations for spatial data: draw the geometry, not the number

A table of metres cannot say what a neighbourhood is shaped like. The k-ring that overshoots 400 m reaches furthest along six axes, so a shop 390 m away is inside or outside depending on its bearing. Inline SVG draws that at the size of the text, inside the sentence making the claim. Resolution 9 gives you for a 400 m walk, and resolution 11 gives you . Same dashed 400 m target, same 15 px, and only the second is the neighbourhood you asked for. Overshoot falls from 514% to nothing.

At 64 px there is room for the boundary. Real H3 disks at 51.48 degrees north, each scaled to its own footprint:

Res	Footprint	Reach	Overshoot	Cells
7		2,457 m	+514%	7
8		922 m	+130%	7
9		702 m	+75%	19
10		527 m	+32%	61
11		401 m	+0%	217
12		414 m	+3%	1,519

Read the dashed circle, not the outline. At resolution 7 the target is a speck inside the one cell you were given. By 11 it nearly fills a footprint that has stopped being a hexagon, which is what 217 cells bought.

Each is under a kilobyte, needs no charting library, and has fixed width and height, so it cannot shift the layout. currentColor serves both themes from one file. Best of all, the script that computes the table emits the glyphs, so the picture cannot drift from the numbers beside it.

A figure does not have to be a page wide to be a figure.