FlowsBook a callSign inCreate free accountSign up
Population and demographics

Water point placement by population in fast-growing districts

Where to add the next public taps, kiosks or standpipes: residents per water point, the streets furthest from one, and how to watch growing edges of a city year by year.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Water point placement by population means putting new taps, kiosks or standpipes where the most residents live furthest from an existing one. Map residents in small cells, measure each cell's distance to the nearest water point, and rank the cells that are both crowded and far away. In districts that grow quickly, repeat it every year, because the streets that were empty fields last time may now hold thousands of people.

This article is for water utilities, municipal engineers, humanitarian and development teams, and companies that run water kiosks. It explains why distance and density have to be read together, the figures that matter, a worked example on an invented district, common mistakes, and an AI employee that redraws the gaps each year.

Distance and density, read together

A water point serves the households who can walk to it and carry water home. Beyond a few hundred metres the walk becomes a burden, and the people who carry the load are often women and children. A district can therefore have enough taps in total and still leave its outer streets badly served, because all the taps sit near the old centre.

Density says how many people a new tap could help. Distance says how much they need it. A cell with ten thousand residents per square kilometre that sits 1.5 km from water is a far higher priority than a sparse cell at the same distance or a crowded cell next to a tap. Ranking by one figure alone gets the order wrong.

What to measure

  • Residents per small cell: a population grid in hexagons of about 0.1 km2 shows where people actually live inside a district.
  • Distance from each cell to the nearest water point: from your own register of taps, kiosks and standpipes.
  • Residents per water point for each district, as a summary for budgets.
  • Children aged 0 to 19, if your programme focuses on schools or families.
  • Signs of growth: new building on the edge of the city, seen on repeated satellite pictures or in your planning records.

An invented example on a city edge

Say a utility on the outskirts of Chennai has 40 public water points across a district that has spread east over recent years. These numbers are made up to show the reasoning.

Part of the districtResidentsPeople per km2Water points insideFurthest cell from a point
Old centre62,00018,000210.4 km
Northern estates48,00012,500110.9 km
Eastern edge55,0009,80042.1 km
Southern fields9,0001,70041.2 km

Invented figures, for illustration only.

The eastern edge holds almost as many people as the old centre but has a fifth of the water points, and its furthest streets are more than 2 km from one. Satellite pictures from earlier years would show those streets being built. That is where the next kiosks go, starting with the crowded cells furthest out, while the southern fields can wait until they fill.

Common mistakes

  • Planning by district totals. Averages hide the far streets. Work at the level of small cells.
  • Measuring straight lines only. A railway or canal can turn 500 metres into a long detour. Walk the shortlisted streets before you build.
  • Counting points that do not work. A broken standpipe serves nobody. Keep your register's status up to date and filter on it.
  • Treating the grid as a census of this month. In a district that grows fast, the newest streets may be under-counted. Pair it with what you see on the ground.
  • Placing once and forgetting. Rerun the analysis every year so new settlements are caught early.

An AI employee that redraws the gaps

In xMap Flows, an AI employee can produce the ranked list of cells each year and a map for the engineers. The background on mapping data like this is in the guide to location intelligence automation.

  1. Schedule: once a year, or each quarter in districts that grow fast.
  2. Area of interest: the district, drawn on the map (Area of interest).
  3. Demographics, set to give back every hexagon: residents and age groups in each small cell (Demographics).
  4. Find nearest: your register of water points as a table in My data; each hexagon gets its nearest point and the distance (Find nearest).
  5. Filter: keep cells more than 500 metres from a point, then Calculated field for a priority such as population times distance.
  6. Sort and limit, highest priority first, then Show on a map and Email the list to the planning team.

The engineers receive a map of the far, crowded cells and a table of the top ones with their residents and distance to water, ready to compare with site visits. A second flow with Satellite images of the edge areas each quarter shows where new building is going up. The template Villages far from drinking water covers rural settlements, and New apartment buildings: water connections ahead watches new demand in cities. More flows are on the water and waste page.

Questions

What distance to a water point is acceptable?

Many programmes work with a few hundred metres as a target, but the right figure is set by your national standard or donor. Set the Filter to that distance and the flow keeps the cells beyond it.

Can I use the places database for water points?

It lists some drinking water fountains and dispensers, but rarely every public tap. Your own register, uploaded to My data, is the reliable list.

Does the population grid show growth?

No. It shows where people live now. Growth has to come from repeated satellite pictures, new connection requests or planning records.

Can the flow handle informal settlements?

It counts the residents the grid sees, which may be fewer than live there in new informal areas. Check those areas on the ground and with satellite pictures before deciding.

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.