FlowsBook a callSign inCreate free accountSign up
Population and demographics

Population data for bus stop planning: who lives within a short walk

Compare candidate bus stops by the residents who can walk to each in five or ten minutes, with children and people over 60 counted apart, and overlaps caught.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

Good population data for bus stop planning answers one thing for every candidate stop: how many people live within a walk they will actually make, and who they are. Draw the area reachable on foot in five or ten minutes from each candidate, count the residents inside it by age, and compare the candidates on the same terms. A stop that reaches 3,000 people beats one that reaches 900, and a stop that reaches many people over 60 may deserve a shelter and a bench before the others.

This is written for transport planners at cities and operators, consultants preparing a route study, and community groups making the case for a new stop. It walks through why a walk beats a circle, how to set the counts up, how to deal with stops that share the same residents, and what population figures cannot tell a planner.

Why a walk, not a circle

A 400 metre circle around a stop is the usual shortcut, and it is wrong in the places that matter most. A rail line, a motorway or a river can put half the circle out of reach; a stop at the end of a cul-de-sac reaches far less than its circle suggests. Travel area draws the area reachable by following the streets on foot, for a travel time (such as 5 or 10 minutes) or a distance by road. On the current plan it reaches up to 15 minutes or 10 km.

Where the routing service cannot draw an area, the block falls back to a circle at a typical walking speed and says it is an estimate. Note those stops when you present the results.

Counting residents for each candidate

  1. List the candidate stops in a table with their positions and upload it to My data.
  2. Read the table with the My data block.
  3. Add Travel area: Walking, A travel time, 5 minutes for a frequent urban route, 10 for a less frequent one. One area is drawn per stop, up to 25 a run.
  4. Add Demographics after it, set to look in the Area of interest, with Totals for each area. Each stop comes back with its residents, children 0 to 19, seniors 60 and over, their shares and people per km².
  5. Sort the stops by residents with Sort and limit, and keep the table for the study.

Reading the comparison

Say a city is choosing between three stop positions on a new route through part of Montreal. The figures below are made up to show how to read the table, not real counts.

CandidateResidents within 5 min walkChildren 0 to 19Seniors 60+
A, by the school2,90026%11%
B, at the junction3,40015%19%
C, by the retirement flats1,6008%41%

A made-up example of three candidate stops, to show how the figures are compared.

B reaches the most people overall. A reaches the most children, which matters for school journeys. C reaches the fewest, but two in five are over 60, the group for whom an extra 300 metres of walking is the difference between taking the bus and not. A planner might keep B, move A closer to the school gate, and argue for C on access rather than numbers.

Stops that share the same residents

Two candidates 300 metres apart will often count the same streets twice. Adding their totals overstates the people the route serves. Two ways to handle it:

  • Compare candidates as alternatives (A or B), never as a sum, when their walk areas overlap.
  • For a whole route, set Demographics to give back every hexagon of about 0.1 km² and remove duplicate hexagons before adding up. Each resident is then counted once, for the route as a whole.

Where the data stops

Residents are only half of a stop's riders. Workers, students and shoppers arrive from elsewhere. For stops near offices, campuses or shopping streets, add what is around each stop with Nearby places (schools, clinics, supermarkets, offices), and treat the resident count as the floor of demand, not all of it.

Keeping the study current

New housing changes a stop's catchment faster than anything else. Running the same flow on a yearly Schedule, with an email to the planning team, keeps the comparison in line with the latest grid. It is one small example of putting location intelligence automation to work for a public service.

Questions

What walking time should I use for a bus stop?

Five minutes is common for frequent urban routes and ten for less frequent ones. Use the same time for every candidate you compare.

Can I count residents along a whole route?

Yes. Give back every hexagon for each stop's walk area, remove duplicates, then add them up so each resident is counted once.

Does it work for cities in the United States?

Not for residents yet: the population grid does not cover the United States or the United Kingdom. Nearby places still works there for counting schools, clinics and shops near each stop.

Can I see the walk areas on a map?

Yes. Add Show on a map after the counts to see each stop's walk area and, with every hexagon, a heat map of where residents are.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.