Geoid Undulation: DGPS Height vs Benchmark Elevation
Geoid Undulation Calculator: H = h - N
Set your GNSS height and undulation, see the elevation that should match a leveled benchmark.
Try a Real, Live Geoid API (US Coverage Only)
This button calls the actual NOAA/NGS Geoid Height web service, a genuine working example of a live geoid API. It does not cover India, its default GEOID18 model is CONUS-only, so this demo is never called with Indian coordinates.
What Geoid Undulation Actually Means
Geoid undulation is the vertical gap between two different surfaces. The geoid is physical: it follows mean sea level extended under the continents, shaped by gravity, rock density, and ocean currents, and every benchmark and leveled elevation on a drawing refers back to it. A GNSS receiver has no idea where sea level sits. It measures height above the WGS84 ellipsoid, a smooth mathematical model of Earth that ignores gravity entirely. At any point those two surfaces rarely coincide, and the vertical distance between them is N, the geoid undulation.
Applying Geoid Undulation Before You Trust an Elevation
Orthometric height H, the number that matches a benchmark, equals ellipsoidal height h minus N. Skip that correction and a raw DGPS height reading can sit tens of metres off a leveled benchmark, since India runs through the well studied Indian Ocean Geoid Low, where undulation stays deeply negative across much of the country. That is why every DGPS RTK survey workflow applies a geoid model, typically EGM2008 for global compatibility, before an elevation reaches a client drawing or a DEM. Treating raw GNSS output as a finished elevation is one of the fastest ways to fail a leveling check on site.
A GNSS receiver measures height above a mathematical shape. A level measures height above gravity. Geoid undulation is the price of confusing the two.