Ellipsoidal vs Orthometric Height
Horizontal coordinate systems get all the attention, but the mistake that quietly ruins elevation work is vertical. A receiver hands you one kind of height, the map beside you uses another, and nothing in either file says so. This guide explains the two heights, why they differ, and the one habit that keeps you out of trouble.
Two different reference surfaces
Ellipsoidal height is measured from a smooth mathematical model of the earth — an ellipsoid. It is a clean geometric surface with no relation to gravity, which is exactly what satellite positioning needs.
Orthometric height is measured from the geoid: the surface that gravity actually defines, roughly mean sea level extended under the continents. It is lumpy, because the earth's mass is not evenly distributed.
Both are "height", both are in metres, and they can differ by tens of metres at the same point.
The geoid separation
The gap between the two surfaces is called geoid separation (often written N). The relationship is simple: orthometric height ≈ ellipsoidal height − N.
N is not small and not constant. It ranges from roughly −100 to +85 metres globally, and it varies across a country. This is why you cannot fix the problem with a single offset unless your site is small.
Why it matters in practice
Water does not flow downhill along the ellipsoid. Drainage, grading, flood levels and anything else driven by gravity must be computed on orthometric heights, or the design is simply wrong.
Volumes are more forgiving but not immune. A volume is a difference between two surfaces, so a constant vertical offset cancels out — as long as both surfaces carry the same kind of height. Mix one ellipsoidal surface with one orthometric surface and you introduce a systematic error across the whole site.
How the mistake usually happens
A drone survey is processed with GNSS control and comes out ellipsoidal. It is compared against an earlier survey that was levelled to benchmarks, so orthometric. Both are correctly georeferenced, both open without a warning, and the difference between them is contaminated by the geoid separation.
The tell-tale sign is a difference map that is uniformly biased — the whole site is "up" or "down" by a suspiciously round number, with the real changes sitting on top of that shift.
The habit that prevents it
Write down the vertical reference of every dataset when you receive it, in the file name or a project note. Elevation files rarely carry it in a way software can read, so the metadata has to be human.
Do any conversion once, at the source, with a geoid model appropriate for your region — then keep the whole project in that one reference.
STREAM computes elevations, slopes and volumes in whatever vertical reference your data already carries; it does not convert between ellipsoidal and orthometric heights. That makes the rule straightforward: bring in surfaces that already share one vertical reference, and every derived number will be consistent. STREAM will warn you when a layer's coordinate system does not match the project, but no software can detect a vertical reference that was never recorded.
Keep one coordinate system per project in STREAM
Native Windows · fully offline · free beta