Did you know that a GPS receiver and a topographic map can give different heights for the same spot even when neither is simply “wrong”? Students sometimes compare the two numbers and immediately blame a faulty device, but the first question is which reference surface each number uses.
Ellipsoidal height measures a position relative to a mathematical reference ellipsoid. Orthometric height measures height in a physical vertical reference system linked to the gravity field, often informally described as height above mean sea level. A geoid model helps convert between these types of height. The reference matters as much as the metres.
In a practical geography or data project, read the altitude label, units, datum and source description before combining two heights. Do not subtract numbers from incompatible height systems and call the difference a hill, a measurement error or a change in sea level.
- A satellite-derived position can be expressed as ellipsoidal height, but a device may also display a converted height; check its documentation.
- A map’s labelled elevations use a specified vertical datum, which may not be identical to the receiver’s height datum.
- A modelled geoid separation connects the reference systems when the model and datum are compatible.
- Accuracy, antenna position, rounding and the age of data can cause further differences even after the datum is handled.
Why there are two useful ways to define height
A globe made of a smooth mathematical shape is useful for calculations from satellite positions. Real Earth is not a smooth ellipsoid, and the direction of gravity does not perfectly match geometric expectations everywhere. Mapping and engineering therefore use physical height systems as well as satellite-oriented coordinate systems. Each answers a legitimate but different question.
The United States National Geodetic Survey explains this distinction in its overview of GPS ellipsoidal and orthometric heights. It gives the relationship h = H + N, where h is ellipsoidal height, H is orthometric height, and N is the geoid height or separation for a compatible geodetic model. Equivalently, H = h − N. The model and datum must be named; the equation is not permission to substitute any three height readings.
Hand-checked worked example with metres and assumptions
Here is a fictional classroom survey, not a real point in Singapore or an observation of a pupil. Imagine that a GNSS solution reports ellipsoidal height h = 72.4 m and a compatible geoid model at that fictional location gives N = +21.6 m. Assume the quoted figures are already expressed in the same frame and that we are ignoring measurement uncertainty for this calculation.
Apply H = h − N. Then H = 72.4 m − 21.6 m = 50.8 m. Check by reversing the formula: 50.8 m + 21.6 m = 72.4 m, which recovers the ellipsoidal height. The arithmetic is straightforward; choosing the correct inputs is the hard part.
What if a different fictional point has h = 18.0 m and N = −7.0 m? Then H = 18.0 − (−7.0) = 25.0 m. The two minus signs matter. A negative geoid separation can lead to an orthometric height numerically greater than ellipsoidal height. There is no universal instruction to always subtract a positive number.
These values are invented for practice. Never copy the +21.6 m or −7.0 m examples into a real map. Actual geoid separations depend on position and the selected model, and real vertical transformations require verified source and target datums. NGS describes its geoid-height service as a way to obtain model values for supported transformations; its regional models must not be assumed valid worldwide.
Diagnose the real misunderstanding before extra exercises
Ask a learner: “A receiver shows 72.4 m and the map shows 50.8 m. Is one wrong?” A careful answer is “not necessarily; first identify the reference surfaces and vertical datums.” A pupil who immediately says “GPS is inaccurate by 21.6 m” may have mistaken a reference-system offset for random measurement error.
Next present the formula h = H + N and ask what each letter measures. If the pupil knows the words but writes 72.4 + 21.6 to obtain H, diagnose algebraic rearrangement and signed-number handling. If they calculate 50.8 m but confidently say “the school is 50.8 m above sea level” without datum information, diagnose a claim that is too strong for the supplied evidence.
Guided-to-independent practice
- Stage 1 — vocabulary: Match ellipsoid, geoid, orthometric height and vertical datum to plain-English descriptions without any calculation.
- Stage 2 — controlled arithmetic: Given h = 60.0 m and N = +12.0 m, calculate H = 48.0 m; verify 48.0 + 12.0 = 60.0 m.
- Stage 3 — negative values: Given h = 8.0 m and N = −4.0 m, calculate H = 12.0 m; write the subtraction clearly.
- Stage 4 — diagnose the source: Show two different height readouts with their model descriptions; ask which datum is named and what information remains missing.
- Stage 5 — independent transfer: On a fresh imaginary map, explain why two numbers differ before deciding whether any subtraction is justified.
What parents and teachers can do next
For a school survey, a teacher can require students to write a short metadata line: “height value, unit, source, reference datum and method.” Parents can ask children to point to the source description rather than accept the first apparent discrepancy as a failure. A student can keep a small data table separating recorded values from converted values, so original evidence remains available for checking.
Observable progress is not only getting one numerical answer right. Track whether the child independently identifies the height type, rearranges the signed formula, and refuses to assert an exact real-world elevation without enough source information. Try the same three checks a week later using different invented numbers.
Limits and common real-world complications
GPS/GNSS height estimates may vary with satellite geometry, signal obstruction, equipment, antenna placement and processing methods. A phone may report a height already converted from the ellipsoid; a detailed survey receiver may expose ellipsoidal height explicitly. Maps may use different local vertical datums, while some apps smooth or average their displayed heights. You cannot decide the source of a mismatch from two unlabeled numbers alone.
Some vertical datums are defined through local tide-gauge or national survey systems and are not interchangeable with an unspecified global “sea level”. The teaching equation is most useful after you verify compatible model definitions. For engineering, flood assessment or safety-critical navigation, rely on qualified survey methods rather than a simple phone screenshot.
Frequently asked questions
Is GPS altitude always ellipsoidal height?
No. Raw or processed GNSS positions can use an ellipsoidal reference, but some devices and services output a converted height. Check the device, dataset and datum.
Does a map elevation always mean exact height above today’s sea surface?
No. It refers to the map’s specified vertical datum and may reflect survey accuracy, rounding and model conventions. Sea level itself varies with place and time.
Can I use the same geoid offset everywhere?
No. Geoid separation varies geographically, and different model and datum choices matter. A number from an unrelated region is not a valid correction.
What is the fastest self-check for the formula?
For a compatible height system, verify that the chosen H plus N gives back h, keeping all quantities in metres and preserving negative signs.
Continue with verified eduKate guidance
For another map-reading decision, explore how to convert compass readings into true map bearings. The Education Hub connects geography, mathematics and independent source-checking. Our Clementi teaching reference develops the habit of naming quantities, checking algebra and testing the answer independently.
Good geographic reasoning starts with the meaning of a measurement. Once children ask “height above what?” rather than just “how high?”, apparent contradictions become questions they can investigate responsibly.