DDL Global Urban Boundaries

Package scope: Global ADM2 urban agglomeration splits
Release version: v0.1
Release date: 2026-05-11
Reference year: 2025
Feature count: 3130
Archive filename: ddl-urban-boundaries-adm2-global-v0.1.zip
Generated at: 2026-05-11 11:22:30 UTC

Contents
- One GeoPackage with a single `urban_boundaries_adm2` layer
- This README

GeoPackage schema
- id: DDL boundary identifier
- parent_id: Parent DDL urban agglomeration identifier
- adm_id: Source GADM administrative identifier for the split
- name: Boundary name
- population: estimated population
- alpha3: ISO alpha-3 country code
- area: geometry area in square meters
- geometry: boundary polygon in EPSG:4326

Coordinate reference system
- EPSG:4326

License
- Released under CC BY 4.0.

Disclaimer
By accepting data provided by the Development Data Lab (DDL), you agree to the following conditions of release and acknowledge the following disclaimers: Neither DDL nor the contributors of data to DDL shall be held liable for any improper or incorrect use or application of the data provided, and assume no responsibility for the use or application of the data or information derived from interpretation of the data. In no event shall DDL or its collaborators be liable for any direct, indirect, or incidental damages arising from the use or application of these data. This disclaimer of liability applies to any damages or injury, including but not limited to those caused by any failure of performance, error, omission, defect, delay in operation or transmission, computer virus, alteration, use, application, analysis, or interpretation of data. No warranty, expressed or implied, is made regarding the accuracy, adequacy, completeness, reliability, or usefulness of any data provided. These data are provided on an "as is" basis. All warranties of any kind, express or implied, including but not limited to fitness for a particular use, freedom from computer viruses, and non-infringement of proprietary rights, are disclaimed. Data are added and changed periodically, and data may become out-of-date quickly. It is recommended that the user not let a significant period of time elapse between obtaining and using the data.
