Understanding slope
What slope measures, degrees versus percent, how Orbis3D computes it with Horn's method on true ground distances, and what affects the result.
You will learn
- What slope is and how it is expressed.
- How the 3 × 3 Horn method works.
- What cell size, z factor and NoData do to slope.
Prerequisites
The idea
Slope is the steepness of the ground: how much it rises over a horizontal distance, in the steepest direction. It is given as
- an angle in degrees: 0° is flat, 90° would be a vertical wall;
- a percent rise: rise ÷ run × 100. A slope of 45° is 100 %, because the ground rises one metre for every metre across.
| Degrees | Percent | What it looks like |
|---|---|---|
| 2° | 3.5 % | Gentle valley floor |
| 10° | 17.6 % | Steep road |
| 30° | 57.7 % | Steep hillside, avalanche terrain starts |
| 45° | 100 % | Very steep slope |
How Orbis3D computes it
For every cell, Orbis3D looks at its eight neighbours (a 3 × 3 window, named a to i from the north-west corner):
a b c north
d e f
g h i south
It estimates how fast the ground rises to the east and to the north with Horn's (1981) method, the default of GDAL's gdaldem and of ArcGIS:
dz/dx (east) = ((c + 2f + i) − (a + 2d + g)) / (8 · Δx)
dz/dy (north) = ((a + 2b + c) − (g + 2h + i)) / (8 · Δy)
slope = atan( √( (dz/dx)² + (dz/dy)² ) )
Δx and Δy are the true ground sizes of the cell in metres:
- for projected DEMs, the cell size in the CRS unit (feet are converted to metres);
- for geographic DEMs in degrees, the cell size at the latitude of each row on the WGS 84 ellipsoid. A 1 arc-second cell is 30.8 m north–south everywhere but only 26.7 m east–west at 30° N;
- for Web Mercator, corrected by the cosine of the latitude.
Elevations are converted to metres and multiplied by the z factor (1 by default).
## What affects slope- Cell size. Slope from a 30 m DEM is smoother than from a 1 m DEM of the same place; fine details average out. Compare slopes only at the same resolution.
- Working resolution. Orbis3D analyses the working grid. For very large rasters this is reduced (see Optimizing terrain resolution), which also lowers the steepest values.
- Wrong units. Elevations in feet treated as metres give slopes that are too steep. Set the elevation unit in Info ▸ Units and scale.
- Edges and NoData. A cell next to the raster edge or NoData has no complete window. With Compute edges on (the default), missing neighbours are filled the way
gdaldem -compute_edgesdoes; with it off, those cells become NoData. - Vertical exaggeration has no effect: analysis always uses true elevations.
Next
Compute slope on real mountains in Performing slope analysis.