Copernicus DEM: Global Digital Surface Model for GIS and Earth Analysis
Copernicus DEM is a global and European digital surface model produced from TanDEM-X and WorldDEM data, with additional local infill sources. It represents the elevation of the Earth's surface, including terrain, vegetation, buildings, and infrastructure. The dataset is distributed in EEA-10, GLO-30, and GLO-90 instances, with different geographic coverage, resolutions, formats, and access conditions. It is useful for terrain visualization, watershed analysis, orthorectification, slope and aspect calculations, visibility studies, regional modeling, and other raster-based GIS workflows. Because it is a DSM rather than a bare-earth terrain model, analysts must account for the height of vegetation and built structures.
Copernicus DEM is one of the most important elevation datasets in the contemporary geospatial ecosystem. It gives GIS analysts, Earth-observation practitioners, cartographers, and spatial developers a consistent elevation surface that can be used across large regions and, for GLO-30 and GLO-90, worldwide. The dataset is especially valuable when an analysis needs a common elevation reference across countries rather than a patchwork of national terrain products. The name covers several related products. EEA-10 provides 10 metre coverage for Europe and certain French overseas departments. GLO-30 provides worldwide coverage at 30 metre resolution, while GLO-90 provides worldwide coverage at 90 metre resolution. Copernicus describes these products as digital surface models: their elevations include natural and human-made features such as vegetation, buildings, and infrastructure, not only the underlying ground. (documentation.dataspace.copernicus.eu) For location-data work, that distinction matters. Copernicus DEM can help explain the physical setting around a road, building, waterway, settlement, or infrastructure asset, but it should not automatically be treated as a bare-earth elevation layer. The appropriate interpretation depends on the question, the resolution selected, the terrain, and the feature being studied.
How EDK fits
For: GIS analysts, remote-sensing specialists, cartographers, hydrologists, environmental modelers, urban and regional planners, infrastructure analysts, geospatial developers, and researchers who need a standardized elevation surface for Europe or global analysis.
Copernicus DEM contributes a physical-elevation layer to the broader task of finding, understanding, and computing about Earth. A world model needs more than names, addresses, roads, and boundaries: it also needs a representation of how the land and built environment rise, fall, and obstruct movement across space. Copernicus DEM can provide elevation context for physical features such as roads, buildings, rivers, shorelines, facilities, and land-use areas. The connection is strongest when elevation is used as a computation input rather than only as a shaded-relief backdrop. Elevation values can support slope and aspect calculations, terrain-aware proximity analysis, watershed and drainage studies, viewshed modeling, route evaluation, flood-screening workflows, and comparisons between places with different topographic conditions. E2's world-model perspective is relevant here because elevation becomes more useful when it is analyzed together with the other geographic features that describe a place. Copernicus DEM itself does not provide those other layers, and this page does not imply that it does; rather, it is a specialized raster dataset that can add surface-height context to a broader geographic representation.
- •Combine Copernicus DEM elevation with mapped roads, buildings, waterways, and infrastructure to compare terrain conditions around physical assets or regions.
- •Use the raster as an input to geographic computations such as slope, aspect, relief, visibility, watershed, elevation-band, and terrain-aware proximity analysis.
- •Add elevation context to place-level searches so that a location can be understood not only by what is present there, but also by the surrounding physical form of the land and built surface.
Dataset profile
Formats
DGED
DTED
GeoTIFF
32-bit floating-point DGED and INSPIRE data
16-bit signed-integer DTED data
1° × 1° geographic tiles for global DGED and DTED products
Shapefile grid indexes for product and tile discovery. (dataspace.copernicus.eu)
Access methods
Copernicus Browser
Copernicus Data Space APIs
OData catalog and download access
S3-compatible object storage for bulk access
Sentinel Hub Process API for selected DEM processing and outputs
Registration and user-category eligibility may apply, particularly for EEA-10 and some GLO-30 service paths. (documentation.dataspace.copernicus.eu)
Quality and limits
DSM semantics mean that vegetation, buildings, bridges, and infrastructure can be represented in the elevation surface.
Nominal resolution does not guarantee that narrow roads, drainage channels, building edges, or small terrain features are resolved.
Published accuracy values are product-level specifications and should be locally validated for consequential work.
GLO-90 is unsuitable for analyses that require fine local terrain detail.
Resampling to smaller pixels does not create new source information.
Different releases or tile updates should not be interpreted automatically as measured physical change.
Access defaults and eligibility can change, so production workflows should specify the intended DEM instance explicitly. (dataspace.copernicus.eu)
Analysis workflows
Terrain visualization: mosaic the relevant tiles, reproject if needed, and generate hillshade or relief views while preserving source metadata.
Topographic derivatives: calculate slope, aspect, curvature, local relief, and elevation bands at a resolution appropriate to the study area.
Hydrology screening: use elevation to derive approximate flow surfaces and catchments, but inspect DSM artifacts and validate against hydrographic or bare-earth data.
Urban and infrastructure analysis: combine elevation with building, road, utility, and facility layers to evaluate terrain exposure, visibility, access gradients, or construction context.
Viewshed and line-of-sight analysis: use a DSM when vegetation and structures should act as obstructions; use a terrain model instead when the question concerns ground-only visibility.
Regional comparison: aggregate elevation, slope, or relief statistics by watershed, municipality, service area, ecological zone, or other geographic boundary.
Reproducible raster processing: record the product instance, tile identifiers, release information, access date, coordinate transformations, resampling method, and derived operations.
Value inside EDK
What Copernicus DEM contains
Copernicus DEM is derived primarily from the TanDEM-X mission and WorldDEM, with local infill from sources including ASTER, SRTM variants, GMTED2010, TerraSAR-X Radargrammetric DEM, ALOS World 3D-30m, and selected national elevation datasets. The result is a gridded elevation surface intended to be consistent across broad geographic areas. (dataspace.copernicus.eu)
The central technical distinction is between a digital surface model and a digital terrain model. Copernicus DEM describes the surface visible to the radar measurement, which can include tree canopies, rooftops, bridges, towers, and other elevated objects. That makes it useful for some visibility, surface modeling, and Earth-observation workflows, but it can produce misleading results if an analyst assumes every cell represents bare-earth ground elevation.
- •EEA-10: European coverage at 10 metre resolution; access is more restricted than the global products.
- •GLO-30: worldwide coverage at 30 metre resolution, with public availability subject to current access conditions.
- •GLO-90: worldwide coverage at 90 metre resolution and the default DEM instance in some Copernicus Data Space services. (documentation.dataspace.copernicus.eu)
Geography, resolution, and accuracy
The choice between GLO-30 and GLO-90 is a scale and processing decision, not simply a preference for the highest nominal resolution. GLO-30 is generally more appropriate for regional terrain structure, urban and infrastructure context, and analyses where 30 metre cells can represent meaningful variation. GLO-90 is more efficient for continental or global processing, generalized relief, and workflows where the analysis scale is coarser than individual buildings or narrow valleys.
The published specification identifies one-arc-second grid spacing for GLO-30 and three-arc-second grid spacing for GLO-90. It reports absolute vertical accuracy below 4 metres at the 90% linear-error level, relative vertical accuracy below 2 metres on slopes up to 20% and below 4 metres on steeper slopes, and absolute horizontal accuracy below 6 metres at the 90% circular-error level. These are product-level specifications and should not be interpreted as a guarantee of equal performance in every landscape or for every derived analysis. (dataspace.copernicus.eu)
- •Use GLO-30 when regional terrain detail and manageable processing volume are both important.
- •Use GLO-90 when the study area is continental or global, or when the analysis does not justify 30 metre cells.
- •Treat accuracy figures as dataset specifications, not as a substitute for local validation.
Formats and access methods
Copernicus DEM is offered in DGED and DTED product forms. The published technical description identifies GeoTIFF and DTED as file formats, with 32-bit floating-point values for DGED and 16-bit signed integer values for DTED. DGED and DTED global tiles are organized as 1-degree by 1-degree latitude-longitude cells. (dataspace.copernicus.eu)
The Copernicus Data Space Ecosystem provides several access paths. Users can browse the collection, query it through OData, use APIs for processed requests, or obtain bulk data through S3-compatible object storage and temporary credentials. The availability catalog lists the GLO-30 and GLO-90 DGED and DTED collections for OData, S3 access, and the Copernicus Browser. (dataspace.copernicus.eu)
- •Browser access is useful for inspection and discovery.
- •OData and S3-compatible access are suited to tile search and bulk acquisition.
- •API processing can return selected DEM values or imagery-style outputs for a defined area of interest. (documentation.dataspace.copernicus.eu)
- •Check current registration and user-category requirements before designing a production pipeline.
A defensible GIS workflow
A reliable Copernicus DEM workflow begins by defining the physical question and the correct surface model. For terrain visualization, hillshading, slope, aspect, and regional relief, download the resolution that matches the scale of the analysis. For hydrology, inspect whether buildings, vegetation, bridges, or radar artifacts could affect flow-direction or catchment results; a DSM may require conditioning or a different bare-earth source.
Next, identify the relevant product form and tiles. Preserve the original files, metadata, tile names, acquisition or release information, coordinate-reference information, and licensing attribution. Mosaic only the tiles needed for the study area, and avoid resampling to a finer pixel size as if it created new terrain detail. Resampling can make a raster easier to display or align, but it does not improve the source resolution.
- •Define whether the analysis needs a DSM or a bare-earth terrain model.
- •Select GLO-30, GLO-90, or EEA-10 based on geographic extent and analytical scale.
- •Keep source metadata and attribution with every derivative.
- •Validate hydrologic, urban, and infrastructure results against local data when the decision is consequential.
- •Do not infer temporal change merely from different releases or tile versions.
License, attribution, and limitations
The Copernicus Data Space collection page states that GLO-30 and GLO-90 are available worldwide with a free license. It also specifies attribution language for distributing or adapting Copernicus WorldDEM-30 and WorldDEM-90 material. Users should follow the current license and citation guidance supplied with the product rather than assuming that a free license removes attribution obligations. (dataspace.copernicus.eu)
The principal limitation is semantic: Copernicus DEM is a surface model. In forests, dense urban areas, industrial zones, and places with bridges or other elevated structures, the cell value may not correspond to ground height. Another limitation is scale. A 30 metre raster cannot resolve every road embankment, building edge, drainage channel, or narrow ridge, and a 90 metre raster is coarser still.
- •Free worldwide availability does not eliminate attribution and license obligations.
- •DSM values may include vegetation and buildings.
- •Resolution and grid spacing limit what can be inferred about narrow or small features.
- •Access conditions can change, especially for GLO-30 services.
- •No single recurring update schedule was confirmed in the authoritative sources reviewed.
Questions teams ask
Is Copernicus DEM a digital elevation model or a digital surface model?
Copernicus describes it as a digital surface model. It represents the Earth's surface and can include vegetation, buildings, infrastructure, and other elevated features. It should not automatically be treated as a bare-earth digital terrain model. (documentation.dataspace.copernicus.eu)
What is the difference between Copernicus DEM GLO-30 and GLO-90?
GLO-30 is the worldwide 30 metre instance, while GLO-90 is the worldwide 90 metre instance. GLO-30 generally preserves more spatial detail but requires more storage and processing. GLO-90 is more suitable for broad regional, continental, or global workflows where 90 metre cells match the analysis scale. (documentation.dataspace.copernicus.eu)
Can the general public download Copernicus DEM?
The current Copernicus Data Space collection description says that general users can view all instances and download GLO-30 and GLO-90, subject to registration and the applicable access conditions. EEA-10 and some service pathways have more restrictive eligibility. Because access rules can change, users should verify the current Copernicus Data Space requirements before implementing automated downloads. (dataspace.copernicus.eu)
Does Copernicus DEM have a regular update schedule?
A single fixed recurring update cadence was not identified in the authoritative sources reviewed. The collection documentation describes releases and tile-update rationales. For reproducible analysis, record the product identifier, tile information, release details where available, and the date of access. (dataspace.copernicus.eu)
What GIS operations work well with Copernicus DEM?
Common operations include mosaicking, reprojection, hillshading, slope and aspect calculation, contour generation, elevation-band analysis, visibility modeling, zonal statistics, and terrain-aware overlays with roads, buildings, waterways, infrastructure, or administrative areas. Hydrologic workflows require additional care because the dataset is a DSM and may contain elevated features.
Keep exploring
copernicus dem analysis workflow
A focused companion page for building reproducible slope, terrain, hydrology, visibility, and raster-analysis workflows with Copernicus DEM.
copernicus dem download and formats
A focused companion page for Copernicus DEM product identifiers, DGED and DTED formats, tile structure, access routes, and download choices.
Sources
Copernicus DEM - Global and European Digital Elevation Model
Official collection description covering instances, coverage, access, licensing, attribution, formats, accuracy, sources, and specifications.
Open sourceDigital Elevation Model (DEM) Data – Documentation
Official API documentation describing DEM instances, access behavior, processing options, and current GLO-30/GLO-90 service details.
Open sourceCopernicus Contributing Missions – Documentation
Official documentation describing Copernicus DEM as a DSM and listing EEA-10, GLO-30, and GLO-90 coverage and product identifiers.
Open sourceCopernicus DEM Delivery Review Organisation Note / Product Handbook
Technical product handbook covering file formats, tiling, coordinate systems, grid spacing, and accuracy specifications.
Open sourceCopernicus DEM 30m View Service Update
Official August 25, 2026 notice documenting current GLO-30 view-service restrictions and the GLO-90 default behavior.
Open source