GADM download and formats: administrative boundaries for global GIS
GADM, the Database of Global Administrative Areas, is a global vector dataset of administrative boundaries from country level through multiple lower-level subdivisions. The official GADM site currently identifies version 4.1 as the current release and reports 400,276 administrative areas. Users can download data by country or for the entire world in GeoPackage, geodatabase, Shapefile, GeoJSON, KMZ, and R-compatible formats. GADM is useful for clipping, aggregation, spatial joins, map production, and organizing other geographic data by administrative hierarchy. Its principal constraints are irregular update timing, version-sensitive boundary definitions, uncertainty around disputed areas, and a license that permits academic and other non-commercial use but restricts redistribution and commercial use without permission.
GADM is a practical boundary dataset for analysts who need a consistent way to organize geographic information by country, province, district, municipality, or other administrative subdivision. It is not a basemap, address database, road network, imagery archive, or time series. Its role is narrower and highly useful: provide polygon geometries and administrative attributes that let other data be grouped, clipped, compared, and mapped by jurisdiction. The official project describes GADM as an effort to map the administrative areas of all countries at all levels of subdivision, with high spatial resolution and extensive attributes. (gadm.org)
How EDK fits
For: GIS analysts, researchers, cartographers, data engineers, Earth-observation practitioners, and developers who need global or country-level administrative polygons for spatial joins, regional summaries, map production, or geographic indexing.
Administrative boundaries are one of the clearest ways to make the physical world computable. GADM supplies a jurisdictional frame: a location, raster cell, road segment, building, environmental feature, incident, or observation can be assigned to the country or subdivision that contains it. That makes GADM useful as one layer in a broader world model, while also clarifying its limits. GADM describes administrative organization, not everything physically present in a place. It does not replace roads, buildings, imagery, terrain, hydrology, addresses, or current civic records. In an E2-oriented workflow, GADM can provide the regional hierarchy used to filter, aggregate, compare, and summarize other location data. The boundary layer answers “which administrative area contains or intersects this feature?”; a wider geographic system is needed to answer what the feature is, where it is precisely, how it changed, or how it relates to nearby infrastructure and natural systems.
- •Use GADM polygons as a regional index for grouping physical-world features—such as roads, buildings, waterways, public assets, environmental observations, or service records—by country and administrative level before calculating counts, areas, densities, or comparisons.
- •Combine administrative containment with geographic computation: filter features inside a selected province or district, rank subdivisions by measured activity, compare conditions across jurisdictions, or aggregate observations upward through a country-to-subdivision hierarchy.
- •Use GADM as a boundary reference when connecting administrative geography to a broader searchable representation of places, infrastructure, imagery, and public data, while preserving the distinction between administrative units and the physical features located within them.
Dataset profile
Formats
GeoPackage
Esri geodatabase
ESRI Shapefile
GeoJSON
Google Earth KMZ
R-compatible files, including formats used with R spatial workflows
Access methods
Download individual countries from the official GADM country-download interface.
Download the entire world as a GeoPackage or geodatabase.
Download world data as separate layers by subdivision level in a GeoPackage.
Use older-version downloads when reproducibility requires GADM 4.0, 3.6, or 2.8.
Use documented R spatial tooling such as the geodata package where appropriate, while still recording the underlying GADM version and license terms. (gadm.org)
Quality and limits
Administrative boundaries and names can change between releases; retain the GADM version and download date.
Administrative levels are not directly comparable across countries because institutional structures and subdivision depth differ.
The dataset may not reflect the most recent administrative reforms if they were not incorporated into the confirmed release.
Disputed, exceptional, or politically sensitive boundaries require comparison with authoritative national, legal, or institutional sources.
Large global files can require substantial storage, memory, indexing, and geometry-processing time.
Polygon boundaries are not substitutes for cadastral, electoral, legal, maritime, ecological, watershed, or operational boundaries.
GADM does not provide current physical features such as roads, buildings, addresses, infrastructure condition, imagery, or service activity.
Commercial use and redistribution are restricted by the GADM license unless permission is obtained. (gadm.org)
Analysis workflows
Select the country or global package and administrative level that matches the reporting question.
Record the GADM version, source page, download date, file name, and license status.
Load the GeoPackage or another suitable format into QGIS, ArcGIS, Python, R, or a spatial database.
Inspect the coordinate reference system, layer structure, field names, geometry validity, multipart features, and empty or exceptional geometries.
Use spatial containment or intersection to assign points, lines, polygons, raster cells, or observations to administrative units.
Aggregate counts, areas, rates, or measurements by GID and administrative level, retaining country context and the original geometry vintage.
Clip imagery, environmental layers, public datasets, or physical-feature inventories to administrative extents.
Validate important results against local or national boundary sources, especially for legal, operational, or high-stakes decisions.
For historical comparisons, construct or obtain a crosswalk between boundary vintages rather than assuming that current GADM units match past geographies.
Publish maps and derived statistics with clear attribution, version information, and a statement of the boundary limitations.
Value inside EDK
What GADM contains
GADM stands for the Database of Global Administrative Areas. Its purpose is to represent administrative areas for countries and their subdivisions, including country-level units and progressively lower levels where data are available. The project’s official description emphasizes coverage across countries and subdivision levels, rather than a single fixed administrative scheme used everywhere. That matters because the meaning of “level 1,” “level 2,” or “level 3” can differ from one country to another. (gadm.org)
The dataset is primarily polygon geometry accompanied by administrative attributes. The metadata documentation describes fields for names, variant and non-Latin names, administrative types, country codes, HASC identifiers, validity fields, remarks, and GADM identifiers such as GID. GID values encode a hierarchical path through the administrative structure, for example a country code followed by subdivision components. The metadata also notes that identifiers can change when an area is split or substantially reorganized, so identifiers and versions should be retained in any reproducible project. (gadm.org)
- •Vector polygons for countries and lower-level administrative subdivisions.
- •Attributes for names, administrative types, codes, alternate names, and selected validity or editing notes.
- •A hierarchy that can support country-to-subdivision aggregation, though level meanings vary by country.
- •A global reference layer for spatial joins, clipping, thematic mapping, and regional indexing.
Geography, hierarchy, and update cadence
The official GADM data page currently identifies version 4.1 as the current version and reports 400,276 administrative areas. The same page says version 5 was expected in January 2026. Because the page continues to identify 4.1 as current, the defensible description as of September 9, 2026 is that 4.1 remains the latest version confirmed by the official GADM site; the availability of a subsequent release is not established by that page. (gadm.org)
GADM’s release pattern is not described by the project as a fixed monthly, quarterly, or annual update service. The metadata explains that the version changes when there is a major overhaul of divisions in a country, such as a new subdivision system. This makes GADM suitable for versioned analysis, but not for assuming that every boundary change has been incorporated immediately. Analysts working with historical data should record the GADM version and the date of download, then check whether the boundary vintage matches the observations being analyzed. (gadm.org)
- •Confirmed official current version: 4.1.
- •Reported coverage: 400,276 administrative areas across the dataset’s hierarchy.
- •Update cadence: irregular and driven by major boundary revisions rather than a guaranteed schedule.
- •Recommended practice: store the version, download date, source URL, and any project-specific boundary decisions.
Formats and access methods
The official GADM site recommends downloading by country. Country downloads reduce file size and make it easier to select only the geography and administrative depth needed for a project. GADM also provides world-wide downloads, but the project warns that these are large files and may take a long time to download. (gadm.org)
GeoPackage is GADM’s stated standard format. It is a strong default for modern desktop GIS and scripted workflows because it can store spatial layers and attributes in a single database file. GADM also documents geodatabase downloads, Shapefiles, GeoJSON, KMZ files for Google Earth, and R-compatible files. The formats page specifically notes support through QGIS, ArcGIS, Python spatial packages, and R packages such as sf and terra. (gadm.org)
- •Country downloads: recommended by GADM for most users.
- •World download: available, but large and less convenient for selective workflows.
- •GeoPackage: GADM’s standard format and a strong default for modern GIS.
- •Geodatabase: useful in Esri-centered workflows.
- •Shapefile: broadly compatible, but split across multiple files and subject to legacy field and naming constraints.
- •GeoJSON: useful for web mapping and JavaScript-based applications.
- •KMZ: useful for viewing and sharing in Google Earth.
- •R-compatible files: useful for analysis with the R spatial ecosystem.
Suitable GIS workflows
GADM works well as a boundary foundation for spatial joins. An analyst can assign point observations to the containing administrative polygon, intersect lines or polygons with jurisdictions, or summarize raster values by administrative area. Common examples include calculating population or environmental indicators by province, clipping satellite-derived layers to a country, producing choropleth maps, and comparing the distribution of assets or events across districts.
A defensible workflow begins with the question, not the file format. First select the administrative level that matches the reporting need. Next download the relevant country or world package and record the release. Inspect the geometry and attributes, confirm the coordinate reference system, repair or flag invalid geometries where appropriate, and test a few known places against an authoritative source. Then join the target data using spatial containment or intersection, not merely a name string, unless a stable code relationship has been verified.
- •Country and subdivision mapping.
- •Point-in-polygon assignment of observations to jurisdictions.
- •Clipping imagery, raster products, and vector layers by administrative extent.
- •Zonal statistics and regional aggregation.
- •Cross-country thematic mapping and dashboard production.
- •Spatial indexing for querying or summarizing other physical-world datasets.
- •Preprocessing boundaries for routing, regional comparison, or geographic reporting workflows.
License, limitations, and suitable use
GADM states that its data are freely available for academic and other non-commercial use. Redistribution and commercial use are not allowed without prior permission. The license page also identifies a different license for Austria, so users should read the current license terms rather than applying a blanket assumption to every country. (gadm.org)
The license is a central operational constraint. A research team may be able to use GADM to create maps and publish figures, while a commercial application, data product, hosted service, or redistributed derivative may require permission. Before embedding GADM files in a public repository or shipping them inside an application, obtain a legal review of the intended use and check the project’s current terms.
- •Verify the license before commercial use or redistribution.
- •Preserve the exact GADM version used for reproducibility.
- •Check geometry validity and coordinate reference systems before analysis.
- •Validate important boundaries against national or institutional sources.
- •Do not treat administrative polygons as a substitute for cadastral, legal, electoral, or operational boundary products.
- •Do not infer current conditions, physical assets, or infrastructure from administrative geometry alone.
Questions teams ask
What is the latest confirmed version of GADM?
The official GADM data page currently lists version 4.1 as the current version and reports 400,276 administrative areas. It also says version 5 was expected in January 2026, but the same official page continues to present 4.1 as current. As of September 9, 2026, version 4.1 is therefore the latest version confirmed by the official site. (gadm.org)
Should I download GADM by country or for the whole world?
Use a country download when the project concerns one or a limited number of countries. GADM explicitly recommends downloading by country because the world-wide files are large. Use the global package when you need a single consistent database and have the storage, processing capacity, and workflow controls to manage it. (gadm.org)
Which GADM format should I use?
GeoPackage is the best general-purpose default because GADM identifies it as the standard format and it works with common GIS software and spatial libraries. Choose GeoJSON for web mapping, KMZ for Google Earth visualization, Shapefile for legacy interoperability, geodatabase for Esri-centered workflows, and R-compatible files when working directly in R. (gadm.org)
Can GADM be used in a commercial product?
Do not assume so. GADM’s license says the data are freely available for academic and other non-commercial use, while redistribution or commercial use is not allowed without prior permission. Review the current license and contact the project before incorporating the data into a commercial application, hosted service, or redistributed dataset. (gadm.org)
Is GADM a time series of changing administrative boundaries?
No. GADM is distributed as versioned releases, and its metadata explains that versions change when there is a major overhaul of divisions. It should not be treated as a continuously updated historical boundary archive. For time-series analysis, retain the boundary vintage and investigate crosswalks or historical sources when jurisdictions change. (gadm.org)
Keep exploring
Sources
GADM data
Official current-version statement, reported area count, recommended country downloads, planned release note, and licensing summary.
Open sourceGADM file formats
Official documentation for GeoPackage, Shapefile, KMZ, GeoJSON, R-compatible files, and supported GIS ecosystems.
Open sourceGADM license
Official terms for academic and non-commercial use, redistribution, commercial use, and the Austria-specific license note.
Open sourceGADM metadata
Official attribute definitions, hierarchy identifiers, validity fields, remarks, and explanation of version and identifier changes.
Open sourceGADM download world
Official information about global downloads, GeoPackage and geodatabase packages, layered downloads, and the size-related recommendation to download by country.
Open source