GADM analysis workflow: administrative boundaries for global GIS analysis
The GADM analysis workflow uses the Database of Global Administrative Areas as a polygon foundation for country, regional, provincial, district, and other administrative-boundary analysis. GADM’s official site identifies version 4.1 as the current version and reports 400,276 administrative areas. Data can be downloaded by country or for the entire world in formats including GeoPackage, Shapefile, GeoJSON, KMZ, and R-compatible files. The dataset is useful for clipping, aggregation, regional joins, map production, zonal summaries, and organizing other geographic data by administrative hierarchy. Analysts must still verify boundary definitions, version consistency, temporal meaning, disputed areas, geometry validity, and the project’s non-commercial licensing requirements.
GADM is a global vector dataset of administrative areas. Its purpose is to represent the subdivisions of countries and territories at multiple levels, rather than to describe roads, buildings, land cover, addresses, or physical infrastructure. That makes it a boundary layer: a way to divide the planet into named and coded areas so that other geographic observations can be summarized, compared, mapped, or filtered by place. The official GADM site says its current version is 4.1 and that the database delimits 400,276 administrative areas. It recommends downloading data by country, while also providing global downloads. (gadm.org)
How EDK fits
For: GIS analysts, researchers, cartographers, public-interest technologists, humanitarian and development teams, data scientists, and developers who need a consistent global administrative-boundary layer for spatial analysis.
GADM is useful in the broader problem of finding, understanding, and computing about the physical world because administrative boundaries provide one of the main geographic systems for organizing observations about Earth. A road, building, environmental measurement, service request, census estimate, or satellite-derived indicator can be assigned to a country, province, district, or other administrative unit through spatial containment or intersection. That makes GADM a practical regional-indexing layer rather than a complete representation of the world. In an E2-oriented workflow, GADM boundaries can serve as analysis regions used to filter places, aggregate nearby physical features, compare conditions across jurisdictions, or attach administrative context to other location data. This does not imply that E2 supplies GADM data, reproduces its licensing terms, or replaces a dedicated administrative-boundary source.
- •Use GADM polygons as geographic regions for summarizing physical-world features such as roads, buildings, public assets, waterways, environmental observations, or imagery-derived detections by country or subnational unit.
- •Use GADM’s hierarchy and identifiers to filter, rank, compare, and aggregate location-based observations across administrative levels, while preserving the GADM version and boundary definition used in the calculation.
- •Combine administrative boundaries with a broader world-model workflow when a question needs both named regions and fine-grained physical features—for example, comparing infrastructure or environmental conditions across districts rather than only viewing them on a map.
Dataset profile
Formats
GeoPackage
ESRI Shapefile
GeoJSON
Google Earth KMZ
Geodatabase
R-oriented access through the geodata package
Access methods
Download administrative data by country from the official GADM site.
Download a complete-world database when global coverage is required.
Download a global GeoPackage organized as separate layers by subdivision level.
Use the official country and world download pages to identify available files.
Access GADM through the R geodata package for supported analytical workflows.
Quality and limits
No single global accuracy or completeness measure is provided on the official pages reviewed.
Administrative depth and boundary semantics differ among countries.
GADM’s treatment of disputed or de facto areas may differ from official national, international, or program-specific boundary sources.
Administrative changes can create new identifiers and complicate comparisons across releases.
Names and transliterations may vary; name-only joins are fragile.
Global geometry processing can be resource-intensive, especially at the most detailed available levels.
Commercial use and redistribution restrictions can limit operational deployment.
The dataset should not be assumed to provide current legal, cadastral, electoral, or regulatory boundaries.
Analysis workflows
Country and subnational choropleth mapping.
Point-in-polygon assignment of observations to administrative regions.
Clipping satellite, elevation, environmental, infrastructure, or land-cover data by administrative boundary.
Regional counts, sums, rates, densities, and other zonal summaries.
Cross-country comparison using carefully documented administrative levels and compatible indicators.
Hierarchical aggregation from districts to provinces or countries where parent-child relationships are valid.
Geographic indexing for search, filtering, ranking, and comparison of physical-world observations.
Boundary-aware quality control for datasets containing region names or administrative codes.
Versioned change analysis when the same administrative units can be reconciled across GADM releases or authoritative national sources.
Value inside EDK
What GADM contains
GADM contains polygon geometries for administrative areas and attributes describing their names, codes, types, hierarchy, and selected validity or editing information. The metadata page documents level-0 country fields such as GID_0 and NAME_0, and subdivision fields including GID_i, NAME_i, VARNAME_i, NL_NAME_i, HASC_i, CC_i, TYPE_i, ENGTYPE_i, VALIDFR_i, VALIDTO_i, and REMARKS_i. (gadm.org)
The hierarchy can extend from level 0 countries through levels 1, 2, 3, 4, and 5. These levels are not guaranteed to mean exactly the same administrative role in every country: a level may represent a state, province, county, municipality, district, commune, ward, or another locally defined subdivision. GADM’s English administrative-type field can help interpretation, but it should not be treated as a universal cross-country classification.
- •Global coverage of countries, territories, and their subdivisions, subject to GADM’s own geographic model.
- •Polygon geometries at multiple administrative levels.
- •Names in Latin script, alternate names, non-Latin names, administrative types, and several identifier systems.
- •Hierarchical GID codes such as country and subdivision paths, with version information appended to the code structure.
- •Validity and remarks fields where GADM has recorded relevant temporal or editorial information.
Geography, hierarchy, and update cadence
The official data page states that GADM version 4.1 delimits 400,276 administrative areas. It recommends country-level downloads because global files are large, although a complete-world download is also available. (gadm.org)
GADM’s geographic model does not necessarily match a simple list of sovereign states. Its documentation explains that a GADM “country” is an entity with an ISO country code and may include territories or other entities that are not sovereign states. The project also says it aims to represent de facto administrative situations and does not intend to express an opinion on sovereignty disputes. (gadm.org)
- •Geographic extent: global, organized by country or territory.
- •Administrative depth: level 0 plus up to five subdivision levels, varying by location.
- •Current official version identified on the data page: 4.1.
- •Reported size of the current release: 400,276 administrative areas.
- •Update cadence: not clearly published as a regular schedule.
Formats and access methods
GADM’s world download page provides a complete-world GeoPackage, a geodatabase option, and a GeoPackage organized as six separate layers by subdivision level. Country pages provide country-specific downloads, which are generally more manageable for local projects. (gadm.org)
The official formats page describes GeoPackage as a general vector-data format readable by GIS software and spatial packages in Python and R. It also documents Shapefile, Google Earth KMZ, GeoJSON, and R-oriented access through the geodata package. (gadm.org)
- •Country download: recommended by GADM for reducing file size and simplifying processing.
- •World download: available as a large complete database or by level.
- •GeoPackage: stated standard format for the current global download.
- •Shapefile: widely compatible but split across multiple files and subject to format limitations.
- •GeoJSON: useful for web mapping and JavaScript applications.
- •KMZ: suitable for Google Earth visualization.
- •R access: available through the geodata package’s GADM function.
A defensible GADM GIS analysis workflow
Start by defining the administrative question. Decide whether the analysis needs countries, first-level regions, districts, or the deepest available level. Do not infer that level 2 in one country is directly equivalent to level 2 elsewhere. Select the country or world file, record the GADM version, and preserve the original download before any simplification or repair.
Inspect the coordinate reference system, geometry validity, multipart features, antimeridian behavior, and attribute encoding. Reproject into an appropriate projected coordinate reference system before calculating distance, area, buffers, or density. For global maps, keep the geographic source data intact and create a separate visualization copy with documented simplification.
- •Choose the required administrative level and geographic scope.
- •Record release version, download date, source, coordinate reference system, and processing steps.
- •Validate geometries before overlays or area calculations.
- •Use projected coordinates for metric calculations.
- •Prefer stable identifiers and versioned crosswalks over name-only joins.
- •Compare high-consequence results with national or sector-specific authoritative boundaries.
License, limitations, and suitable use
GADM states that its data is freely available for academic and other non-commercial use. Redistribution and commercial use are not allowed without prior permission. The license page separately notes that data for Austria is covered by a different Creative Commons Attribution-ShareAlike 2.0 license. These terms should be reviewed before incorporating GADM into a public product, commercial service, redistributed download, or hosted API. (gadm.org)
Boundary data also has semantic limitations. GADM is a harmonized global resource, not a guarantee that every polygon is the legally controlling boundary for a particular government program. Administrative units can change, names can vary, and GADM’s representation of disputed or de facto areas may not match another institution’s policy. Its own metadata explains that when an area changes, new codes may be assigned and older codes may no longer be used. (gadm.org)
- •Best fit: regional mapping, spatial joins, clipping, aggregation, and comparative analysis.
- •Poor fit: address lookup, routing, parcel mapping, road-network analysis, or detailed physical-feature inventories.
- •Required caution: license restrictions, boundary disputes, changing administrative units, and inconsistent meanings of subdivision levels.
Questions teams ask
What is GADM used for in GIS?
GADM is used to represent administrative areas as polygons so analysts can map regions, clip other datasets, join observations to countries or subdivisions, calculate regional summaries, and compare geographic indicators. It is a boundary dataset rather than a road, address, routing, or building dataset.
Which formats can I download from GADM?
The official GADM documentation describes GeoPackage, Shapefile, GeoJSON, Google Earth KMZ, and R-oriented access through the geodata package. The global download page also identifies a geodatabase option and GeoPackage downloads organized by subdivision level. GeoPackage is the stated standard format for the current global data.
Is GADM free for commercial use?
Not by default. GADM states that the data is freely available for academic and other non-commercial use, but redistribution or commercial use is not allowed without prior permission. Austria is identified as an exception with a different Creative Commons Attribution-ShareAlike 2.0 license. Review the official license before using GADM in a commercial product or redistributed service.
How often is GADM updated?
A regular update cadence is not clearly stated on the official pages reviewed. The official data page identifies version 4.1 as current and references a planned version 5 release in January 2026, but users should not treat that statement alone as evidence of a completed or recurring release schedule. Record the exact version and download date in every analysis.
Can GADM boundaries be used for legal or official reporting?
They may be useful as a reference or exploratory layer, but GADM should not automatically be treated as the legally controlling boundary source. For elections, taxation, cadastral work, emergency response, regulatory reporting, or other high-consequence applications, compare GADM with the relevant official national or sector-specific boundary dataset.
Keep exploring
gadm download and formats
A complementary guide focused specifically on obtaining GADM files, choosing formats, and handling country versus world downloads.
census acs analysis workflow
A related workflow showing how administrative geographies can be used to organize and analyze demographic and socioeconomic estimates.
copernicus dem analysis workflow
A contrasting spatial-analysis workflow that combines regional boundaries with raster elevation data for terrain and Earth-surface analysis.
Sources
GADM data
Official source for the current version, reported number of administrative areas, country and world download guidance, and stated usage restrictions.
Open sourceGADM download world
Official source for global GeoPackage, geodatabase, and level-separated download options.
Open sourceGADM metadata
Official documentation for identifiers, names, administrative types, validity fields, remarks, and GID behavior.
Open sourceGADM file formats
Official documentation for GeoPackage, Shapefile, GeoJSON, KMZ, and R-oriented access.
Open sourceGADM license
Official licensing terms for academic, non-commercial, commercial, and redistribution use.
Open source