FlowsBook a callSign inCreate free accountSign up
Population and demographics

How many people each fire station can reach in time

Working out fire station coverage population: the residents inside each station's drive area, the people outside every area, and how to keep the count current.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

The usual way to work out fire station coverage population is to draw, for each station, the area its engines can reach within your response target by road, then count the residents inside that area; the people left outside every station's area are your coverage gap. Drive areas and a population grid make both numbers quick to produce and easy to repeat whenever a station moves, closes or opens.

This is for fire and rescue planners, municipal risk teams, insurers studying exposure and consultants preparing station reviews. It covers the two numbers that matter, how to draw the areas, a made-up three-station example, the pitfalls, and an AI employee that reruns the analysis on a timetable.

Two numbers: covered and uncovered

Covered is the residents inside each station's drive area. It shows how much each station carries, and which ones protect the most people.

Uncovered is the residents inside none of the areas. It is the number a review exists to bring down, and the map of where those people live shows where the next station, or a moved one, would do most good.

The two do not simply add up to the city's population, because neighbouring areas overlap: a street between two stations sits inside both. Count overlaps once when you sum.

Drawing the areas

The Travel area block draws what can be reached by car from each station within a set time or road distance, following the road network (up to 15 minutes or 10 km for now). It does not model traffic at different times of day or the speed of an engine with lights on, so treat the areas as a consistent, cautious yardstick rather than a promise of arrival times. Demographics after it counts the residents, men and women and age groups inside each area.

For the uncovered count, work cell by cell: set Demographics to Every hexagon across the whole city, then use Find nearest with your station list to give every cell its nearest station and the straight-line distance. Cells further than your threshold are the gap.

A made-up example with three stations

Invented, for illustration: a city in Ontario with three stations and an 8-minute drive target.

Made-up stationResidents in its 8-minute areaAged 80 and overArea overlapping a neighbour
Station 1, old centre64,0003,900Yes, with Station 2
Station 2, inner east51,0002,700Yes, with Station 1
Station 3, northern suburb28,0001,100No

Invented figures to explain the method; not data about any city.

Say the cell-by-cell count finds 19,000 residents more than 5 km from any station, most of them in a new subdivision north-west of Station 3. Stations 1 and 2 overlap heavily, so moving Station 2 a little further east would barely change who is covered there. The review's question becomes whether a fourth site in the north-west, or a move of Station 3, brings the 19,000 down. The over-80s column matters too: older residents are slower to escape a fire, so services often weigh them more heavily.

Who lives in the gap matters too

A gap of 19,000 people in family housing and a gap of 19,000 in sheltered flats for older people are not the same risk. Because every cell carries its age groups, the uncovered cells can be summed by age as well as in total, which gives the review a second figure: how many residents aged 80 and over sit outside the target. Put both on the first page of the paper.

Pitfalls

  • Circles instead of drive areas. A circle crosses rivers and rail lines an engine cannot.
  • Double counting. Add the stations' totals and you count overlap twice; use the cell method for the city-wide figure.
  • Residents only. Daytime populations in business districts and industrial estates are not in these counts; flag those areas separately.
  • A stale station list. Use your own register, not a list scraped from a map.

Rerunning it with an AI employee

  1. Schedule: every quarter, or on demand before a review.
  2. My data: your stations, one row each.
  3. Travel area: the drive target around each station.
  4. Demographics: residents and age groups inside each area.
  5. Make a report: a table of stations with their covered residents and a map.

A companion flow runs the cell method: Area of interest for the city, Demographics with Every hexagon, Find nearest with the stations, Filter for cells beyond the threshold, Show on a map and Email. The planning team receives the per-station table, a map of uncovered cells and a CSV of every cell to load into their own tools. The Blocks with no fire station within 5 km template is this flow ready-made, and People per police station, block by block applies it to policing. More on running operational analysis like this is in the field operations guide.

Questions

Does the drive area account for rush hour?

No. Travel area follows the roads but not the traffic at a given time, so use it as a consistent yardstick and adjust your target if you know a corridor is slow.

Can it count people who work in an area but live elsewhere?

No. The figures are residents. Daytime crowds are a different measure.

How large an area can one station have?

Up to 15 minutes or 10 km by road for now.

Can I export the uncovered cells to our own GIS?

Yes. The email carries a CSV of every cell with its position and residents, and the map offers GeoJSON.

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.