Columbus radius map: 5, 10, 25 and 50 mile circles

If you want one landmark to calibrate against, use Upper Arlington. It’s 4.1 mi north-west of the centre, so it sits almost exactly on the inner circle. At the other end, Marion is 43.9 mi out to the north, near enough the edge of the 50 mi ring. Everything in between scales from those two.

Read the distances as point to point. GeoNames gives every settlement one coordinate, roughly central, and these figures are the gaps between those coordinates. A sprawling suburb whose centre lands at 10 mi might well start at half that. Where the boundary actually matters, draw the circle and look at where the line crosses.

Place names, coordinates and populations come from GeoNames, which the site uses under CC BY 4.0.

Here’s the thing people get wrong about a radius. Double it and you quadruple the ground underneath. Going from 5 miles to 50 multiplies the area by a hundred, so 79 mi² becomes 7,854 mi². The outermost band on its own, the gap between the 25 and 50 mi circles, accounts for 5,890 mi². Three quarters of everything inside the big circle, in one band.

Cross the two tables and something useful falls out. The 25 mi disc holds 1,268,028 listed people across 1,963 mi², about 646 per mi². Push out to 50 and you buy 5,890 mi² more for only 245,081 extra people. Most of that last band is empty, which is what you’d expect and still surprises people when they see it drawn.

Every circle here is a straight-line radius, measured crow-flies. Marion shows up at 43.9 mi north, and the road out there will be longer. Always is. In a town laid out on a grid, reckon on 20 to 40 per cent more actual travel than the radius says. Put a river, a harbour or a decent hill in the way and that rule of thumb stops meaning much at all.

If travel time is genuinely what you need, use these rings to narrow the field first and check the survivors properly afterwards. The circle is cheap, instant, and honest about what it measures. It also can’t tell you that the 10 mi to the north crosses water while the same 10 mi to the south is dual carriageway the whole way.

Where it all comes from. Names, coordinates and populations are GeoNames cities15000, which covers settlements of roughly 15,000 people and up. Anything smaller is simply absent. City subdivisions get stripped out on purpose, so a page about Columbus doesn’t fill with its own neighbourhoods instead of its neighbours. Distances are haversine on a 6,371.0088 km sphere, areas are spherical caps.

All of it was computed when the site was built, then written into a file that ships with the page. Nothing here is fetched while you read. That’s why the tables are in the HTML the server sends rather than appearing a second later, and it’s why the figures can’t drift: rerun the build and every number on all fifty of these pages is recalculated from the same dump.

Most of the traffic to a page like this is practical. Somebody wants to know which towns near Columbus fall inside a service area, or how many people live within 25 miles of a site they’re weighing up. The table answers the first one outright. For the second, take the ring populations as a floor, since everything under 15,000 people is missing from them.