Published October 26, 2026 | Version v1

Pre-Built Global VRT Collections of GLO-30 DEM VRTs for WRS-2 and MGRT tiles

  • 1. ROR icon Humboldt-Universität zu Berlin
  • 2. ROR icon Universität Trier

Contributors

  • 1. ROR icon Humboldt-Universität zu Berlin

Description

Pre-Built Global VRT Collections of GLO-30 DEM VRTs for WRS-2 and MGRT tiles

 

Background

This dataset support functionality of FORCE and comprises a collection of vrt files that group Copernicus GLO-30 DEM data for each WRS-2 and MGRT tile.
The  GLO-30 DEM dataset is distributed in six latitude bands Figure 5 in the Product Handbook where each zone has its own specific longitude reduction factor.  This means that the x-resolution (pixel width) of the DEM data depends on latitude, with changes occurring above 50° N and S.
 
[Figure1.png]
Figure1: The x-resolution (in degrees) in relation to latitude. In black - longitude grid spacing in six latitude bands of GLO-30 data. In blue line represents the effective resolution (i.e. the average) of the European VRT mosaic. The red line represents the effective resolution of the global VRT. Image credit: David Frantz
 
Consequently, when multiple DEM tiles are aggregated to a single mosaic or a VRT, its x-resolution will depend on the latitudinal extent of the DEM tiles used to create the said mosaic or a VRT.
 
❗This translates into several issues:
 
DEM VRTs created based on different collections of tiles will likely have different resolutions.
Datasets processed with different DEMs or DEM VRTs will have i) shifts between pixels, and ii) different BOA values. This, in turn, prohibits the reproducibility of FORCE results.
For VRTs spanning regions with low and high latitudes (e.g., continental and global VRTs) the resolution decreases towards the Equator.

[Figure2.png]
Figure 2: Hypothetical effective resolution (in meters) of European (blue) and Global (red) DEM VRT mosaics in relation to latitude. In black - resolution of GLO-30 data distributed in six latitude bands. Image credit: David Frantz

 

Solution

In FORCE, the best way to address these critical issues, is to process each Landsat and Sentinel-2 tile using only these DEM tiles that overlap with the footprint of the processed tile. This functionality has been enabled in FORCE v3.8.01dev through a new parameter in the LEVEL2 parameter file called `USE_DEM_DATABASE` that allows for tile-specific processing.
`USE_DEM_DATABASE` is meant to be used in conjunction with the `FILE_DEM` parameter. Whenever `USE_DEM_DATABASE = TRUE` the `FILE_DEM` needs to point not to a global, or regional VRT but to a folder with a collection of VRTs generated for each Landsat of Sentinel-2 tile.

 

Pre-Built Global VRT Collections

To facilitate the use and adoption of this new way of using GLO-30 data, we provide a ready-to-use global collection of WRS-2- and MGRS-specific VRTs.
The dataset in question comprises:
- MGRT_VRT.tar - global collections of Sentinel-2/MGRT specific VRTs
- WRS_VRT.tar - global collections of Landsat/WRS-2 specific VRTs
The list of GLO-30 tiles essential to process each WRS-2 and MGRT tile was identified based on openly available WRS-2 and MGRT footprints.
> [!IMPORTANT]
> Furthermore, we used 20 km buffer to account for potential deviation from the expected footprint's location.

 

Use

⚠️ The distributed archives include only the VRT files. The Copernicus GLO-30 DEM tiles must already be present in the user's computational environment.
VRTs are built with relative paths and must be placed in a directory located at the same level as the copernicus directory containing the DEM tiles.
Landsat and Sentinel-2 specific VRTs can be deposited in the same parent directory.
#
higher-level-dir
├── DEM_VRT
│   ├── MGRS_T01CDH.vrt
│   ├── MGRS_T01CDJ.vrt
│   ...
│   ├── WRS-2_013001.vrt
│   ├── WRS-2_013002.vrt
│   ...
│   ├── MGRS_T60XWF.vrt
│   ...
│   └── WRS-2_221015.vrt
├── copernicus
│   ├── Copernicus_DSM_10_N00_00_E006_00_DEM.tif
│   ├── Copernicus_DSM_10_N00_00_E009_00_DEM.tif
│   ...
│   └── Copernicus_DSM_10_S90_00_W180_00_DEM.tif
...

 

Special Case: Caucasus Region

Since the GLO-30 tiles from the Caucasus area are under embargo, under the aforementioned link, we provide SRTM tiles from this region (`SRTM_Caucasus.tar`), and respective WRS-2 (`WRS-2_VRT_Caucasus.tar`) and MGRS (`MGRS_VRT_Caucasus.tar`) collections of VRTs.

 

⚠️To allow for a seamless incorporation of the SRTM DEM data, the SRTM tiles from the SRTM_Caucasus.tar need to be placed in a srtm_aster directory located at the same level as copernicus and DEM_VRT directories.

 

#
higher-level-dir
├── DEM_VRT
│   ├── MGRS_T01CDH.vrt
│   ├── MGRS_T01CDJ.vrt
│   ...
│   ├── WRS-2_013001.vrt
│   ├── WRS-2_013002.vrt
│   ...
│   ├── MGRS_T60XWF.vrt
│   ...
│   └── WRS-2_221015.vrt
├── copernicus
│   ├── Copernicus_DSM_10_N00_00_E006_00_DEM.tif
│   ├── Copernicus_DSM_10_N00_00_E009_00_DEM.tif
│   ...
│   ├── Copernicus_DSM_10_S90_00_W180_00_DEM.tif
├── srtm_aster
│   ├── n38_e045_1arc_v3
│   ├── n38_e046_1arc_v3
│   ...
│   └── n41_e049_1arc_v3
...
⚠️Furthermore, the respective VRT files available in the global VRT distribution need to be overwritten with VRTs available in the `WRS-2_VRT_Caucasus.tar` and `MGRS-2_VRT_Caucasus.tar` archives

 

Documentation

The distributed data collection comes with readme.md comprising general information on the dataset. Furthermore, each *.tar* archive available under the abovementioned link comprises a README.MD file with setup guidelines, as well as a *log*.csv file listing all DEM tiles used to create a VRT for a specific WRS-2 or MGRS tile.

Disclaimer

The authors accept no responsibility for errors or omissions in this work and shall not be liable for any damage caused by these.

Funding Information

Funding: This research was funded by the Deutsche Forschungsgemeinschaft (DFG, German Research Foundation) – Project-ID 414984028 – SFB 1404 FONDA.

Citation

Lewińska K.E., Frantz D., Leser U., Hostert P., (2026), Pre-Built Global VRT Collections of GLO-30 DEM VRTs for WRS-2 and MGRT tiles [Dataset], zenodo, 10.5281/zenodo.23532250

Files

Figure1.png

Files (694.7 MB)

Name Size
md5:86ef27176b3ea0c3ac6349a05b74e6ed
5.4 kB Preview Download
md5:96c9413ef61b38ab31ba5d29ffcdf868
11.0 kB Preview Download
md5:ab49756ba8cccb7394ea54bd27d989e3
127.8 MB Download
md5:d18d9c9fd390928c2b1ff5d03ec2a8dd
179.2 kB Download
md5:9e51174a6a9e11acd6feef43d9d5765a
6.1 kB Preview Download
md5:9b1cb586833914a8bda6a031dc383501
416.3 MB Download
md5:4cb51e72475eb5e08131b800828346a7
165.4 kB Download
md5:6c929c0ae27b85822ffab14bdb42d38c
150.2 MB Download

Additional details

Funding

Deutsche Forschungsgemeinschaft
FONDA 414984028