Ground Elevation Converter

The Ground Elevation Converter converts GPS ellipsoidal heights to orthometric elevations, between datums and units, using geoid models.

About the Ground Elevation Converter

Ground elevation is the height of land relative to a vertical datum that approximates mean sea level. GNSS receivers report ellipsoidal height, which does not match ground elevation by default. The difference is the geoid undulation, a gravity-based correction that varies by location. Converting between these height types requires a geoid model and the correct vertical datum.

This Converter helps engineers, surveyors, GIS teams, and field crews keep numbers consistent. It aligns GNSS points with topo maps, matches drone surfaces with benchmarks, and brings multiple datasets into one frame of reference. It supports common datums and unit conversions, and it documents the steps used in every calculation.

Digital elevation sources vary. A DEM represents bare-earth terrain. A DSM includes buildings and vegetation. A DTM is a curated terrain model. The tool can accept any of these as inputs, but it always reports which surface you used, so you can compare results fairly.

How the Ground Elevation Method Works

The core idea is simple: convert ellipsoidal heights to orthometric heights using a geoid model, or transform one vertical datum to another. The Converter automates datum selection, geoid lookup, interpolation, and unit handling. It then returns both the computed elevation and the supporting parameters.

• Start with latitude, longitude, and an ellipsoidal height from GNSS, or a map elevation from a DEM.
• Select your source and target vertical datums. Typical options include NAVD88, EGM96, and EGM2008.
• Query the geoid model to get N, the geoid height at your location, using interpolation across model grids.
• Convert heights: orthometric elevation H = h − N, where h is ellipsoidal height.
• Apply unit conversion and optional terrain adjustments, then record the final elevation and uncertainty.

When transforming between vertical datums, the Converter uses the appropriate geoid surfaces or model-to-model offsets. It also flags when a requested conversion is outside the supported area or data range.

Equations Used by the Ground Elevation Converter

The tool applies standard geodetic relationships. It computes geoid heights through grid interpolation, then propagates units and uncertainties. The following equations summarize the core math.

• Orthometric height: H = h − N, where h is ellipsoidal height and N is the geoid undulation.
• Datum-to-datum transform: H2 = (h − N2), with h = H1 + N1, so H2 = H1 + (N1 − N2).
• Bilinear interpolation for geoid grid: N(x, y) = Σ wi · Ni at the four surrounding nodes.
• Bicubic interpolation (optional): N(x, y) from 16 neighboring nodes using cubic polynomials for smoother derivatives.
• Unit conversion: meters to international feet ft = m × 3.280839895; US survey foot ftUS = m × 3.280833333.
• Decimal degrees: dd = deg + min/60 + sec/3600; negative for south latitudes or west longitudes.

The sign convention H = h − N assumes geoid heights are positive above the ellipsoid. Some references reverse signs; the Converter fixes the convention per geoid and documents it in the result. It also preserves significant figures to match your measurement precision.

Inputs, Assumptions & Parameters

Provide a position, a height, and your preferred datums and units. The Converter validates your inputs, fills any missing defaults, and shows the assumptions used in the calculation.

• Position inputs: latitude and longitude in decimal degrees or DMS format.
• Height inputs: ellipsoidal height h from GNSS, or ground elevation H from a DEM or survey.
• Vertical datum options: NAVD88, EGM96, EGM2008, and other supported regional models.
• Geoid model: chosen automatically based on datum, with model version noted in results.
• Units: meters, international feet, or US survey feet.
• Interpolation method: bilinear by default; bicubic available for smoother surfaces.

Latitude must be between −90 and 90. Longitude must be between −180 and 180. Heights can be negative in deep basins or below sea level. Extremely high points, such as Everest, remain valid. If a point falls outside a model’s coverage, the tool warns you and suggests another model.

Using the Ground Elevation Converter: A Walkthrough

Here’s a concise overview before we dive into the key points:

1. Select your source height type: Ellipsoidal (GNSS) or Orthometric (map or DEM).
2. Enter latitude and longitude, then choose your input and output datums.
3. Type your height value and select units under the Units options.
4. Open Advanced options to pick the interpolation method if needed.
5. Click Convert to compute ground elevation and see key steps in the summary.
6. Review outputs, including H, N, unit conversions, and estimated uncertainty.

These points provide quick orientation—use them alongside the full explanations in this page.

Case Studies

A construction surveyor collects a GNSS reading on a control point: h = 251.432 m at 39.742° N, −104.991° W. The geoid model returns N = 17.890 m for EGM2008. The Converter calculates H = 251.432 − 17.890 = 233.542 m NAVD88. The elevation in international feet is 233.542 × 3.280839895 = 766.11 ft. What this means: the control point’s ground elevation is about 233.54 m (766.11 ft) above the NAVD88 datum.

A drone mapping team processes a DSM over a city block and reports roofline elevations near 120.0 m. They want bare-earth elevations in EGM96. The DSM-to-DEM offset averages −8.5 m from ground truth. The Converter applies Hground ≈ 120.0 − 8.5 = 111.5 m, then verifies N differences between EGM2008 and EGM96. After adjusting between datums, final terrain elevations average 111.2 m EGM96. What this means: removing surface objects and aligning datums yields consistent terrain values for design work.

Accuracy & Limitations

Accuracy depends on your input quality, the chosen geoid model, and the local terrain. GNSS ellipsoidal heights can be very precise, but a poor geoid choice introduces bias. DEMs carry their own errors from sensors and interpolation.

• Typical geoid model uncertainty ranges from a few centimeters to several decimeters, by region.
• GNSS height accuracy worsens under canopy, near buildings, or with short observation times.
• DEM resolution and age affect local elevation, especially in steep or built environments.
• Datum mismatches can add systematic offsets if not handled explicitly.
• Interpolation is an approximation; bicubic is smoother but can overshoot near sharp gradients.

Use the Converter’s reported uncertainty as guidance, not a guarantee. For legal or design-grade work, tie into local benchmarks, extend GNSS observation times, and confirm the vertical datum with your client or agency.

Units Reference

Elevation work crosses maps, instruments, and regulations that use different units. Consistent units prevent costly mistakes. This quick reference shows common units and the factors used in conversions.

To convert meters to feet, divide by the factor above; to convert feet to meters, multiply by it. Check project specs for which foot definition applies, since ft and ftUS differ slightly.

Common Issues & Fixes

Most conversion errors come from datum mix-ups, unit confusion, and off-by-one coordinate formats. Use the tool’s validation messages to catch these early.

• Heights look too high or low: verify the vertical datum and geoid model.
• Foot conversion off by a bit: confirm international foot vs US survey foot.
• Coordinates plot in the ocean: check the sign for west longitudes or south latitudes.
• Rough geoid at edges: switch from bilinear to bicubic interpolation.

If your area lacks coverage for a geoid model, pick a supported alternative or limit conversions to the available region. For mixed datasets, convert everything to one datum and unit before comparing.

FAQ about Ground Elevation Converter

What is the difference between ellipsoidal and orthometric height?

Ellipsoidal height is measured from a mathematical ellipsoid used by GNSS. Orthometric height is measured from a gravity-based surface approximating mean sea level, called the geoid.

Which geoid model should I pick?

Use the model associated with your target datum and region. For global work, EGM2008 is common. For the United States, NOAA GEOID models align with NAVD88 and related datums.

Can I convert between NAVD88 and EGM96 directly?

Yes. The Converter computes differences between the models at your location, then adjusts the height accordingly. It reports the models and versions used.

How accurate are results from a consumer GPS?

Expect several meters vertically in typical conditions. Tall buildings, trees, and short fixes worsen accuracy. For better results, average observations or use survey-grade equipment.

Ground Elevation Terms & Definitions

Ellipsoidal Height (h)

Height above a reference ellipsoid, usually WGS 84, as reported by GNSS devices.

Orthometric Height (H)

Height above the geoid, representing elevation relative to mean sea level.

Geoid Undulation (N)

The separation between the ellipsoid and the geoid at a location, used to convert h to H.

Vertical Datum

A reference surface for heights, such as NAVD88 or EGM2008, tied to a specific geoid model.

DEM, DSM, DTM

DEM is ground terrain, DSM includes surfaces like trees and roofs, and DTM is a refined bare-earth model.

Interpolation

A method to estimate values between grid nodes; bilinear is simple, bicubic is smoother.

Uncertainty

A quantitative estimate of potential error from measurements, models, and processing steps.

Benchmark

A surveyed point with known elevation used to validate or adjust local measurements.

References

Here’s a concise overview before we dive into the key points:

• NOAA NGS Geoid Models and Tools
• NGA WGS 84 and Earth Gravitational Model Information
• USGS National Map Elevation Data
• EPSG Geodetic Parameter Dataset
• NOAA NGS Continuously Operating Reference Stations (CORS)

These points provide quick orientation—use them alongside the full explanations in this page.