Read an elevation profile without misreading the climb

Separate ascent from height difference

Imagine a profile that starts at 200 m, climbs to 500 m, descends to 300 m and finishes at 600 m. Its total ascent is 600 m: two climbs of 300 m. Its descent is 200 m and its net height change is 400 m. Subtracting the start from the finish would miss a third of the climbing.

A loop can end at the same height where it started and still accumulate substantial ascent. That is why our route pages show both distance and elevation gain. The high and low points describe the range of elevation; they do not measure the total work of repeated climbs.

Check both axes before comparing silhouettes

Two charts can look alike while representing very different routes. A compact drawing might stretch 20 km across the same screen width as a 3 km walk. Its vertical axis may cover hundreds of metres rather than a few dozen. Read the distance and elevation labels before interpreting a steep-looking line.

As an arithmetic example, a rise of 100 m over 1 km is an average rise of about 10%. That average can hide flatter stretches and short, sharper climbs. It is not a measurement of the steepest step, and it says nothing by itself about the surface or exposure.

Use the section table to see where climbing accumulates

Below supported profiles, we divide the recorded distance into thirds. Each row adds the rises and falls between elevation samples in that section. When a boundary falls between two samples, we interpolate the height at the boundary and share the change between the adjacent sections.

The table helps distinguish a route whose climbing is concentrated near one end from a route with repeated climbs throughout. Read it in the profile's recorded direction. If you walk the same line in reverse, the last section comes first and ascent becomes descent. The rows are analytical divisions, not named stages or independently surveyed trail sections.

References: How the directory derives elevation and route data

Keep the profile's limitations in view

Our elevations are sampled from a terrain model along stored route geometry. They are not an account of someone walking the path. Sampling and smoothing can omit short changes; errors in the route line can also affect the result. Differences between the table and headline totals can reflect rounding or different treatment of the samples.

Before using a striking peak or dip to plan a stop, locate it on a current map and check what actually exists there. A graph does not establish a viewpoint, suitable rest area or safe water crossing. Use its strength—showing the distribution of recorded elevation—alongside sources that describe conditions on the ground.

References: How the directory derives elevation and route data