GADM: Global Administrative Boundaries for GIS and Spatial Analysis
GADM, the Database of Global Administrative Areas, provides vector boundaries for countries and their administrative subdivisions. It is designed for mapping, spatial joins, regional aggregation, geographic lookup, and analysis that depends on consistent administrative units across countries. The project publishes country-level and worldwide downloads in formats including GeoPackage, Esri Shapefile, GeoJSON, KMZ, and geodatabase. GADM is useful as a boundary reference layer, but it is not an authoritative cadastral, legal, postal, routing, or address dataset. Its licensing also restricts redistribution and commercial use without prior permission.
GADM is a global administrative-boundary dataset for GIS, cartography, and geographic analysis. It represents countries and lower-level administrative areas—such as provinces, states, regions, counties, districts, and municipalities, depending on the country—in polygon vector layers with attributes describing the administrative hierarchy. The project’s stated goal is to map administrative areas for all countries at all subdivision levels, and its website provides both browsable maps and downloadable spatial data. (gadm.org) For analysts, GADM is most valuable when the question is organized around administrative geography: which region contains a location, how many features fall within each province, how indicators compare across districts, or how a global dataset can be grouped into country and subnational units. It can serve as a common geographic frame for joining population, environmental, infrastructure, service, or event data. It should not, however, be treated as a guarantee of legally authoritative boundaries, a property-parcel dataset, or a substitute for national mapping agency data when legal or operational precision matters.
How EDK fits
For: GIS analysts, researchers, cartographers, data engineers, public-interest technologists, Earth-observation practitioners, and developers who need downloadable administrative polygons for country or cross-border analysis.
Administrative boundaries are one of the core ways people organize information about the physical world. GADM does not attempt to model every road, building, address, natural feature, or infrastructure asset; instead, it supplies the geographic containers used to summarize and compare those features. In a broader world-model workflow, GADM polygons can provide the regional structure needed to answer questions such as which districts contain reported service issues, how environmental observations vary by province, or which administrative areas intersect a corridor, watershed, or development zone. The important distinction is that GADM is a boundary layer, not a complete representation of Earth. Its value comes from making geographic aggregation and spatial membership calculations possible when combined with other location data. A system concerned with finding, understanding, and computing about the physical world can use administrative units as one analytical lens among many, while still preserving the underlying places and features being measured.
- •Use GADM polygons as a regional aggregation layer for counting, ranking, or comparing physical-world features—such as roads, buildings, environmental observations, public assets, or reported incidents—by country, province, district, or municipality.
- •Use GADM boundaries for point-in-polygon and intersection workflows that convert geographic coordinates, imagery-derived detections, or mapped features into an administrative context before analysis or reporting.
- •Use GADM as a reference layer when building a broader geographic search or computation workflow, while retaining more detailed source datasets for addresses, transportation networks, parcels, infrastructure, and natural features.
Dataset profile
Formats
GeoPackage (.gpkg)
Esri Shapefile components, commonly distributed in ZIP archives
GeoJSON (.json or .geojson)
Google Earth KMZ
Geodatabase
R access through the geodata package and gadm() function
Access methods
Download spatial data by country from the official GADM website.
Download worldwide data as a global GeoPackage or geodatabase.
Download a worldwide GeoPackage organized into six subdivision or aggregation layers.
Use the official format pages to select a GIS-compatible representation.
Use R’s geodata package for package-based retrieval where appropriate.
Preserve the original archive and record the version, country, format, and download date.
Quality and limits
Boundary authority and accuracy can vary by country, administrative level, and source material.
Administrative hierarchies are not semantically equivalent across countries.
Boundary changes, renamings, reorganizations, and disputed areas can affect longitudinal comparisons.
The data should not be assumed to represent legally authoritative sovereignty, cadastral ownership, postal service areas, or routing jurisdictions.
The official site does not provide a clearly documented regular update schedule.
Worldwide files may be large and require substantial storage, memory, and preprocessing.
License restrictions can prevent redistribution or commercial deployment without prior permission.
Administrative polygons alone do not provide roads, addresses, buildings, imagery, infrastructure, demographics, or other physical-world feature classes.
Analysis workflows
Download the relevant country files or the worldwide GeoPackage, and preserve the original archive as an immutable source artifact.
Inspect layer names, administrative levels, identifiers, names, geometry validity, and coordinate reference system before analysis.
Use point-in-polygon joins to assign coordinates, observations, facilities, events, or detected features to administrative units.
Use polygon intersections to determine which districts or provinces overlap environmental, infrastructure, hazard, imagery, or land-use layers.
Aggregate records by stable identifiers where available, while retaining names and hierarchy fields for display and reporting.
Normalize administrative levels explicitly for cross-country analysis rather than treating ADM1, ADM2, or ADM3 as institutionally identical everywhere.
Reproject into an appropriate projected coordinate reference system before calculating area, distance, density, or other metric quantities.
Validate boundary-sensitive results against national or local authoritative sources when decisions involve law, regulation, property, public administration, or operational deployment.
Combine GADM with detailed physical-world datasets when the analysis requires roads, buildings, addresses, infrastructure, natural features, imagery, or temporal change.
Record the GADM version, download date, source URL, license interpretation, processing steps, and any boundary corrections applied.
Value inside EDK
What GADM contains
GADM provides vector maps of administrative areas for countries and their subdivisions. The dataset is hierarchical: a country may be represented at the national level and then through one or more lower administrative levels, depending on how that country’s government geography is represented. The exact meaning of a level is not globally uniform. An ADM1 layer may correspond to a state, province, department, governorate, or another first-order subdivision; an ADM2 layer may represent a county, district, municipality, or comparable unit.
The official project describes its coverage as administrative areas at all levels of subdivision and says that its data include extensive attributes. The current data page states that version 4.1 delimits 400,276 administrative areas. (gadm.org)
- •Country and national-level polygons.
- •Multiple levels of subnational administrative subdivisions where available.
- •Names, identifiers, and hierarchy-related attributes associated with administrative areas.
- •Downloadable country datasets and worldwide compilations.
Geography, resolution, and update cadence
GADM is global in intended scope and is organized by country or ISO-coded geographic entity. Its resolution is administrative rather than pixel-based: the meaningful unit is the polygon representing a jurisdiction. Within that framework, spatial detail varies by country, administrative level, source material, and version. A small municipality may have a detailed coastline or complex boundary, while a generalized national boundary may be adequate only for regional visualization.
The official site currently identifies version 4.1 as the current version and recommends downloading by country. It also provides a worldwide database for users who need a single global file. (gadm.org)
- •Global intended coverage, organized by country and administrative hierarchy.
- •Polygon detail varies by location and subdivision level.
- •No clearly documented regular update interval.
- •Version and download date should be treated as essential metadata.
Formats and access methods
GADM’s format documentation describes GeoPackage, Esri Shapefile, KMZ, and GeoJSON options. The project identifies GeoPackage as its standard format for general spatial data and offers a worldwide GeoPackage database, a geodatabase, and a worldwide GeoPackage divided into six layers corresponding to subdivision or aggregation levels. (gadm.org)
Country downloads are the recommended approach when an analysis concerns only one country or a manageable group of countries. They reduce download size and make it easier to preserve country-specific attributes and inspect the administrative hierarchy. The worldwide files are useful for global pipelines but can be large and may require more memory, storage, and preprocessing.
- •GeoPackage (.gpkg) for the project’s standard global database.
- •Esri Shapefile, usually distributed as a ZIP archive.
- •GeoJSON for web mapping and lightweight interchange.
- •KMZ for Google Earth.
- •Geodatabase and R-oriented access through the geodata ecosystem.
- •Country downloads or worldwide downloads.
Suitable GIS workflows
GADM works well as a boundary reference layer in desktop GIS, scripting, spatial SQL, and data-engineering workflows. In QGIS or ArcGIS, users can symbolize administrative levels, label regions, clip other layers, and export maps. In Python or R, the polygons can support spatial joins, intersections, dissolves, area calculations, and regional summaries.
A common workflow is point-in-polygon assignment: take coordinates from sensors, facilities, observations, incidents, or imagery detections and determine which GADM unit contains each point. Another is polygon intersection: calculate which administrative areas overlap a flood extent, satellite-derived change polygon, ecological region, transport corridor, or infrastructure footprint. A third is aggregation: group records by GADM identifiers or names to produce country, province, district, or municipality statistics.
- •Point-in-polygon assignment for coordinates and observations.
- •Spatial intersection with imagery, environmental, infrastructure, or hazard layers.
- •Regional aggregation and comparative mapping.
- •Clipping and filtering large geographic datasets.
- •Administrative lookup for dashboards, reports, and map products.
- •Country-level and subnational selection in broader geographic computation workflows.
License, strengths, and tradeoffs
GADM states that its data are freely available for academic and other non-commercial use. It also states that redistribution and commercial use are not allowed without prior permission. Academic research maps and figures are permitted under the conditions described by GADM, but organizations should review the license before embedding GADM data in a product, redistributing derived files, or operating a commercial service. Austria is identified as having a different license arrangement in the GADM license text. (gadm.org)
The strongest advantage is breadth: GADM offers a consistent, downloadable administrative framework across a very large geographic scope. Its range of formats and country-level access options makes it practical for both desktop GIS users and programmatic pipelines. The main tradeoff is that global consistency does not mean identical local authority, semantics, vintage, or legal status. Boundary-sensitive applications require validation against the relevant national or local source.
- •Strength: Broad global coverage across countries and multiple administrative levels.
- •Strength: Practical formats for desktop GIS, web mapping, R, and spatial programming.
- •Strength: Useful hierarchy and attributes for regional joins, filtering, and aggregation.
- •Tradeoff: Redistribution and commercial use are restricted without prior permission.
- •Tradeoff: There is no clearly documented regular update cadence.
- •Tradeoff: Administrative levels and meanings are not directly comparable across all countries.
- •Tradeoff: Boundaries may not be appropriate for legal, cadastral, postal, routing, or high-stakes operational use without validation.
Questions teams ask
What is GADM used for?
GADM is used for mapping and analyzing administrative areas. Common applications include assigning points to countries or districts, summarizing observations by region, clipping geographic layers, comparing subnational areas, and creating maps of administrative hierarchies. It is a boundary dataset rather than a complete geographic database.
Is GADM free for commercial use?
Not by default. GADM states that the data are freely available for academic and other non-commercial use, while redistribution and commercial use are not allowed without prior permission. Review the current GADM license before using the data in a commercial product or redistributing derived datasets. (gadm.org)
What formats does GADM provide?
GADM documents GeoPackage, Esri Shapefile, KMZ, and GeoJSON formats. The project identifies GeoPackage as its standard format for the worldwide database and also provides a geodatabase option. R users can access GADM through the geodata package’s gadm() function. (gadm.org)
How often is GADM updated?
GADM does not publish a clearly defined regular update cadence. The official site currently labels version 4.1 as current and includes a statement that version 5 would be released in January 2026, but I found no authoritative release announcement confirming a newer public version as of September 9, 2026. Record the exact version and download date when using GADM.
Can GADM boundaries be treated as legally authoritative?
Not automatically. GADM is useful for geographic reference and analysis, but the project discusses mapping de facto administrative situations and avoiding positions on sovereignty disputes. For legal, cadastral, regulatory, postal, or operational decisions, consult the relevant national or local authority and validate the boundary definition required for the application. (gadm.org)
Keep exploring
gadm download and formats
A focused companion page for obtaining GADM files, choosing country versus worldwide downloads, and working with GeoPackage, Shapefile, GeoJSON, KMZ, and geodatabase formats.
gadm analysis workflow
A focused companion page for point-in-polygon assignment, spatial joins, aggregation, clipping, hierarchy normalization, and validation of GADM boundaries in GIS workflows.
Sources
GADM — Data
Official source for the currently labeled version 4.1, the stated count of administrative areas, download guidance, and license summary.
Open sourceGADM — About
Official description of GADM’s goal to map countries and administrative subdivisions at all levels.
Open sourceGADM — File formats
Official documentation for GeoPackage, Shapefile, KMZ, GeoJSON, ZIP archives, and R-oriented access.
Open sourceGADM — Download world data
Official source for country-versus-world download guidance, global GeoPackage and geodatabase options, and the six-layer worldwide GeoPackage.
Open sourceGADM — License
Official license terms covering academic and non-commercial use, redistribution, commercial use, and country-specific licensing notes.
Open sourceGADM — What is a country?
Official explanation of ISO-coded entities, de facto mapping, and the handling of sovereignty-related geographic distinctions.
Open source