Why does elevation gain look low after a short, steep climb?

The short answer

Elevation gain is not read straight off a sensor — it is summed from a string of altitude readings, and before any of that gets added up, the readings pass through some kind of noise filter so an ordinary wobble on level ground does not turn into fake climbing. That filter has to guess which parts of the signal are a real change in height and which parts are just sensor noise, and it mostly does that by treating anything narrow and sudden with suspicion. A short, steep pitch — a rock step, a quick scramble, a rise that is over in a few strides — is narrow and sudden too. Some of it can get smoothed away along with the noise, which is why the number afterward can feel smaller than what your legs just told you.

What a short, steep climb looks like in the raw altitude data

Every app reporting elevation gain is working from the same kind of source material: an altitude value attached to roughly every point along the track. A long, gradual slope shows up in that string as a steady rise spread across dozens or hundreds of points in a row. A short, steep pitch produces a very different shape — a handful of readings jump up quickly, then the ground levels off and the readings flatten right back out just as fast. Looked at purely as a shape in the data, with no sense of what the ground underfoot actually did, that narrow spike is hard to tell apart from the kind of brief, sharp wobble that ordinary GPS or barometric noise produces on level ground.

Why the filter that protects a flat walk also costs a steep one

Any app has to run its altitude readings through some kind of filtering before adding anything to the running total — otherwise a flat, level walk would rack up dozens of metres of gain from sensor jitter alone. That filtering usually works by treating a brief, narrow change with some suspicion: ignoring an up-and-down swing that does not hold for more than a couple of readings, or smoothing the trace so a short spike gets pulled down toward the flatter ground on either side of it. That is exactly the right thing to do to a genuine wobble on level ground. The trouble is that a short, steep climb is shaped like a spike too, so the same smoothing that keeps a flat walk from looking hilly also rounds off part of a real, sharp climb before it ever reaches the total.

Why a long, gradual climb does not lose nearly as much

A climb that unfolds gradually over a long stretch of trail is wide relative to whatever smoothing window the app is using, so filtering only touches its two edges — where the climbing starts and where it levels off — and barely dents the long, steady rise in between. A short, steep pitch is closer in width to the noise the filter is designed to remove, so a much larger share of it falls inside that same window. Two climbs that gain an identical number of metres can end up contributing very different amounts to the final total, purely because of how long each one took to happen, not because either was measured worse than the other.

When it is worth a second look

• A short scramble or rock step that you are confident gained real height barely shows up on the elevation profile, while the gentler stretches on either side of it read clearly — that is the ordinary pattern described above, not a sign anything recorded wrong.
• A hike built from several short, sharp pitches back to back ends with a noticeably lower total than a single long climb you know gained a similar overall height — expected for the same reason, and worth remembering when comparing two very differently shaped routes by elevation gain alone.
• The profile line itself shows a brief, steep jump right where you remember the scramble — that is the real climb visible directly in the recorded data, even if the running total did not fully credit it.
• The gap between what you felt and what the total shows is large and the climb was genuinely long, not short — that pattern points at something else, since a long climb is the one case this particular filtering effect does not explain well.

Where TrailCam fits in

TrailCam draws elevation gain as a profile under the map for every recorded route, both while you are out and again on replay, so a short, sharp rise is something you can see directly on the line rather than judge only from the single total at the end. That profile and the running total are both included when a route is exported as GPX 1.1 or CSV, part of the optional TrailCam Pro upgrade; the app itself is free to download.