Framework project: Digital Elevation Models (DEMs)

GDAL Terrain analysis II (Arctic DEM)

Introduction

The relative variations in topography is highly scale sensitive, and also the key for categorising different geomorphological elements (plains valleys, peaks etc), as well as for determining landscape hydrological properties (recharge and discharge areas, channels etc). From a Digital Elevation Model (DEM), the relative variation can be calculated by comparing a single cells with its neighbours. gdaldem includes three different measures on the relative topographic variations that can be accessed via the Framework:

  • Topographic Position Index (TPI),
  • Terrain Ruggedness index (TRI), and
  • Roughness index (RI)

If you are looking for deriving slope, aspect or hillshade or from DEM, this is covered in the previous post.

Overview

This post covers the processing of TPI from DEM data tiled to the modis system. The processing of Terrain Ruggedness index (TRI) and Roughness (RN), are identical. All the indexes (TPI, TRI, RN) utilize the GDAL DEM utility (gdaldem). In Karttur’s GeoImagine Framework you can set the TPI (TRI or RN) processing to produce destination layers at different spatial resolutions. This is convenient if you are intending to the TPI (TRI, RN) data for e.g. landform classification.

Topographic Position Index (TPI)

The Topographic Position Index (TPI) is defined as the difference between a cell’s elevation value and the average elevation of the neighbouring cells. Positive values mean the cell is higher than its surroundings while negative values means that it is lower. The degree to which it is higher or lower, plus the slope of the cell, can be used to classify the cell into slope position. If it is significantly higher than the surrounding neighbours, then it is likely to be at or near the top of a hill or ridge. Significantly lower values suggest the cell is at or near the bottom of a valley. TPI values near zero could mean either a flat or mid-slope area; the cell slope can be used to distinguish the two.

Framework process and json commands

Framework process for GDAL TPI (other alternatives exist): GdalDemTiles.

All destination layers have default names that builds on the input DEM and the spatial aggregation. Any number of spatial aggregations can be produced with a single command through the radisucsv parameter. The parameter should be given as a comma separated value list in the form of a text string: The default value “1” applies a (1+1+1 = 3 cells square kernel) 3x3 kernel for calculating the DEM index (TPI) for the central pixel. A value of “2” aggregates averages all 2x2 pixels to a single cell and then calculates the index on the average of 3x3 cells originally derived from 6x6 cells. While the analysis is done using reduced resolutions, the produced layers will be in the original resolution to allow direct overlay and analysis.

The json object above produces two (2) TPI compositions, using a 3x3 cells and 9x9 cells (with the latter reduced to 3x3 prior to the analysis). The json will produce TPI layers for all modis tiles covered by the user tract karttur-arcticdemext (corresponding default region = arcticdemext) that was created in one of the previous posts.

The figure below illustrates the TPI for a detailed scene at the two aggregation levels (bottom row).

image image image image
Comparison of Terrain Position index (TPI) at 500 m and 1500 m (bottom row); the top row shows the DEM and the slope for the same region.