Why GPS Altitude Is So Inaccurate (and What the Numbers Actually Mean)

Stand on a beach and your GPS may confidently report an altitude of −25 meters. Hike a summit marked 1,000 m and your watch shows 1,043 m. Horizontal GPS is good to a few meters — so why is the vertical number so unreliable? Two independent reasons: satellite geometry and two different definitions of "zero."

Reason 1: All the Satellites Are Above You

Horizontal position benefits from satellites spread across the whole sky — east, west, north, south. Vertical position does not get the equivalent: there are no satellites below you to bracket your altitude from underneath. Every ranging sphere intersects your position from above the horizon, so the vertical component of the solution is geometrically weak.

This asymmetry is captured in the dilution-of-precision numbers receivers compute: VDOP (vertical) typically runs 1.5–3× worse than HDOP (horizontal) in identical conditions. If your horizontal fix is good to 5 m, expect 10–15 m vertically on a good day — worse near buildings or terrain that blocks low-elevation satellites.

Atmospheric delay compounds this: signals from low-elevation satellites cross more ionosphere and troposphere, and those satellites disproportionately shape the vertical solution.

Reason 2: Which "Zero" — Ellipsoid or Sea Level?

Even a perfect measurement can show a "wrong-looking" altitude, because there are two zero references in play:

• The WGS84 ellipsoid — the smooth mathematical spheroid GPS computes against. Raw GPS altitude is height above the ellipsoid.
• The geoid (mean sea level) — the lumpy equipotential surface that actual sea level follows, shaped by Earth's uneven gravity.

The gap between the two — called geoid undulation — is anything but small: it ranges from roughly −106 m south of India to +85 m near New Guinea. If your device reports raw ellipsoidal height, a beach can legitimately read tens of meters negative.

elevation above sea level = GPS ellipsoidal height − geoid undulation (N)

Modern phones apply a built-in geoid model (such as EGM96 or EGM2008) before displaying altitude, but the applied model's local error plus the geometric weakness above still leaves vertical readings noticeably rougher than horizontal ones. Dedicated hiking devices often sidestep GPS entirely for altitude, using a barometric altimeter calibrated at known elevations — pressure sensing is smoother and more responsive for climb tracking, though it drifts with weather.

What Each Number Is Good For

Practical advice: treat consumer GPS altitude as an estimate with a ±20 m band, never as a precise elevation. For anything where vertical truth matters — drainage, construction, aviation minimums — barometric or survey-grade equipment is the tool.

The Takeaway

Horizontal coordinates and altitude come from the same satellites but are not created equal: geometry favors the horizontal, and the vertical answer additionally depends on which zero you mean. The full picture of what degrades GPS readings — atmosphere, multipath, geometry — is in our GPS accuracy guide, and the fundamentals of the measurement itself are in how GPS works.

Your latitude and longitude, meanwhile, remain the dependable part: view your current fix in every format with the GPS coordinates finder, or convert readings with the coordinate converter.