A worked example: 1 km² of central Paris
Measured on 2026-08-14 for the box 2.345400,48.852100,2.359000,48.861100, around the Île de la Cité. The numbers below are what this tool returned, not an estimate. Île de la Cité and the Latin Quarter, Paris, 1.0 km².
| Dataset | Buildings | Total footprint | What happened |
|---|
| OpenStreetMap | 1,391 | 454,132 m² | Answered live from Overpass in about six seconds. 326 m² per polygon. |
|---|
| Microsoft Global ML Building Footprints | 213 | 568,930 m² | One 91 MB file, quadkey 120220011, read whole and filtered to the box. 2,671 m² per polygon. |
|---|
| Google Open Buildings v3 | 0 | 0 m² | No coverage. Google Open Buildings v3 does not publish Europe. |
|---|
Read those two rows again. OpenStreetMap returns 6.5 times more polygons than Microsoft, and Microsoft covers 25% more ground. Both are true. In central Paris the model merges a whole block into one shape, 2 671 m² on average, while people drew each building, 326 m² on average. So a count tells you how the data was cut, not how much of the city is in it. That is why this page never ranks a source by its count, and why it shows total footprint area beside every one.