All posts
Route craft ·6 December 2025 · 9 min read

Reading an elevation profile: the picture is not to scale

The Moveee team

Free coaching · a real route for every ride

Every route planner draws you a little mountain range along the bottom of the screen, and every rider has learned to glance at it and form an opinion. That opinion is frequently wrong, because the picture is not drawn to scale and was never going to be.

Profiles are not lying to you deliberately. They are solving an unsolvable presentation problem — showing a few hundred metres of height across tens of kilometres of distance in a box the shape of a letterbox. Here is what that distortion does, and how to read past it.

The same climb, drawn twice

Below is one climb: 5 km long, gaining 300 m, an average of 6%. Nothing about the road changes between the two pictures. Only the height of the box does.

Drawn in a tall box

0 km 5 km

"That looks brutal."

Drawn closer to true scale

0 km 5 km

The road your tyres are actually on.

Both pictures are honest representations of the same data. The right-hand one is closer to what you would see standing at the bottom — which is why a climb that looked terrifying on screen so often turns out to be an ordinary drag, and occasionally why one that looked trivial turns out to have a 15% wall in it.

Four things a profile gets wrong

The vertical axis is exaggerated

A 20 km ride with 400 m of climbing is drawn in a box perhaps 600 pixels wide and 150 tall. To make 400 m visible at all, the vertical scale is stretched — often by a factor of twenty or more. Every profile you have ever looked at is a cartoon of the road.

Averaging hides the steep bits

A profile drawn from points every 500 m shows a 6% average where the road actually holds 200 m at 14%. The ramp that breaks you is frequently invisible at the zoom level you planned at.

Total ascent depends on how it was calculated

Two platforms can report the same GPX as 1,180 m and 1,460 m, because they smooth the elevation data differently. Comparing a number from one service against one from another tells you very little.

Barometric and GPS elevation disagree

Your head unit's barometer drifts with the weather; GPS elevation is noisy. Neither is wrong exactly, but they will not match each other or the route you planned.

The second one is the one that actually hurts. Averaging a climb over long sample distances turns a punchy road into a smooth ramp on screen, and the steep sections reappear only when you are on them. If a climb is described by locals as harder than its average suggests, believe the locals over the picture.

How to read one properly

Look at the axis numbers, not the shape

Before reacting to a profile, read how much total ascent it covers and over what distance. A wall-shaped profile with 300 m of climbing is a pleasant afternoon.

Zoom into each climb separately

The only honest way to see gradient. Most planners will show a single climb's own profile — that view is trustworthy in a way the whole-route view is not.

Do the arithmetic on the climbs that matter

Metres of ascent divided by horizontal metres gives the average gradient. Two kilometres gaining 160 m is 8%. That number, not the picture, is what your legs will experience.

Convert ascent into time, not fear

A rough rule: for a fit amateur, every 100 m of climbing adds several minutes over riding the same distance flat. Total ascent is mostly a duration problem.

Cyclists riding on an open road
No profile has ever accurately conveyed what a road feels like. The numbers underneath one can.

The numbers worth extracting before an event

  • Total ascent, and where it is. 2,000 m spread evenly across 160 km is a completely different day from 2,000 m in three climbs.
  • The length and average gradient of each significant climb. These are the only two numbers you can pace from — see how to pace a climb with power.
  • Where the steepest kilometre sits. A 14% kilometre at hour five needs planning for; the same kilometre at hour one does not.
  • What comes immediately after each climb. A descent is recovery. A flat exposed valley into a headwind is not, and riders regularly blow up there rather than on the climb itself.

Working those out in advance turns a profile from a source of anxiety into a plan. It is the same preparation that pacing a gran fondo with power is built on, and it takes about ten minutes.

Better than reading it: ride it

The most reliable way to understand a profile is to have already ridden the road, and for an event abroad that is usually impossible. The next best thing is riding the actual GPX indoors, where the gradients arrive at your legs in the right order at the right steepness — which is a far more informative preview than any picture.

Moveee Indoor takes a route you have saved and rebuilds it as a 3D road in a browser tab, with the trainer resistance following the real gradient. Ride the last 20 km of your target event a fortnight out and you will know exactly where the hard part is — which is knowledge no profile can give you. Previewing a race course indoors covers how to set that up.

And when you are building routes rather than reading someone else's, Moveee's Route Engine works from the actual elevation and surface data rather than the drawing — see how to build the perfect cycling route.

Sources 5

Where this article summarises a study, the study itself is linked — not a write-up of it.

  1. 1 Menaspà P, Impellizzeri FM, Haakonssen EC, Martin DT, Abbiss CR Consistency of commercial devices for measuring elevation gain · International Journal of Sports Physiology and Performance · 2014
  2. 2 Ranacher P, Brunauer R, Trutschnig W, Van der Spek S, Reich S Why GPS makes distances bigger than they are · International Journal of Geographical Information Science · 2016
  3. 3 Aeronautical Information Manual, Chapter 7 Section 2: Barometric altimeter errors and setting procedures · Federal Aviation Administration · 2026
  4. 4 Martin JC, Milliken DL, Cobb JE, McFadden KL, Coggan AR Validation of a mathematical model for road cycling power · Journal of Applied Biomechanics · 1998
  5. 5 Swain DP A model for optimizing cycling performance by varying power on hills and in wind · Medicine & Science in Sports & Exercise · 1997
Put it into a route

Build a route that is actually worth riding

The Route Engine works from real surface and elevation data and favours quiet roads, so it finds the lanes a fastest-way-there app routes you straight past. Give it a distance and a direction and it does the rest.

Build a route

Keep reading

Route craft

How to read the wind forecast for cycling (and stop riding into it both ways)

Wind costs a cyclist more than rain ever will, and the weather app's little arrow doesn't tell you what it'll do to your loop. Why headwinds punish you harder than tailwinds repay you, which way to ride your route, what 20 vs 40 km/h actually feels like, and how to plan around gusts before you clip in.

Route craft

The same roads backwards: why reversing a route changes the ride

The descent you know by heart is a climb you have never paced, the tailwind is now waiting for you at the wrong end, and the low winter sun is in your eyes at every junction. Why the loop you have ridden forty times is still one ride you haven't done.

Route craft

Navigating without a screen

Every rider eventually has the same afternoon: 80 km out, battery dead, phone on 4%. Five methods in the order you will use them, and why learning the shape of a route beats learning its turns.

Route craft

How to find good roads in a place you've never ridden

Reading a map for gradient and surface, using heatmap data without following the crowd, avoiding the trunk road that looks like a shortcut, and sanity-checking a route before you commit a day to it.

Route craft

Planning gravel routes: reading the surface data

The difference between a superb gravel loop and four hours of pushing is usually a few hundred metres of surface nobody recorded. What the OpenStreetMap surface tags actually mean, which one is a coin toss, and the four checks before you commit.

Route craft

Planning a mountain day: passes, weather windows and the descent home

The col may still be under snow in June, the storms build over the summit by early afternoon, and the 24 °C valley is 10 °C at the top before wind chill. A big mountain day is a planning problem before it is a fitness problem.

Route craft

Loop, out and back, or point to point?

Most riders default to one route shape without deciding to. The shape changes what a ride is good for — and for windy days and interval sessions, the usual favourite is clearly the wrong choice.

Route craft

Prekmurje: Slovenia's flat corner, for the days you don't want a climb

The Mura route, 600 km of signed asphalt on the plain, and the driest climate in the country: why Prekmurje is where Slovenian riders go for long steady hours and winter miles

Route craft

Gravel vs road: how to pick the right surface for every ride

Two disciplines, one love of riding. Here's an honest look at gravel vs road — the bikes, the skills, the training value — and how to choose for any given day.

Route craft

Winter route design: ice, shade and the roads that thaw first

In January the north-facing lane stays frozen until lunchtime and the valley bottom is colder than the hill above it. Designing routes around aspect, cold-air drainage, gritting priority and the hours of daylight you actually have.

Route craft

Bikepacking route planning: water, resupply and daylight

Loaded, on unknown surfaces, your daily distance is not your road distance. How to plan around water, shops and daylight — the three things that actually decide whether a bikepacking day works.

Race prep

Pre-race openers: the day-before session that wakes your legs up

Complete rest the day before an event often leaves you feeling flat. What an opener session does, what it should look like, and how long before the start it's worth doing.

Ready to ride with a plan?

Connect Strava and get your first three-week block today — free.

Continue with Strava