Geoid vs Ellipsoid vs Topographic Surface

LinkedIn image 1
Published: Olalekan Odunaike  |  Author: Omar Ahmed  |  Source: LinkedIn
Tags: #definitions, #earth, #ellipsoid, #geoid, #hydrographic, #hydrospatial, #survey, #topo_surface

Technical Explanation

What the Image Shows: “Geoid vs Ellipsoid vs Topographic Surface”

The image is an educational comparison of three distinct “surfaces” used to describe the Earth in geodesy and hydrographic/hydrospatial practice:

  • Ellipsoid: a smooth, mathematically defined reference surface used for geodetic positioning and coordinate systems.
  • Geoid: an irregular, gravity-based equipotential surface that approximates global mean sea level (MSL) and continues under landmasses.
  • Topographic surface (including seabed/bathymetry): the true, physically irregular surface of the Earth (land relief, water surface, and seafloor).

In hydrography, these are not abstract concepts: they define how you turn sensor measurements (GNSS positions, depths, tides) into charted depths and elevations in the correct vertical datum (e.g., LAT, MSL) and horizontal datum (e.g., WGS 84 / ITRF / national realizations).

Core Definitions and How They Relate

Ellipsoid (Reference Ellipsoid)

The ellipsoid is a simplified geometric model defined by parameters such as semi-major axis and flattening. Commonly used ellipsoids include WGS 84 and GRS80 (very similar but tied to different reference frame conventions).

  • What GNSS natively provides: latitude/longitude and ellipsoidal height (h) above the ellipsoid.
  • Why it matters: ellipsoidal heights are not “height above sea level.” They are purely geometric and do not follow gravity.

Geoid

The geoid is a gravity-defined surface: an equipotential of the Earth’s gravity field that best corresponds to long-term global mean sea level. It is spatially variable and can be “higher” or “lower” relative to the ellipsoid due to mass distribution within the Earth.

  • Geoid undulation (N): separation between ellipsoid and geoid at a location.
  • Primary use: converting GNSS ellipsoidal height (h) to an orthometric height (H, “height above the geoid”) via H ≈ h − N (with important nuance depending on the chosen height system and model).

Topographic Surface (Land, Water Surface, and Seabed)

The topographic surface is the real physical surface: mountains, buildings, rivers, and—critically for hydrography—the water surface (time-varying) and the seafloor (bathymetry). This is what is directly observed by surveying sensors (sonar, lidar, photogrammetry) but must be referenced to the correct geodetic frames and vertical datums to become usable hydrospatial information.

Key Height Types Used in Hydrography

Hydrographic surveys commonly deal with multiple height/depth definitions simultaneously:

  • Ellipsoidal height (h): from GNSS, relative to ellipsoid.
  • Orthometric height (H): “MSL-like” heights referenced to geoid (or national vertical datums approximating it).
  • Chart datum-related heights/depths: depths reduced to a chart datum such as LAT (Lowest Astronomical Tide) or MLLW in some regions.
  • Sounding/depth (d): measured relative to the instantaneous water surface (or sonar reference point), then reduced to chart datum through tides or ellipsoidally referenced methods.

A practical hydrographic workflow is largely the disciplined transformation among these “surfaces” using defensible models and documented uncertainty.

Datums and Geodetic Reference Frames (Horizontal and Vertical)

Horizontal: Reference Frames vs Datums

Modern hydrography relies on geocentric reference frames (e.g., ITRF realizations) that are realized through GNSS. Many operational “datums” (e.g., WGS 84 as used in navigation) are practical realizations of such frames at an epoch.

  • Important operational detail: the difference between a frame at one epoch and another (plate motion) can create measurable offsets over time.
  • Hydrographic impact: coastal and nearshore surveys often require strict alignment with national geodetic control and charting products (ENCs/paper charts) that may be published in specific realizations.

Vertical: MSL, Geoid-Based Systems, and Chart Datums (LAT)

Vertical referencing in hydrography is more nuanced because charting needs are safety-critical (under-keel clearance), and the water level changes in time and space.

  • MSL (Mean Sea Level): a long-term average of sea level, not a fixed global surface everywhere; locally estimated and affected by ocean dynamics and vertical land motion.
  • Geoid-based vertical datums: national vertical datums frequently approximate a geoid-related surface, though the realization may involve leveling networks, gravity, and constraints.
  • LAT (Lowest Astronomical Tide): a chart datum intended to provide a conservative “low-water” reference for charted depths; defined through tidal theory and long records/modelling, and typically varies spatially.

Hydrographic deliverables often require depths reduced to LAT while also needing GNSS-based elevations and interoperability with land/topo data in MSL/orthometric systems.

Instrumentation: What Measures Which Surface

Positioning (GNSS and Aiding)

  • GNSS (RTK/Network RTK/PPP) provides ellipsoidal positions (including h), with centimeter-to-decimeter level capability depending on technique.
  • Base stations / CORS tie survey results into the adopted geodetic frame and epoch.
  • Heading sensors (dual-antenna GNSS or gyro) are needed for multibeam geometry.

Seafloor Measurement (Sonars)

  • Multibeam echo sounder (MBES) for full-swath bathymetry and backscatter.
  • Singlebeam echo sounder (SBES) for profiling or simpler tasks.
  • Sound velocity sensors: SVP/CTD profilers (water column) and near-transducer sound speed for ray tracing and beam steering.

Vessel Motion (IMU/INS)

An IMU/INS (MRU) measures heave, roll, pitch, and often yaw rate—critical for correcting sonar pointing and measured ranges. These corrections are referenced to the vessel frame and must be aligned precisely (see calibration below).

Topographic/Littoral Mapping

  • Topo-bathymetric lidar bridges land-water interface.
  • Photogrammetry/UAS for coastal topography and intertidal mapping.
  • Terrestrial/MLS lidar for coastal infrastructure and shoreline features.

Survey Setup: Referencing, Lever Arms, and Installation Geometry

The core practical challenge is to express every measurement in a common, well-defined reference frame and epoch. This requires:

  • Lever arms: precise 3D offsets from the GNSS antenna reference point (ARP) and IMU to the sonar head and/or transducer phase center.
  • Reference point definition: a consistent vessel reference frame and sign conventions (forward-starboard-down or similar) documented for the project.
  • Antenna and sensor placement: minimizing multipath for GNSS, avoiding acoustic interference, ensuring rigid mounts to reduce flexure.

Calibration and Alignment (Why “Good Sensors” Still Produce Bad Bathymetry)

Patch Test (MBES Calibration)

Even with accurate GNSS and IMU, small angular misalignments between the sonar and IMU cause systematic bathymetric errors that vary with depth and beam angle. A standard patch test estimates:

  • Roll offset: assessed over flat seafloor with reciprocal lines.
  • Pitch offset: assessed over a slope with reciprocal lines.
  • Yaw/heading offset: assessed by crossing a distinct feature from different directions.
  • Latency/time delay: assessed via dynamic maneuvers; critical when speeds are high or positioning is RTK/PPP with specific filtering.

Sound Speed Calibration

Sound speed errors directly map into refraction and depth biases, especially for outer beams in MBES. Hydrographic practice requires:

  • Frequent SVP/CTD casts based on stratification and environmental variability.
  • Continuous near-surface sound speed at the transducer for correct beam steering.

Time Synchronization: The Hidden Datum

Hydrographic systems are multisensor systems; a timing error is equivalent to a position error when the platform is moving. Robust surveys therefore implement:

  • Single time base for GNSS, sonar, and INS (often GNSS time/UTC traceable).
  • PPS (Pulse-Per-Second) and time-tagging distribution to acquisition PCs and sensors.
  • Latency characterization: documenting and compensating sensor and network delays (especially for inertial aiding and GNSS corrections).

Without validated synchronization, you can meet individual sensor specs but still fail bathymetric tolerances due to mismatched time stamps.

Vertical Referencing Workflows in Practice (Geoid, Tides, and the “Separation Models”)

Tide-Based Reduction to Chart Datum (Traditional Method)

  • Measure water level from tide gauges (and/or hydrodynamic tide models).
  • Apply time/space corrections to convert measured depths to depths relative to LAT (or other chart datum).
  • Requires careful datum connection: tide gauge zero to chart datum, and stable benchmarks tied to the geodetic network.

Ellipsoidally Referenced Surveying (ERS)

Many modern surveys reduce to chart datum using GNSS heights and models rather than (or in combination with) gauge observations:

  • GNSS provides h.
  • Apply a geoid model (ellipsoid-to-geoid) plus a chart datum separation model (geoid-to-LAT or ellipsoid-to-LAT) derived from tide models, observations, and/or national hydrographic agency products.
  • Result: real-time or post-processed tide correction equivalent without a local tide gauge for every project area (subject to approval, model validity, and uncertainty budget).

Data Processing Workflow (From Raw Measurements to Hydrospatial Products)

Acquisition and Logging

  • Raw GNSS, INS, sonar, sound speed, and ancillary sensor data recorded with metadata.
  • Line planning and coverage designed for required detection/coverage standards and seafloor type.

Post-Processing Steps

  • GNSS/INS processing: apply differential corrections (RTK/PPP), smoothing, and navigation QC.
  • Apply calibrations: patch test values, lever arms, latency.
  • Apply sound speed corrections: ray tracing with SVP, transducer sound speed updates.
  • Vertical reduction: tides or ERS using geoid and separation models; ensure the output vertical datum is explicitly stated (LAT, MSL, etc.).
  • Cleaning and filtering: remove spikes, water column artifacts, noise; maintain audit trail.
  • Surface generation: create gridded bathymetry (e.g., BASE surface), contours, and features.

Final Outputs

  • Bathymetric grids and soundings reduced to chart datum (e.g., LAT).
  • Topo surfaces for coastal zones integrated with bathymetry for seamless DEMs.
  • Derived products: backscatter mosaics, seabed classification inputs, hazard/feature reports.

QA/QC and Uncertainty (Making Results Defensible)

Hydrography is governed by safety-of-navigation and engineering decision requirements, so uncertainty must be quantified and demonstrated.

Error Sources to Track

  • GNSS errors: multipath, corrections quality, reference frame consistency, antenna calibration.
  • INS/IMU errors: bias stability, alignment, vibration, heading performance.
  • Sound speed uncertainty: temporal/spatial mismatch, sensor drift.
  • Tide/water level uncertainty: gauge errors, zoning/model errors, timing offsets, spatial gradients.
  • Datum/model uncertainty: geoid model errors, chart datum separation model errors, transformation uncertainties.

Common QA/QC Practices

  • Crosslines and junction analysis: quantify consistency between intersecting survey lines.
  • SBET/trajectory QC: check GNSS fix quality, PDOP, residuals, outages.
  • Statistical cleaning rules: documented thresholds and review of rejected soundings.
  • Uncertainty surfaces: producing TPU (Total Propagated Uncertainty) layers where feasible.
  • Traceability: complete metadata on frames, epochs, datums, models, software versions, and parameters.

A key practical point connected to the image: you can only claim “depth relative to LAT” (or “elevation relative to MSL/geoid”) if you can demonstrate the chain from the measured topographic/bathymetric surface through the ellipsoid/geoid models and tide/separation models with known uncertainty.

Real-World Applications (Why These Surfaces Matter)

  • Nautical charting and ENCs: safe depths require correct reduction to chart datum (often LAT) and consistent horizontal framing.
  • Dredging and port engineering: volume estimates and compliance surveys require stable vertical control, often bridging chart datum and engineering datums.
  • Coastal resilience and flooding: integrating topo (land) with bathymetry needs coherent transitions between MSL/geoid-based heights and tidal datums.
  • Offshore energy and subsea construction: precise seafloor positioning and vertical reference control for pipelines, cables, foundations.
  • Habitat mapping and marine spatial planning: bathymetry grids and derivatives (slope, rugosity) depend on consistent processing and QC.

Practical Takeaway

The image’s message can be summarized operationally:

  • Ellipsoid: where GNSS “lives” (geometric reference).
  • Geoid: gravity-based bridge toward “MSL-like” height systems.
  • Topographic/bathymetric surface: what sensors measure and what users need—provided it is reduced to the correct datum (LAT/MSL) and tied to the correct geodetic frame, with robust time synchronization, calibration, processing, and QA/QC.

Details & Context


Credit: Article assembled by Olalekan Odunaike from a LinkedIn post by Omar Ahmed.