Why your GPS elevation gain doesn't match the trailhead sign
You pass a trailhead sign with a tidy elevation figure printed on it, finish the hike, and your app reports a noticeably bigger number — sometimes by a couple of hundred metres on what was meant to be the same climb. Nothing has gone wrong. A posted elevation gain and a GPS-recorded one are two different measurements of the same trail, built from different source data by different methods, and a gap between them is the normal outcome rather than a sign that either figure is wrong.
The short answer
A sign, map or guidebook usually states a single, smoothed elevation figure worked out once, from a source that already threw away most of the small ups and downs. A GPS recording works the opposite way: it logs an altitude reading many times a minute and adds up every rise between one point and the next, small ones included. Summing lots of small real and near-real climbs almost always comes out higher than a figure that was smoothed before it ever reached the sign, which is why your recorded number is usually the bigger one.
A difference of a few percent is nothing to think twice about. A recorded figure that comes out noticeably higher on a trail known for short, rolling ups and downs is the expected pattern, not a fault in the phone or the app.
How the sign got its number
Posted elevation figures usually come from a topographic source rather than anyone walking the trail with a GPS unit switched on — a contour map, an agency's trail database, or a guidebook author's own older measurement, copied forward from one edition to the next. Contour maps in particular mark height at a fixed vertical spacing rather than continuously, so reading a climb figure off one already skips over anything smaller than that spacing, in much the same way a GPS app's own noise threshold skips small jitters, just decided by the map instead of the phone.
Many posted figures are also closer to net elevation change — the difference between the trailhead and the high point — than to true cumulative gain, especially on guidebook pages that were never trying to be precise about every roller along the way. A trail with several short dips and re-climbs can have a cumulative gain well above its net change, and a sign is more likely to be quoting the smaller, tidier number.
How your recorded number got made
A phone logs altitude many times a minute while it records a route, and elevation gain is built by walking through that log in order and adding up every increase between one point and the next. Nothing about the trail's official profile enters into it — the number comes entirely from what your phone measured on that specific walk, on that specific day.
That includes real small climbs a topo source never itemised — a dip to cross a drainage, a short rise over a rock step, a boardwalk that bobs up and down — and it includes a share of ordinary sensor noise as well, because altitude readings wander by a metre or more even when the ground genuinely is not changing height. Both of those push the total up, and neither one is a mistake in the recording.
Why your number usually comes out higher, not lower
Because the two measurements are asymmetric. A sign's figure has already had its small ups and downs smoothed away by the source it came from, before a human ever wrote it on a board. A GPS recording has not been smoothed at all beyond whatever noise filtering the app itself applies, and it captures every genuine small climb along with a portion of the noise. Add those together against a number that started out simplified, and the recorded total is very likely to land higher.
It is not the only possible direction. A route started from a car park below the marked trailhead, or an app whose noise threshold is set aggressively enough to cut real small climbs along with the jitter, can both pull a recorded figure down instead. Neither changes the underlying point: the two numbers were never measuring the same thing in the same way, so an exact match was never the likely outcome.
Which number to trust, and for what
For deciding whether a hike is a reasonable size for the day you have, the posted figure is good enough, and it is not worth relitigating a sign over a couple of hundred metres either way. For understanding how hard the walk actually was, or comparing it against the last time you did it, the recorded figure is the more honest one, because it reflects the climb your legs actually did rather than a number smoothed for a board at the trailhead.
TrailCam keeps elevation gain alongside distance, moving time and pace for every route in its history, so a fair comparison — this visit against the last one, recorded the same way both times — is a matter of opening two saved routes rather than arguing with a sign. It is free to download.
Questions
- Is my recorded elevation gain wrong if it's higher than the trailhead sign?
- Not necessarily. A posted figure is usually a smoothed number from a topographic source, worked out once. A GPS recording adds up every rise it actually logged that day, small ones included, so it typically comes out higher. A gap of this kind is the expected outcome, not a fault.
- Why is the sign's number so much rounder than my recorded figure?
- Because it likely came from a contour map or an older survey rather than a device logging altitude continuously. Reading gain off contours only counts crossings at a fixed spacing, which quietly filters out anything smaller — similar in effect to the noise threshold a GPS app applies, just built into the map instead.
- Could my recorded elevation gain ever come out lower than the sign says?
- Yes, though it is less common. Starting the recording below the marked trailhead, or using an app with an aggressive noise filter, can both pull the recorded figure down. It still does not mean either number is wrong — they were never the same kind of measurement.
Recording your own routes
TrailCam is an iPhone app that records your route with GPS, keeps video clips, photos and voice notes pinned to the spot where you took them, and exports the result as GPX 1.1 or CSV. It is free to download.