Isochrone Maps Explained: What They Are and Why They Beat Radii

The word "isochrone" comes from the Greek isos (equal) and chronos (time). An isochrone map draws the line of equal travel time — everything inside the boundary is reachable; everything outside is not. It sounds simple, and it is, which is why the concept has survived unchanged since the 19th century while the tools for computing it have gotten dramatically better.

The geometry problem with circles

The radius circle — a fixed distance from a center point, drawn with a compass — was the default tool for geographic market analysis for decades, and it remains the default in most spreadsheet-based site evaluation. Its appeal is simplicity: one number (miles), one shape (circle), immediate calculation.

The problem is that people don't travel in circles. They travel on roads. And roads are not uniformly distributed, uniformly fast, or uniformly connected to every point within a given distance. A river with one bridge concentrates all traffic through that crossing. A highway on-ramp pushes access far in one direction. A grid of suburban arterials allows faster lateral movement than radial roads through a dense urban core.

The result is that a circle over-counts population in some directions (where barriers or slow roads exist) and under-counts in others (where fast roads extend reach). For categories where every 10,000 people in the trade area matter — QSR revenue models, franchise disclosure documents, site underwriting for private equity — the error compounds.

How isochrones are calculated

Modern isochrone calculation runs on a road network graph. Each road segment is a node in the graph, weighted by travel time (length ÷ speed limit, adjusted for turn costs and intersection delay). Starting from the origin point, a routing engine expands outward in all directions simultaneously — a process called Dijkstra's algorithm or one of its variants — consuming the time budget as it traverses each segment.

When the time budget is exhausted, the engine has a set of road segments it fully reached and a set it partially reached. The boundary of the reachable territory — the isochrone — is traced by connecting the frontier points into a polygon. The result is a shape that follows roads where roads exist and fills in open land where the density allows.

The quality of the result depends heavily on the road data. Networks built on OpenStreetMap data (the most common choice for non-commercial tools) are accurate in urban areas but can miss private roads, newly built subdivisions, or gated communities. Commercial road data from providers like HERE or TomTom adds speed profiles derived from GPS traces, enabling time-of-day traffic modeling.

Drive, walk, and bike modes

Each travel mode uses a different sub-graph of the road network and different speed assumptions. Drive mode uses the full network weighted by speed limits and turn restrictions. Walk mode removes highways and uses a uniform pedestrian speed (typically 5 km/h average). Bike mode uses bike paths and lower-speed roads at a cycling average (around 15 km/h).

The shape differences between modes are dramatic. A 15-minute drive isochrone from a suburban US address might cover 40–80 km². A 15-minute walk from the same point covers 2–4 km² — roughly 20× smaller. In dense urban grids, the walk isochrone expands more evenly than the drive isochrone, which tends to shoot out along arterials.

Reading an isochrone correctly

Three things to look for when you see an isochrone for the first time:

• Fingers and protrusions. The polygon will extend further in the direction of major roads and highways. These fingers are real — they mean your location can reach those corridors efficiently. A finger extending 3 km down a highway is not an artifact; it's a signal that customers along that corridor are within your practical catchment.
• Flat edges and compression. Where the polygon boundary runs straight or compresses unexpectedly, look for the cause: a river without a nearby bridge, a highway with few exits, a railroad or industrial zone with no through roads. These are real barriers your customers face.
• Asymmetry. Very few isochrones are symmetric. A downtown site will typically reach much farther in the direction of the freeway on-ramp than toward a dense pedestrian grid. This asymmetry tells you something about where your customers will come from — and where your signage should be oriented.

Isochrones vs. radii: when does it matter most?

The gap between a radius and an isochrone is smallest in cities with uniform, flat road grids (Phoenix, Las Vegas, parts of Houston) and largest in cities with rivers, harbors, hills, or highway monocultures (San Francisco, Boston, Pittsburgh, Nashville). In the first group, the radius error might be 10–15%. In the second, it can exceed 50%.

For decisions where the error is smaller than your uncertainty about other inputs — rough market sizing, casual feasibility screening — a radius is probably acceptable. For decisions where precision matters — franchise territory protection, lease negotiation, cannibalization modeling, investor underwriting — the difference between a radius and a real isochrone can be the difference between a profitable site and an unprofitable one.

· · ·