← All articles

By ·

WorldPop vs LandScan vs GHSL vs Kontur vs Meta HRSL: Which Gridded Population Dataset to Use, and How to Check It

WorldPop vs LandScan vs GHSL, Kontur, Meta and GPW compared. Kontur's grid read 9.6% above Islamabad's 2023 census, or 3.1% below, by boundary rule.

WorldPop, GHS-POP, LandScan, Meta's High Resolution Settlement Layer, Kontur Population and GPWv4 all start from census counts and spread them over a grid, so the right one depends on resolution, method and what "population" means. WorldPop (100 m) and Meta (30 m) map where people live, LandScan (about 1 km) maps a 24-hour average of where people are, and GHS-POP is the best time series. Before using any of them, check the grid's total against the census for the same boundary: Kontur's hexagons came out 9.6% above Islamabad's 2023 census or 3.1% below it, depending only on how the boundary was applied.

This article compares the six datasets on producer, resolution, method, population type, years and licence, then shows a check I ran on the Kontur hexagons used across this site against census figures for Calgary, Islamabad and Bahawalpur, with Python code for zonal sums and census rescaling.

What is a gridded population dataset?

A gridded population dataset is an estimate of how many people live in, or are present in, each cell of a regular grid. Census offices publish counts for administrative units such as districts, tehsils or dissemination areas, which vary in size and change over time. A grid spreads those counts into equal cells, so you can sum people inside any polygon: a drive-time catchment, a flood zone or a station's coverage area.

How the counts are spread is what separates the datasets:

Almost every dataset is ultimately a census count redistributed. A grid never contains more information about the total than the census behind it, and its error is concentrated in where people are put inside each unit.

How do WorldPop, GHSL, LandScan, Meta, Kontur and GPW compare?

DatasetProducerResolutionMethodPopulation typeYearsLicence
WorldPop Global 2 (R2025A)University of Southampton100 m (1 km aggregates)Random-forest dasymetric, constrained to settlementsResidentialAnnual, 2015 to 2030CC BY 4.0
GHS-POP R2023AEuropean Commission Joint Research Centre100 m (and 3 arc-seconds)GPWv4.11 census counts spread by GHSL built-up surface and volumeResidentialEvery 5 years, 1975 to 2030CC BY 4.0
LandScan GlobalOak Ridge National Laboratory30 arc-seconds (about 1 km)Multi-variable dasymetric, now with machine-learning modelsAmbient (24-hour average)Annual, 2000 onwardCC BY 4.0 since the 2022 public release
Meta High Resolution Population Density Maps (HRSL)Meta and CIESIN, Columbia University30 m (1 arc-second)Buildings detected in satellite imagery, census counts allocated to themResidential, with age and sex splitsVaries by countryCC BY 4.0
Kontur PopulationKonturH3 resolution 8 (about 400 m), plus 3 km and 22 kmFuses GHS-POP, Meta HRSL, Microsoft building footprints, land cover and OpenStreetMapResidentialReleases to 1 November 2023Creative Commons Attribution
GPWv4.11CIESIN, Columbia University (NASA SEDAC)30 arc-secondsAreal weighting of about 13.5 million census unitsResidential2000, 2005, 2010, 2015, 2020CC BY 4.0

A few things the table does not show:

Should you use residential or ambient population?

Use residential population for anything about homes and the services people reach from home, and ambient population for anything about who is exposed at an unknown time of day. School and clinic access, voter or customer catchments, and station coverage all assume people start from where they live, so WorldPop, GHS-POP, Meta or Kontur fit. Earthquake, flood and industrial-accident exposure, where the event can happen at 2 pm on a Tuesday, is LandScan's purpose.

Mixing them in one model gives a number nobody can interpret. If you need both, run the analysis twice and report the two answers side by side.

Does a gridded population total match the census?

Usually within a few percent for a whole city, but only if the grid and the census cover the same area, and that is easy to get wrong. I checked the Kontur hexagons (1 November 2023 release, H3 resolution 8) behind the Site Selection Showdown map against census figures for each study area.

Method:

Study areaOSM boundaryHexagonsEvery touching hexagonWeighted by share insideCensusDifference
Calgary852.7 km²1,2051,463,3281,456,5771,306,784 (2021)+12.0% / +11.5%
Islamabad Capital Territory962.8 km²1,1642,590,2332,291,5662,363,863 (2023)+9.6% / −3.1%
Bahawalpur City Tehsil399.0 km²542673,192604,230815,202 (2023)−17.4% / −25.9%

Left: dot chart of Kontur population minus census, as a percentage of census. Calgary +12.0% and +11.5%, Islamabad Capital Territory +9.6% for every touching hexagon and -3.1% when weighted by share inside, Bahawalpur City tehsil -17.4% and -25.9%. Right: map of Islamabad's population density on hexagons, with the territory boundary in black and 190 hexagons crossing it outlined, many along the border with Rawalpindi

Each city tells a different story about why a grid total and a census figure disagree.

Each row shows a different failure:

  1. Islamabad: the boundary rule. 190 of the 1,164 hexagons cross the territory line, and they hold 514,217 people. Most of those crossing the southern edge are in dense Rawalpindi, which presses right against the boundary. Counting them in full adds about 299,000 people who live outside the territory. Weighting by area brings the total to 3.1% below the census, which is a good match for a modelled grid.
  2. Calgary: the reference year. The boundary barely matters here (198 crossing hexagons hold only 23,559 people, and weighting changes the total by 0.5%). The gap is time. Calgary grew fast after 2021, and the City of Calgary's own estimate for April 2023 was 1,422,800, within about 3% of the Kontur total. Comparing a 2023 grid with a 2021 census makes a good grid look 12% wrong.
  3. Bahawalpur: the boundary does not match the census unit. The OpenStreetMap polygon called Bahawalpur City Tehsil covers 399 km². Compilations of the census tables put the tehsil at about 1,490 km². The 2023 figure usually quoted for the city itself is 903,795. None of these covers the same area as the polygon, so the −17% and −26% come from mismatched boundaries and cannot be used to judge Kontur's accuracy.

The general rule: before you use any gridded dataset, sum it over a boundary that matches a census unit exactly, for the same reference year, and explain any gap larger than a few percent before running the analysis.

How do you sum a population raster inside polygons in Python?

Read the raster with rasterio, check its CRS and nodata value, then use zonal statistics to sum the cells inside each polygon. The choice of tool matters at the edges.

import geopandas as gpd
import rasterio
from rasterstats import zonal_stats
from exactextract import exact_extract

tif = "worldpop_pakistan_2023_100m.tif"      # a WorldPop country GeoTIFF
with rasterio.open(tif) as src:
    print(src.crs, src.res, src.nodata)       # EPSG:4326, ~0.000833°, nodata
    pop = src.read(1, masked=True)            # masks the nodata cells
    print(f"Raster total: {pop.sum():,.0f}")

zones = gpd.read_file("tehsils.gpkg").to_crs(src.crs).reset_index(drop=True)

# Centre-of-cell rule: a cell counts in full if its centre is inside
zs = zonal_stats(zones, tif, stats=["sum"], all_touched=False)
zones["pop_centre_rule"] = [z["sum"] for z in zs]

# Exact fractional coverage: each cell weighted by its share inside
ee = exact_extract(tif, zones, "sum", include_cols=["tehsil_code"], output="pandas")
zones = zones.merge(ee.rename(columns={"sum": "pop_exact"}), on="tehsil_code")

Use exactextract for small or irregular polygons, where a 100 m cell is a large share of the shape. With all_touched=True, rasterstats counts every cell the polygon touches in full, which is the raster version of the Islamabad mistake above.

How do you rescale a gridded dataset to census totals?

Multiply every cell in a census unit by the ratio of the census count to the grid's sum for that unit. This keeps the grid's pattern inside each unit and makes every unit total match the official figure.

import numpy as np
import rasterio
from rasterio import features

with rasterio.open(tif) as src:
    pop = src.read(1, masked=True).filled(0).astype("float64")
    zone_id = features.rasterize(
        zip(zones.geometry, zones.index + 1), out_shape=pop.shape,
        transform=src.transform, fill=0, dtype="int32")
    profile = src.profile

grid_sum = np.bincount(zone_id.ravel(), weights=pop.ravel())
factor = np.ones_like(grid_sum)
factor[zones.index + 1] = zones["census_2023"].to_numpy() / grid_sum[zones.index + 1]
adjusted = pop * factor[zone_id]

profile.update(dtype="float32", nodata=-1)
with rasterio.open("pop_rescaled_2023.tif", "w", **profile) as dst:
    dst.write(adjusted.astype("float32"), 1)

Rescale with the smallest census units you can match exactly. A factor far from 1 in one unit (say below 0.8 or above 1.25) is worth a look before you trust it: it usually means a boundary mismatch, a new development the model missed, or an error in the census join. To move the result onto hexagons, aggregate with H3 at a resolution that suits the analysis, as covered in the H3 resolution guide.

Which population dataset should you use?

JobUseWhy
Access to schools, clinics or shops at neighbourhood scaleWorldPop 100 m or Meta 30 m, rescaled to censusResidential, fine enough for walking distances
Ready-made hexagons for site selection or coverage modelsKontur PopulationAlready on H3; check boundary and year first
Change over decades, urban growthGHS-POPConsistent method across 1975 to 2030
Disaster exposure, daytime presenceLandScan GlobalAmbient population
Age or sex groups (women of reproductive age, children under 5)Meta's demographic layers, or WorldPop age-sex gridsSplits by group
A baseline with no model assumptionsGPWv4.11Census spread by area only
Official counts for a reportThe census itselfGrids are estimates

For Pakistan specifically, the 2023 census, the country's first digital census, recorded 241.49 million people and publishes counts down to tehsil level. That makes rescaling straightforward, and it matters: grids built before the 2023 results were released relied on older census figures and projections. The Islamabad school access study on this site used Kontur hexagons for the same reason the site selection maps do: they are ready to route on. The same caution applies there. A population grid sets the denominator for every accessibility ratio, including the supply-to-demand ratios in two-step floating catchment analysis, so an error in the grid passes straight into the result.

What should you take from this?

Pick the dataset by what you need to count: residents at fine scale (WorldPop, Meta), residents over time (GHS-POP), people present during the day (LandScan), or hexagons ready for analysis (Kontur). Then check it against the census for the exact same boundary and year. In my three cities, the boundary rule moved Islamabad's total by 13 percentage points, the reference year explained Calgary's 12% gap, and in Bahawalpur the boundary itself was not the census unit. None of that showed up on the map. The same checks belong in any fire station or service-coverage study before the first model runs.

If you need population estimates prepared and checked for a planning, site-selection or coverage project, email me at mahad.imran29@gmail.com.

Frequently asked questions

What is the difference between WorldPop and LandScan?

WorldPop estimates residential population, where people live, at 100 m using random-forest models that spread census counts over settlements. LandScan Global estimates ambient population, a 24-hour average of where people are, at about 1 km from Oak Ridge National Laboratory. Use WorldPop for services to homes, such as schools and clinics. Use LandScan when daytime presence matters, such as hazard exposure.

What is the best population data for GIS?

Use the national census for official totals, and a gridded dataset to place people inside census units. For residential analysis at neighbourhood scale, WorldPop (100 m) or Meta's 30 m maps are the usual choices. For time series, GHS-POP covers 1975 to 2030. For ready-made H3 hexagons, Kontur Population. Always compare the grid's total with the census for your study area first.

Is LandScan free to use?

Yes. LandScan Global was released to the public in 2022 under a Creative Commons Attribution licence, and catalogues such as Google Earth Engine list it as CC BY 4.0, so commercial use is allowed with attribution. WorldPop, GHS-POP, Meta's maps, GPWv4 and Kontur Population are also published under Creative Commons Attribution licences. Check each download page for the exact attribution text.

What population grid should I use for Pakistan?

Start from the 2023 census, Pakistan's first digital census, which counted 241.49 million people, for totals by district and tehsil. Then use WorldPop's annual 100 m grids, Meta's 30 m maps or Kontur's H3 hexagons to place people inside each tehsil, and rescale the grid so each tehsil matches its census total. Watch boundaries: OpenStreetMap polygons do not always match census units.

How accurate are gridded population datasets?

Totals for large areas are usually close to census figures because most grids are built from census counts. Error grows at small scales, in fast-growing suburbs and informal settlements, and at boundaries. In my check, Kontur matched Islamabad's census to within 3.1% when hexagons were weighted by their share inside the boundary, but counting every hexagon touching the boundary added 9.6%.

Let's talk.

Best way to reach me is email. I respond to most things.