Population within a drive time and within a radius, worked out step by step
The same site can have very different populations around it depending on the shape you draw. A step-by-step calculation showing where the two counts part and which to trust.
Part of the guide Location intelligence automation
The population within a drive time and the population within a radius are both sums of the same small grid cells; they differ only in which cells each shape takes in. A circle takes every cell within a set distance, whatever lies between. A drive-time area takes the cells a car can reach in the time, so it drops cells behind rivers, rail yards and dead ends and reaches further along fast roads. Work out both, then look at the cells one has and the other does not: that difference, not the two totals, tells you which number to use.
This walk-through is for analysts, planners and anyone who has been asked why two reports gave two populations for the same site. It shows how the counts are built, a full worked example with the arithmetic, how to compare shapes of different sizes fairly, and how to produce both numbers with one flow.
How a population count around a site is built
xMap's population grid splits the land into small hexagons of about 0.1 square kilometres, each holding an estimate of its residents, split into men and women and nine age groups. A count around a site is the sum of the hexagons that fall inside the shape. Demographics does this for a circle around each place (from 500 m to 8 km) or for any area handed to it, and also returns the area in square kilometres and the people per square kilometre, so two shapes of different size can be compared.
A drive-time area comes from Travel area, which follows the road network to draw what a car, a bike or a walker can reach, up to 15 minutes or 10 km by road for now. Put Demographics after it and the count is taken over that shape instead of a circle.
A worked example in Pune
The figures in this example are made up, to show the arithmetic. A diagnostics company is weighing a collection centre in Pune and wants the residents its patients would come from. It asks for two things: everyone within 3 km, and everyone within a 15-minute drive.
- The circle. A 3 km radius covers 3.14 x 3 x 3, about 28.3 square kilometres. Say the hexagons inside it sum to 412,000 residents, or about 14,600 per square kilometre.
- The drive-time area. The 15-minute drive area comes out at, say, 24.0 square kilometres, stretched along two main roads and cut short by a river to the west. Its hexagons sum to 296,000 residents, about 12,300 per square kilometre.
- The overlap. Say 18.5 square kilometres lie in both shapes, holding 251,000 residents.
- Circle only. 412,000 minus 251,000 leaves 161,000 residents inside 3 km but beyond a 15-minute drive: most of them across the river, where the nearest bridge is a long way round.
- Drive area only. 296,000 minus 251,000 leaves 45,000 residents beyond 3 km but within 15 minutes, out along the main roads.
- The verdict. The circle overstates the reachable population by 116,000 people, the difference between the two totals, but the real story is bigger: 161,000 people counted by the circle cannot easily reach the site, and 45,000 who can are missing from it.
| Shape | Area | Residents | Per square km |
|---|---|---|---|
| 3 km circle | 28.3 km2 | 412,000 | 14,600 |
| 15-minute drive | 24.0 km2 | 296,000 | 12,300 |
| In both | 18.5 km2 | 251,000 | 13,600 |
Made-up figures for one site; the areas follow from the shapes, the residents are invented to show the method.
Comparing shapes of different sizes
Two totals from two shapes of different size are not directly comparable. A fair check is the equal-area radius: the circle with the same area as the drive-time area. For 24.0 square kilometres that is the square root of 24.0 divided by 3.14, about 2.76 km. If a 2.76 km circle holds roughly the same residents as the drive area, geography is not doing much at this site and either shape will do. If the numbers part, as they do in Pune, the barriers and fast roads matter and the drive area is the one to trust.
Density is the other check. When the circle's people per square kilometre is much higher than the drive area's, the circle has reached into a dense district the roads do not connect well, which is exactly the kind of area a planner should look at on the map before signing anything.
When the radius is still the better number
- Walking trade in a dense grid. Where streets connect evenly in every direction, a short circle and a short walk cover much the same people, and the circle is quicker to explain.
- Comparing hundreds of sites. One radius applied everywhere is consistent and cheap to reason about. Switch to drive areas for the shortlist.
- When the area is an estimate. If the routing could not be drawn, Travel area falls back to a circle at a typical speed and says so. Then the two numbers are the same by construction, and the step tells you.
Producing both numbers with an AI employee
One flow can give every candidate site both counts side by side, so nobody has to explain two reports again.
- My data: the candidate sites, one row each.
- Demographics: residents within 3 km of each site, totals for each.
- Travel area: 15 minutes by car around each site, from the same rows.
- A second Demographics after it: totals for each drive-time area.
- xMap LLM, on the whole list: put the two counts side by side, work out the gap and the equal-area radius, and flag sites where they differ by more than a fifth.
- Email the table to the team.
What lands in the inbox is one row per site with both populations, both densities and a line on which to use. Templates to start from: who my warehouse reaches in 15 minutes, who lives around new places and where to open a nursery.
Questions
Why is the drive-time population sometimes larger than the radius population?
Because fast roads let a car reach beyond the radius in the same time. Where a ring road or motorway leaves near the site, the drive area can stretch well past the circle.
How accurate is each hexagon's population?
Each is a modelled estimate, good for comparing areas and sites, not for counting a single street. Sums over many hexagons are steadier than any one of them.
Can I do this for walking or cycling too?
Yes. Travel area draws walking and cycling areas the same way, and Demographics counts the residents inside them.
What is the largest drive time I can use?
Up to 15 minutes, or 10 km by road, for now. For a larger catchment, use a Demographics circle of up to 8 km and say it is a circle.
Templates that do this
Read next
More on population and demographics · Every article · Templates