← All articles

By ·

Drive-Time vs Radius Trade Areas: Why Your 3-Mile Ring Misleads You

Drive time vs radius trade area: across 169 Calgary sites, a 3-mile ring missed a 10-minute drive's population by over 25% at 42% of them.

Aerial view of a multi-level highway interchange in a dense city
Photo: Denys Nevozhai on Unsplash

A drive-time trade area counts the people who can reach a site within a set number of minutes on the road network. A radius counts everyone within a straight-line distance. Across 169 Calgary sites, a 3-mile ring and a 10-minute drive enclosed similar land, but their population counts differed by more than 25% at 42% of sites.

This article covers that comparison in full, why the ring goes wrong, when a ring is still the right tool, where to get isochrones, how traffic changes the answer, and how to count people inside a polygon using US and Canadian census units.

Drive time vs radius trade area: what is the difference?

A radius trade area (or ring) is a circle of fixed distance around a site, such as 1, 3 or 5 miles. It is simple, cheap and easy to explain to a real estate committee.

A drive-time trade area (an isochrone, or a service area in Esri's terminology) is the set of places from which a driver can reach the site within a fixed time, such as 10 minutes, travelling along the road network at modelled speeds.

The difference is that a ring ignores everything that shapes how people actually arrive:

For a site that will cost real money, the question is how much these effects change the answer. The rest of this article measures it.

How different are a 3-mile ring and a 10-minute drive in practice?

I tested this on Calgary, using the same data behind the Site Selection Showdown game on this site.

The data and method

Matching the reach fairly

Comparing a ring with a drive time is only fair if the two cover a similar amount of ground. Across the 169 sites, the median free-flow catchment was:

Drive timeMedian catchment areaMedian population reached
8 minutes35.3 km²80,850
9 minutes48.7 km²116,491
10 minutes65.6 km²161,865
11 minutes86.9 km²208,490
12 minutes110.1 km²265,219

A 3-mile ring (73.2 km²) sits between the 10- and 11-minute catchments, so the comparison below pairs a 3-mile ring with a 10-minute drive. In Calgary at free-flow speeds they are about the same size.

Results across 169 sites

MeasureResult
Median ratio, ring population ÷ drive-time population1.01 (they agree on average)
Middle 80% of sites0.76 to 2.17
Sites where the two counts differ by more than 25%42%
Sites where they agree within 10%24%
Sites where the ring overstates by more than 25%33%
Sites where the ring understates by more than 25%9%
Median share of the ring's people who are more than 10 minutes away19%
Median share of the drive-time's people who are outside the ring15%
Rank correlation between the two (Spearman)0.78
Sites shared by the top 10 under each method4 of 10

The headline is not that rings are biased. On average they land close. The problem is that the error is large and unpredictable for any single site, and site selection is always about a single site.

The ranking result matters most. If you shortlisted the top 10 Calgary sites by 3-mile ring population, only 4 of them would also be in the top 10 by 10-minute drive-time population. The single best site by drive time, on 16 Avenue NE (the Trans-Canada Highway) in the inner northeast, ranks 72nd of 169 by ring population. It reaches 307,647 people in 10 minutes, but only 175,863 live within 3 miles of it. The freeway carries its catchment well past the ring.

Six example sites

These are the buildable hexagons nearest to six well-known Calgary locations. Population is counted inside city limits only.

Site3-mile ring10-minute driveIn bothRing onlyDrive onlyRing ÷ drive
Downtown core221,230279,477218,1903,04061,2870.79
Chinook Centre168,260237,115160,5707,69076,5450.71
Sunridge (northeast)191,725210,737177,34014,38533,3970.91
Southcentre150,467153,185122,42828,03930,7570.98
Crowfoot (northwest)166,853156,447124,46842,38531,9791.07
Market Mall (northwest)170,436119,460101,72468,71217,7361.43

Three patterns show up:

  1. Arterial sites are undercounted by rings. Chinook Centre sits on Macleod Trail near Glenmore Trail. The ring misses 76,545 people who can drive there in 10 minutes, a third of the true catchment.
  2. Sites hemmed in by barriers are overcounted. At Market Mall the ring includes 68,712 people, mostly south of the mall, who cannot reach it within 10 minutes. The ring overstates the market by 43%.
  3. Matching totals can hide a different market. Southcentre's ring and drive time differ by less than 2% in total population, which looks like agreement. But 58,796 people are in one area and not the other, 38% of the drive-time population. At Crowfoot the totals are within 7% and 74,364 people differ. If you then profile income, age or household size, you are describing partly the wrong neighbourhoods.

Two Calgary maps comparing a 3-mile ring with a 10-minute drive. At Chinook Centre the ring holds 168,260 people and the drive 237,115, missing people along the arterials. At Market Mall the ring holds 170,436 and the drive 119,460, overcounting people to the south who cannot reach it in 10 minutes

Chinook Centre and Market Mall: green is in both areas, orange only in the ring, blue only in the drive time.

Is it just the ring's size?

To check whether a better-sized ring would fix this, I drew a second ring at every site with exactly the same area as that site's own 10-minute catchment. This removes size from the comparison and leaves only shape.

Measure (ring sized to each site's own catchment)Result
Median ratio, ring ÷ drive-time population0.92
Sites off by more than 25%6.5%
Median share of people in one area but not the other, relative to the drive-time population33%
Sites where that mismatch exceeds 20%80%

A perfectly sized ring fixes the totals at most sites. It does not fix the people. At four out of five sites, more than a fifth of the population is still on the wrong side of the line. You can only size a ring this way after computing the drive time anyway, so in practice there is no shortcut.

When is a radius trade area good enough?

Rings are not wrong everywhere. They are the right choice when:

Use drive time when the decision commits capital to a specific site, when the site sits near a freeway, river, rail line or large park, or when you will profile the people inside the area and not just count them.

Where do drive-time isochrones come from?

Four common sources, with what each actually does:

SourceIsochrone supportTrafficNotes
OSRMNo isochrone endpoint. Services are route, nearest, table, match, trip and tile.Free-flow speeds from the routing profile, unless you load your own segment speed filesFast and open source. Build catchments from the table service or a precomputed grid, as in the Calgary test.
ValhallaNative isochrone endpoint. Contour times in minutes, up to four contours by default.Accepts a date_time for a departure or arrival timeOpen source, OpenStreetMap based. Check what speed data your routing tiles were built with before reading anything into time of day.
Esri ArcGIS Network AnalystService area analysisTime of day and date are used for traffic when the network dataset or service includes traffic dataCommercial. Esri's Business Analyst extension adds a Huff model tool on the same platform.
HERE Isoline Routing API v8Native isolines by time or distancedepartureTime sets the start time. departureTime=any ignores traffic.Commercial. Useful when you need traffic-aware catchments by hour.

Whichever you use, write down the engine, the date of the road data, the speed assumptions and the time of day in the report. Two analysts using different engines will draw different polygons for the same site, and the committee should know which one it is looking at.

Should you use rush-hour or free-flow drive times?

Free-flow catchments are the largest a site will ever have. They flatter every location, and they flatter freeway sites most because freeways gain the most speed when traffic is light.

The Calgary numbers above are free-flow. That is a fair basis for comparing a ring with a drive time, because both are idealised. It is not a fair basis for forecasting sales at a site whose customers arrive at 5:30 pm on a weekday.

A practical rule:

  1. Pick the hour that matters. Grocery and big-box peak on weekends. Quick-service dinner trade is weekday evening. Childcare and schools are weekday morning drop-off.
  2. Compute the catchment at that hour with a traffic-aware engine, using historical traffic for a typical week, not live traffic on the day you ran it.
  3. Keep a free-flow version as the upper bound, and report both. The gap between them is itself useful: a site whose catchment collapses at peak is more exposed to congestion than one that barely changes.

Drive-time catchments are also used for public services. The same method, solved for coverage, is how fire station location analysis is done.

How do you count population inside a trade area in the US and Canada?

The polygon is only half the job. You then need people, households and spending inside it, which means overlaying it on census units.

United StatesCanada
Distance unit in reportsMilesKilometres
Main small-area unitBlock groupDissemination area (DA)
Typical sizeAbout 600 to 3,000 peopleAverage of 400 to 700 people
Detailed demographics fromAmerican Community Survey 5-year estimates. Block groups are the smallest published ACS geography, for select tables.Census of Population. The DA is the smallest standard area for which all census data are disseminated.
Postal geographyZIP Code Tabulation Areas, built from census blocks to approximate ZIP codesCensus forward sortation areas, the first three characters of the postal code

Apportioning units the boundary cuts

A drive-time polygon will slice through block groups and DAs. There are three ways to handle the cut units, in increasing order of accuracy:

  1. Centroid rule. Include a unit if its centre is inside. Fast, but can swing totals by thousands at the edge.
  2. Area weighting. Include the share of the unit's population equal to the share of its area inside the polygon. This assumes people are spread evenly, which is false wherever a unit contains a park, an industrial strip or undeveloped land, which describes most suburban edge units.
  3. Dasymetric weighting. Spread each unit's population over its residential land or building footprints first, then intersect. This is the method to use when a few thousand people decide the answer.

DA counts come from the census of the reference year, so in fast-growing suburbs check building permits or newer population estimates before trusting them. ACS block group figures are five-year estimates with margins of error, and those margins matter when a trade area contains only a handful of block groups.

What are the limitations of this comparison?

What should you do with this?

If you are comparing sites for a lease or a franchise rollout, run drive times at the hour your customers travel on every shortlisted site, keep rings only where a contract or benchmark needs them, and profile the people inside the drive-time polygon, not the ring. When ring and drive time disagree by more than about a quarter, find out why on the map before the committee meeting, because someone will ask.

If you need drive-time trade areas built for your candidate sites, scoped or done, email me at mahad.imran29@gmail.com.

Frequently asked questions

Is a 3-mile radius the same as a 10-minute drive?

In area, roughly. A 3-mile ring covers 73 square kilometres, and in Calgary the median 10-minute free-flow drive catchment covered 66. In population, often not. Across 169 Calgary sites the two counts differed by more than 25% at 42% of sites, and even when the totals matched, about a third of the people inside one boundary were outside the other.

When should I use a radius instead of a drive-time trade area?

Use a ring when the question is legal or contractual (a lease radius clause or a protected territory written in miles), when you are screening hundreds of sites for a first cut, when customers walk in a dense grid, or when you must compare against a benchmark report that was built on rings. Use drive time for any decision that commits capital to one specific site.

What is the best free tool for drive-time isochrones?

Valhalla is the most direct open-source option because it has a native isochrone endpoint that takes contour times in minutes. OSRM is fast and widely used but has no isochrone endpoint, so you build catchments from its table service or a precomputed grid. Both run on OpenStreetMap and assume free-flow speeds unless you supply traffic data.

Should trade areas use rush-hour or free-flow drive times?

Use the time of day your customers actually travel. A grocery store's busiest trips are not a commuter's, and a quick-service dinner trade area is shaped by weekday evening traffic. Free-flow catchments are the largest they will ever be, so they flatter every site. If your routing source only offers free-flow, say so in the report and treat the catchment as an upper bound.

How do I count population inside a drive-time polygon?

Overlay the polygon on census units, US block groups from the American Community Survey or Canadian dissemination areas from Statistics Canada, and apportion units the boundary cuts. Simple area weighting assumes people are spread evenly, which is rarely true at the suburban edge, so weight by residential land, building footprints or smaller census blocks where you can.

Let's talk.

Best way to reach me is email. I respond to most things.