Why City Boundaries Lie
The lines on the map are political, not economic. A city's official border was drawn by administration and rarely redrawn since โ so it swallows farmland it shouldn't, and cuts off dense neighbourhoods it should contain. When your unit of analysis is "a city," that mismatch quietly distorts every comparison you make. This lab shows the problem, how satellite data fixes it, and why India in particular undercounts how urban it really is.
The administrative city vs the economic city
Economists define a city by agglomeration โ a contiguous patch of built-up density where people and firms benefit from being close together. Administrations define it by whatever line was last drawn in a gazette. The two rarely match. Toggle the map to see the gap.
This isn't hypothetical
Delhi & its edge
Noida, Gurugram and Ghaziabad are functionally part of one economic city with Delhi โ shared labour markets, commutes and firms โ yet sit in different states and administrations. Study "Delhi" by its border and you miss a huge chunk of the actual city.
Dhaka's mismatch
Dhaka's official limits reach out over farmland while dense, unplanned settlements at the fringe fall outside them. The border counts fields as city and leaves people out.
Every country, differently
"City" means something different in each country's law, so cross-country comparisons of "urban" are often comparing incomparable units โ one reason global urban research is so hard.
How India undercounts its own cities
India's Census uses a strict, decades-old rule to decide what counts as "urban". Many places that are city-like in every practical sense stay classified as rural โ so the official urbanisation rate is almost certainly an undercount.
- a population of at least 5,000;
- a density of at least 400 persons per km²; and
- at least 75% of the male main workforce in non-agricultural work.
| Boundary logic | What it counts as a city | Blind spot |
|---|---|---|
| Statutory (administrative) | Places a government chose to give an urban local body. | Politics and lag decide the line, not density. |
| Census town (India) | Meets the 5,000 / 400-per-km² / 75%-male-non-farm rule. | Gendered, agriculture-anchored, re-classified slowly. |
| Economic / built-up | A contiguous patch of built-up density, from satellite data. | Needs calibration; a snapshot in time; some manual tuning. |
Redrawing the city from space
Instead of trusting an administrative line, you can build a boundary from what the land actually looks like. The approach behind Development Data Lab's Global Urban Boundaries combines three satellite-derived signals and asks: does this small grid cell look urban?
Population density
How many people live in the cell โ from gridded datasets like WorldPop.
Built-up area
How much of the cell is buildings and pavement โ from GHSL (Global Human Settlement Layer).
Night-time lights
How brightly the cell glows after dark, a proxy for activity โ from VIIRS.
Try it: classify a grid cell
Drag each signal relative to its (illustrative) threshold and watch the 2-of-3 rule decide. This is a simplified teaching model, not the production algorithm.
Why any of this matters for your work
Boundaries are not neutral bookkeeping. The line you use silently shapes what you measure, who is served, and whether your comparisons hold up.
The line changes the finding
- Per-capita anything. Include farmland and the denominator swells, so income, density and service coverage per person all look lower than the real city's.
- Comparisons across cities or countries. If "city" means different things in each place, a ranking of "most productive cities" may just be ranking how boundaries were drawn.
- Who is responsible. A dense settlement classified rural gets rural governance and budgets โ no urban planning, no municipal services โ even as it fills with people.
- Growth vs annexation. A city can "grow" on paper simply because its border was redrawn. A fixed-boundary, satellite snapshot lets you separate real densification from administrative expansion.
Get the real data
This lab teaches the idea. For the actual boundaries and the tools to work with them, go to the source โ Development Data Lab, an independent research group whose datasets are open and free:
Global Urban Boundaries 2026
Economic city boundaries for 5,000+ cities worldwide, with an interactive explorer comparing them to older definitions, and downloadable data.
SHRUG (for India)
DDL's open, village/town-level platform linking Census, night-lights and more โ the finest-grained way to study urbanisation in India. Also in our Indian Data Navigator.
The Global Urban Boundaries dataset, the interactive explorer, and SHRUG are the work of Development Data Lab, not ImpactMojo. This lab is an independent teaching companion; all credit for the data and method is theirs.
Now make the call for your own work
Turn the lesson into a decision you can defend. Record which boundary your analysis will use and why, then export a short boundary-decision note to paste into a concept note, proposal, or methods section.
The lesson and making the call are free. Exporting the note is a Premium feature (Practitioner plan and up).
You'll never trust a city border blindly again
Administrative vs economic boundaries, India's urban undercount, and how satellites redraw the map โ enough to read urban statistics critically and pick the right unit for your own analysis.