FlowsBook a callSign inCreate free accountSign up
Population and demographics

Library catchment population: residents per library and the districts without one

How to work out how many residents each public library serves, spot districts with no branch within reach, and keep the picture current for a library service plan.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

A library catchment population is the number of residents living within a reasonable distance of a branch, usually a 15 to 20 minute walk or about 1 to 2 kilometres in a city. Divide the residents of each district by the libraries that serve it and you get residents per library; districts where that figure is very high, or where no branch lies within reach at all, are the gaps a library service plan should address first.

This is for library services, city planning teams, education departments, charities that run reading rooms and developers who promise community facilities in a new district. It covers what to count, how to read residents per library without being misled, a worked example with invented districts, mistakes to avoid and a flow that keeps the numbers fresh.

What a library serves, and who it misses

Libraries are walked to more than driven to. Children come after school, older readers come on foot or by bus, and students use them as a place to work. The people who lose out when a branch is far away are exactly those without a car: the young, the old and households on low incomes. That is why planners measure catchment by walk or short distance, and why the age profile of a district matters as much as its total.

A district can be well served on paper because one large central library sits nearby, while its outer streets are a long walk from anything. So it pays to look at two figures side by side: residents per library across the district, and the residents who live beyond the walking distance of any branch.

The figures and how to read them

  • Residents in each district or neighbourhood, summed from a population grid of small hexagons.
  • Children aged 0 to 19 and residents aged 60 and over, the two groups that rely most on a nearby branch.
  • Libraries within reach: public libraries and children's libraries within 1 or 2 km of the district's middle, or inside it.
  • Residents per library: the district's residents divided by the branches that serve it.
  • Distance to the nearest branch, for each small part of a district, to find the pockets left out.

An example with invented districts

Suppose a city team in Pune is preparing a five-year plan for its branches. These figures are made up to show the method.

DistrictResidentsUnder 20Libraries within 2 kmResidents per library
Old city180,00041,000536,000
Eastern growth area240,00071,0001240,000
University quarter95,00030,000331,700
Western suburbs150,00039,0000no branch

Invented figures, for illustration only.

The old city looks crowded but has five branches. The eastern growth area holds the most young people and relies on a single library, and the western suburbs have none within 2 km at all. A planner would put both on the shortlist, then check bus routes and where schools sit before choosing a site for a new branch or a mobile library stop.

Mistakes that hide the real gaps

  • Using city-wide averages. One residents-per-library figure for the whole city hides the districts with none.
  • Counting a branch twice. A library on a boundary serves two districts. Decide whether to split it or count it for both, and stay consistent.
  • Ignoring opening hours. A branch open two afternoons a week serves far fewer people than its location suggests. Add hours from your own records.
  • Treating every library as equal. A central library with long hours and study space is not the same as a small reading room; weight them if your plan needs to.
  • Planning on a snapshot. New housing fills districts quickly. Rerun the count each year so the plan follows where people now live.

An AI employee that keeps the map current

In xMap Flows, a flow that runs on its own is an AI employee. This one counts residents and branches for every district and sends the table and a map each quarter. The methods behind it are gathered in the guide to location intelligence automation.

  1. Schedule: every quarter, on the first Monday (Schedule).
  2. My data: a table of district names with the latitude and longitude of each district's middle (My data).
  3. Demographics: residents within 2 km of each, with children and seniors (Demographics).
  4. Nearby places, set to pass on each incoming place with counts: libraries, public libraries and children's libraries within the same 2 km (Nearby places).
  5. Calculated field: per_library = if(nearby_count > 0, round(population / nearby_count), population).
  6. Sort and limit, highest residents per library first, then Make a report or Email to the planning team.

The report lists every district with its residents, its young and old, the branches within reach and the ratio, plus the nearest branch to each. Districts with a count of zero stand out on the map. To see the pockets inside a district rather than district totals, set Demographics to give back every hexagon and add Find nearest with your branches as the points, then keep the hexagons more than 2 km from a branch. The templates Older people far from a community centre and Neighbourhoods with many people and few notaries use the same pattern for other services, and Children per school, block by block is close to the education side. Flows for councils are on the government and cities page.

Questions

What is a normal number of residents per library?

Standards differ by country and by the size of branch, so there is no single figure. Use residents per library to rank your own districts and to show change from one year to the next.

Should I measure catchment by walk or by distance?

A straight distance of 1 to 2 km is simple and comparable across districts. Where rivers or major roads cut the walk, a walking area drawn on the streets with Travel area gives a fairer picture.

Can the flow use our own list of branches instead of the places database?

Yes. Upload your register to My data and use it with Find nearest, which gives each part of the city its nearest branch and the distance to it.

Does it show how many people use each library?

No. It counts residents who live nearby. Loans and visits come from your own systems, which you can join to the table with Match with my table.

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.