Maps · Chapter 19

Elevation Profile Reader

An elevation profile is height plotted against distance. Total ascent adds up every climb; net gain is just finish minus start. And most profiles stretch height, so slopes look much steeper than they are.

Home › Calculators › Maps › Elevation Profile Reader

Opens on Chapter 19’s first worked example: the Ridge Trail from its contour crossings: 230 m at Fern Junction, then 250, 300, 350 … 650 m, to 699 m at 2.06 km.

1. Points along the walk
2. Vertical exaggeration
3. An average
Enter your numbers, then press Work it out.

How it works

Read each contour crossing’s distance along the route off the map and write it beside its height; those pairs are the profile. Each piece’s slope is its rise ÷ its run. Total ascent adds every rise and ignores the drops; total descent adds the drops; net gain is the last height minus the first. A graph’s vertical exaggeration is (ground meters per cm across) ÷ (meters per cm up): with 100 m per cm across and 20 m per cm up, heights are stretched 5 times, so a 22.8% trail looks like 114%.

From the book, Chapter 19. The Ridge Trail’s crossings: 250 m at 0.10 km, 300 at 0.34, 350 at 0.59 … 550 at 1.43. Its gentlest 50 m takes 0.25 km, its steepest 0.13 km. Drawn 100 m per cm across and 20 m per cm up, heights are stretched 5×: 22.8% looks like 114% (48.7°). Owl Ridge: net 47 m down, 39 m of ascent, 86 m of descent. Cormac’s 610 m over 42 km averages 1.5%. Imogen’s phone drew the River Walk at 613.3 m per cm across and 3.5 m per cm up: stretched about 175 times. Every chapter and its tool →

Numbers may use commas (25,000) and a scale may be typed as 1:25,000. The Thimble Hills, their map and every place on it are invented for the book. This tool does arithmetic only: it doesn’t know where you are and can’t tell you whether a walk is safe; check local information for any real place. Everything stays in your browser: no sign-up, nothing stored or sent.