Location & accessibility

Catchments, access to services, gravity models, site suitability and choosing where the next facility should go.

A straight-line buffer against a drive-time catchment over the same road network. a circle is not a catchment2 km, as the crow flies5 minutes, by roadThe difference between the two is a river, a railway or a one-way system — and it is the answer

A catchment is a claim about how people travel, and a circle drawn around a facility is a claim that they travel in straight lines at uniform speed. They do not: a river, a railway, a one-way system or a single bridge changes the shape entirely, which is why a five-minute drive-time area and a two-kilometre buffer rarely overlap much.

From there the topic is about deciding rather than measuring. Access, gravity models, site suitability and facility location all take the same shape: score the candidates, weight the criteria, apply the constraints as a mask rather than a low score, and check how much the answer depends on the weights you chose. The last step is the one most often skipped and the one that decides whether the result is a recommendation or a preference.

The concepts cover catchments, accessibility measures and suitability; the how-to guides compute them; and the fixes cover the models that will not solve and the maps that come out flat.

Learning paths run through this topic too — see the end of this page.

🧭 Start with the concepts

The ideas the how-to guides below assume you already have.

Show every concept in this topic

⚙️ Then do the task

Step-by-step walkthroughs with code you can copy and adapt.

Show every how-to guide in this topic

🔧 When it breaks

The errors this topic produces, with the cause explained rather than just the command.

Related topics

Subjects that keep coming up alongside this one, most overlap first.

Keep browsing

Location & accessibility sits in Modelling & prediction. Every topic on the site is listed on the topics index.