Skip to content

Geoid vs Spheroid

  • by

Maps and GPS apps look simple on a screen, yet every coordinate rests on a hidden choice between two invisible shapes: the lumpy geoid and the smooth spheroid. Picking the wrong one can shift a boundary line or send a tunnel off course.

Understanding the difference is no academic exercise—survey crews, drone pilots, and even hikers who blend old benchmarks with new satellites confront it daily.

🤖 This article was created with the assistance of AI and is intended for informational purposes only. While efforts are made to ensure accuracy, some details may be simplified or contain minor errors. Always verify key information from reliable sources.

Core Definitions in Plain Language

What the Geoid Really Is

The geoid is an imaginary sea surface that would hug Earth’s hills and valleys if oceans could flow through continents. It answers the question “Where would water level be?” at every spot on land or sea.

Because gravity tugs unevenly—stronger over dense rock, weaker over light sediments—the geoid rises and falls by roughly a hundred meters relative to a perfect ellipse.

What the Spheroid (Ellipsoid) Really Is

A spheroid is a smooth, rotating ellipse spun symmetrically around its short axis; it looks like a slightly squashed beach ball. Geodesists use it as a convenient mathematical stand-in for Earth’s bulk shape.

It ignores mountains, ocean trenches, and gravity quirks, offering a single set of neat numbers—semi-major and semi-minor axes—that fit nicely into software code.

Why Two Models Exist Side by Side

Gravity’s Messy Reality

Water pipes, not satellites, first forced surveyors to care about the geoid. A plumber laying sewer lines in a flat-looking prairie still needs downhill flow; the geoid provides that true “level” reference.

Computers’ Love of Smooth Math

Early computers struggled to store every lump on Earth, so scientists replaced the lumpy surface with a sleek ellipsoid that needs only two radii. The compromise stuck, and today’s chips still prefer the simplicity.

Visualizing the Separation

Orthometric vs Ellipsoidal Heights

Your phone might say you stand 1,200 m above “sea level,” yet its raw GPS fix places you 1,235 m above the ellipsoid. The 35 m gap is the geoid-ellipsoid separation, often labeled N.

Confuse the two numbers and a reservoir spillway could be built 35 m too low, turning a safety feature into a flood risk.

Where the Gap Vanishes

Near the coasts of some regions, gravity happens to pull so that geoid and spheroid coincide; here, elevation numbers look identical and errors disappear. Surveyors call these “zero-undulation” strips and use them as calibration checkpoints.

Field Examples That Matter

Construction Site Stakes

A road crew in a mountain valley transfers benchmarks from a nearby geoid-based monument. If they adopt raw GPS heights based on the spheroid, the first asphalt layer can drift several decimeters, forcing costly re-grading.

Drone Mapping Mosaics

Photogrammetry software stitches drone photos using GPS tags tied to the spheroid. Without geoid correction, elevation colors on the final map sag or bulge, making drainage plans unreliable for farmers.

Coordinate System Traps

Projected Grids vs Global Frames

National grids bake the geoid in through orthometric heights, while global frames like WGS84 sit on the spheroid. Mixing a grid bearing with a global distance calculation is like mixing metric and imperial bolts—threads almost fit, then jam under load.

Epoch Updates Shift the Floor

When reference frame maintainers release a new epoch, the spheroid’s center can drift a few centimeters relative to crustal plates. Surveyors who ignore the shift inject a tilt into supposedly “flat” parking lots.

Choosing the Right Model for Your Task

When the Geoid Wins

Floodplain mapping, sewer design, and any task where water must flow correctly demand geoid-based heights. Engineers want true gravity level, not geometric elegance.

When the Spheroid Suffices

Airline navigation, satellite tracking, and continental plate motion studies care more about geometric position than water flow. Here, the smooth spheroid keeps math light and errors globally consistent.

Software Settings Most People Miss

Check the Vertical Datum Flag

Field apps often default to “Ellipsoidal h.” Toggle once to “Geoid h” or your exported CSV will carry the wrong vertical unit, silently propagating into CAD plans.

Geoid Model File Versions

Replacing an older GEOID12B file with GEOID18 in the same project changes heights by a few centimeters. Reprocess old surveys before merging new shots to avoid stair-step elevation artifacts.

Hardware Considerations

Single-Frequency Receivers

Budget GPS modules lack the bands needed to solve for tropospheric delay, so their spheroid heights wander. Rely on them only after tying to a local geoid benchmark with a short-range level run.

RTK Base Corrections

RTK base stations broadcast differences relative to the spheroid. If the rover outputs orthometric heights, the base must load the same geoid model, or the separation is applied twice, sending a culvert invert skyward.

Practical Workflow Tips

Start Every Job with a Datum Label

Write “NAVD88 orthometric” or “WGS84 ellipsoidal” on the first page of the field book. A one-second habit prevents weeks of re-survey when mixed teams share data months later.

Store Raw and Corrected Files Separately

Keep a “_ellipsoid” copy untouched. When a new geoid model appears, you can recompute instead of returning to the field for another dusk session on a busy highway.

Leave a Reply

Your email address will not be published. Required fields are marked *