Night-time residents vs daytime visitors: two different counts of an area

Residents and visitors are two different counts of the same place. Residents are the people who live there and sleep there at night; a population grid counts them. Visitors, workers and passers-by are everyone present during the day; footfall measures them, as people-hours of presence. An office district can have few residents and heavy footfall at noon. A quiet suburb can have many residents and little footfall at any hour. Most site decisions need to know which of the two a business lives on.

This article is for anyone choosing opening hours, a site or a delivery zone: pharmacies, cafes, gyms, convenience stores, security firms. It covers what each count measures, how to set them side by side, a worked example, the limits of each, and an AI employee that reports both for every site you have.

Two counts, two questions

What the two blocks in xMap Flows measure.

The units are different, so the two numbers can never be added or subtracted. Footfall counts hours: someone who stays three hours near a site counts three times. A count of residents counts heads. What you can compare is the shape: is this area busy when its residents are at home, or when they are away?

Reading the day's shape

Mobility Footfall can split each place's day into morning, midday, evening and late night, and give the busiest hour and the busiest and quietest day. That split is the closest the data comes to telling residents and visitors apart.

• A strong midday and a quiet late night, with few residents, is a working district. Lunch, quick services and weekday opening hours fit; Sunday trade will be thin.
• A strong evening and late night, with many residents, is a place people come home to. Late opening, evening classes and delivery fit.
• A strong late night and few residents is a nightlife or transport area. Security, late food and late transport fit; a family clinic does not.
• A flat day with many residents and steady footfall is a mixed neighbourhood: often the most forgiving place to open.

Then read the residents count from Demographics beside it, in the same radius, to confirm. Many residents and an evening peak tell the same story twice, which makes it more believable.

A worked example

A made-up case. A pharmacy group in Mumbai is deciding the opening hours of two new branches, one in an office district and one in a residential district a few kilometres away. It asks for the residents within 1 km of each and the footfall within 200 m over the last 30 days. The figures below are invented, to show how the reading goes.

Made-up figures, for illustration only.

The office branch serves people who live elsewhere. It should open early, staff up at lunch and close in the early evening, and it can shorten its Sunday hours. The residential branch serves its neighbours after work and late, every day of the week, so it should stay open late and keep the same hours at weekends. The same chain, the same products, two very different timetables, both read from data rather than guessed.

Where each count falls short

Residents

A residents count says nothing about the hours people are around, or about the thousands who arrive each morning. In the United Kingdom and the United States there is no residents count in xMap Flows at all. It also changes slowly, so a new apartment tower that filled last year may not show yet.

Footfall

Footfall is people-hours, not unique people, so a long-staying crowd looks bigger than a passing one of the same size. It arrives about 10 days late, so it describes the recent past, not today. It starts in mid-October 2026, so it cannot yet show the seasons. It does not cover Australia yet. And where visitors come from is measured only in Sao Paulo so far; elsewhere you know how busy a spot is, not where the people live.

Mistakes to avoid

• Dividing footfall by residents and calling it a visitor ratio. The units differ; at most use it as a rough index to rank sites in one city against each other.
• Comparing one week of footfall from a holiday week with a normal week elsewhere. Use the same window for every site.
• Choosing a radius that does not match the question: 200 m for how busy the street is, 1 km or a walking area for who lives near enough to come.
• Ignoring the late-night share. It is often the clearest sign of what kind of area you are in.

An AI employee that reports both

This is a good monthly job for an AI employee: one row per site, both counts, and a plain label for each.

1. Schedule: the first Monday of each month.
2. My data: your branches, or the candidate sites.
3. Demographics: residents within 1 km of each.
4. Mobility Footfall: footfall and busy hours within 200 m, last 30 days.
5. xMap LLM: label each site as a home area, a working area, a night area or mixed, with a one-line reason drawn from its own figures.
6. Email or a sheet to the operations team.

The inbox gets a table that says, branch by branch, who lives around it and when it is busy. Sites with no footfall yet say so in their note rather than showing zero. The Where to patrol on weekend nights template applies the same idea to late hours, and Offices near my gyms for corporate memberships goes after the daytime crowd a gym's residents do not include.