LAT, Chart Datum, Tide, and Depth

Cover image
Published: Olalekan Odunaike  |  Author: Omar Ahmed  |  Source: LinkedIn
Tags: #chart_datum, #depth, #hydrographic, #hydrospatial, #lat, #survey, #tide

Technical Explanation

Technical Explanation: What the Image Shows (LAT, Chart Datum, Tide, and Depth)

The image is a simplified hydrographic concept diagram showing the relationship between Lowest Astronomical Tide (LAT), Chart Datum (CD), tidal height, and two different “depth” notions used in navigation and surveying: charted depth and actual depth. The graphic depicts a sea surface varying with the tide and a vertical reference level labeled LAT/Chart Datum, from which tide heights and charted depths are referenced.

On the right-hand side, the image illustrates:

  • Height of tide: the instantaneous water level above the chart’s vertical reference (typically Chart Datum).
  • Charted depth: the depth value printed on nautical charts, reduced to Chart Datum.
  • Actual depth: the true water column at the time of observation, which equals charted depth plus the instantaneous tidal height (and any residual effects).

The accompanying text in the post’s comments correctly notes an important operational nuance: Chart Datum is not always identical to LAT. Many charting authorities adopt LAT as Chart Datum where feasible, but Chart Datum can be set lower than LAT for safety or for practical reasons (e.g., limited tidal records, conservative policy, or stepped datums in complex estuaries).

Core Definitions (Hydrography and Geodesy)

Lowest Astronomical Tide (LAT)

LAT is the lowest tide level that can be predicted to occur under average meteorological conditions and astronomical forcing only (sun/moon tidal constituents). It is a tidal datum derived from analysis of tidal observations and harmonic constituents, and it is intended to represent an extreme low-water reference excluding weather effects (storm surge, pressure, wind setup/setdown).

Chart Datum (CD)

Chart Datum is the vertical reference surface to which:

  • charted depths (soundings) are reduced, and
  • tide predictions (heights of tide) are referenced in tide tables and in most nautical charting systems.

In many regions, CD is defined as LAT; however:

  • CD may be lower than LAT as an added safety margin if LAT is uncertain or the record length is insufficient.
  • In rivers and estuaries, CD may be implemented in discrete segments (“steps”) for practicality, while the true LAT surface varies more continuously along the channel.

Mean Sea Level (MSL)

MSL is a long-term average water level over a defined epoch. It is commonly used in geodesy and coastal engineering as a “mean” reference but is not a safe navigation datum because water levels frequently fall below MSL.

Tidal Height and Depth Relationships

For navigation and survey reduction, a key relationship is:

Actual depth at time t ≈ Reduced (charted) depth + Height of tide(t) + Residual(t)

Where Residual(t) represents non-astronomical effects such as storm surge, wind setup, seiches, and atmospheric pressure anomalies. The image’s narrative (“only meteorological events can violate the assumption”) refers to this residual component.

Why LAT and Chart Datum Are Critical in Hydrographic Surveying

Safety of Navigation

Nautical charts are designed so that charted depths are conservatively shallow. If the chart datum approximates an extreme low-water surface (LAT or lower), then the mariner’s under-keel clearance calculation is simplified and safer: the vessel can generally assume that actual depth is usually greater than or equal to charted depth, except during unusual meteorological conditions or in highly dynamic environments.

Standardization of Survey Reductions

Hydrographic surveys must reduce measured depths to a consistent vertical reference (CD). Without a common datum, soundings collected on different days (different tides) cannot be combined into a coherent bathymetric surface for charting, dredging, or coastal modeling.

Instrumentation and Measurement Setup

Bathymetric Sensors

  • Singlebeam echo sounder (SBES): measures depth along a line; suited to reconnaissance, smaller areas, and specific profiles.
  • Multibeam echo sounder (MBES): measures swath bathymetry; standard for modern charting and high-resolution seabed models.
  • Sound velocity instruments: SVP/CTD casts and/or surface sound speed sensors to correct acoustic ray-path and travel time.

Positioning and Attitude Sensors

  • GNSS (RTK/Network RTK/PPP): provides geodetic position; with appropriate methods can also provide ellipsoidal heights for GNSS tide workflows.
  • IMU/MRU: measures heave, roll, pitch, and often heading; essential for MBES uncertainty control.
  • Gyrocompass or GNSS heading: provides heading; critical for beam steering and georeferencing.

Water Level Measurement (Tide and Datum Transfer)

  • Tide gauges (stilling well, pressure, radar): measure water level relative to a local gauge datum, later related to CD via leveling and datum relationships.
  • GNSS-based water level (“GNSS tide”): uses ellipsoidal heights and a separation model to convert to chart datum without relying solely on a nearby gauge (requires careful geoid/CD separation modeling and validation).

Calibration and Field Checks (Hydrographic Best Practice)

Echo Sounder Calibration (Bar Check / Patch Tests)

  • SBES bar check: verifies draft, latency, and sound speed in shallow water.
  • MBES patch test: estimates timing latency and angular misalignments (roll, pitch, yaw) by running specific calibration lines over known features or slopes.

Sound Speed Control

Sound speed variability is a dominant error source for MBES. Good practice includes frequent SVP casts where stratification changes, and consistent application of sound speed profiles in processing.

Draft and Dynamic Draft

Transducer draft must be measured and referenced consistently. Dynamic effects (squat, settlement, trim changes) can be significant in shallow water and should be modeled or measured when required by accuracy standards.

Geodetic Frames and Vertical Datums (How LAT/CD Relate to GNSS)

Ellipsoidal Heights vs. Chart Datum

GNSS natively provides heights above a reference ellipsoid (e.g., WGS 84 / ITRF realization). Chart datum is a tidal datum. Converting between them requires a separation model:

  • Ellipsoid → Geoid (or quasi-geoid) to obtain orthometric/normal heights (MSL-like vertical reference), and
  • Geoid/MSL-like surface → CD (LAT-based surface) using tidal datum modeling and gauge control.

Vertical Datum Surfaces in Practice

Depending on national hydrographic practice, a project may involve one or more of the following surfaces:

  • Chart Datum (CD): for soundings and safe navigation products.
  • MSL or national vertical datum: for coastal engineering, shoreline work, and integration with terrestrial mapping.
  • Ellipsoid: for GNSS measurement; used internally in processing and for seamless offshore/onshore workflows.

Why CD May Differ from LAT

The comment highlighted in the post is operationally important:

  • Record length and completeness: LAT computed from limited observations may not capture the true lowest predicted tide; authorities may set CD lower to remain conservative.
  • Complex hydrodynamics: estuaries and rivers can have strong spatial gradients in tidal range and phase; charting implementations may simplify CD transitions into steps for usability, even though the physical LAT surface is continuous.
  • Policy and legacy considerations: chart datum definitions are sometimes inherited and maintained for chart continuity, even as models improve.

Time Synchronization (Often Underestimated, Always Critical)

Hydrographic systems are multi-sensor and time-dependent. A consistent time base is required to correctly apply position, attitude, and tide/water level at the moment each sounding is measured.

  • GNSS time / UTC alignment: acquisition computers, GNSS receivers, and sonars must be synchronized (NMEA time tags, PTP/NTP discipline, or hardware time stamping).
  • Latency management: delays in sonar ping time stamping, navigation output, and IMU integration must be measured and corrected (particularly for MBES at speed).
  • Tide time series alignment: gauge data and predicted tides must be referenced to the same time system and sampling/averaging conventions.

Data Processing Workflow (From Raw Soundings to Charted Depths)

1) Data Ingest and Sensor Integration

Merge raw sonar, navigation, and motion data using the survey vessel reference frame (lever arms, alignment angles, vessel coordinate system). Confirm correct application of offsets and sign conventions.

2) Apply Environmental and System Corrections

  • Sound speed profile correction (ray tracing for MBES).
  • Heave/roll/pitch/heading corrections.
  • Draft and dynamic draft/squat (if modeled).

3) Vertical Reduction to Chart Datum

Apply one of the following, depending on project design:

  • Tide gauge zoning: apply observed/predicted tide heights referenced to CD, with spatial zoning for large areas.
  • GNSS tide / ellipsoid referencing: reduce soundings via ellipsoidal heights using a validated separation model to CD.

4) Cleaning, Gridding, and Surface Creation

  • Outlier detection (statistical filters, CUBE or equivalent uncertainty-based methods).
  • Creation of gridded bathymetry (resolution chosen based on depth, required detection capability, and survey specification).
  • Feature investigation (contacts, obstructions) and least depth determination for navigation hazards.

5) Product Generation

  • Sounding selections and contours for nautical chart compilation.
  • Digital terrain models for engineering and habitat applications.
  • Uncertainty layers and survey reports aligned to IHO standards.

QA/QC and Uncertainty (What Must Be Demonstrated)

Uncertainty Budget Components

Total vertical uncertainty typically includes contributions from:

  • Sonar measurement (range precision, beam geometry, detection).
  • Sound speed (profile error and temporal/spatial mismatch).
  • Vessel motion (IMU performance, alignment, latency).
  • Positioning (GNSS accuracy, multipath, outages).
  • Vertical referencing (tide gauge error, zoning error, separation model uncertainty).

Validation Techniques

  • Crosslines and check lines: compare intersecting lines for consistency and detect systematic biases.
  • Patch test verification: confirm stable alignment parameters over time and after equipment changes.
  • Water level residual analysis: compare observed vs predicted tides; quantify non-tidal residuals and assess whether additional corrections are needed.
  • Uncertainty compliance: demonstrate that results meet project/IHO S-44 order requirements, including documented TPU (Total Propagated Uncertainty).

Real-World Applications of LAT/CD Concepts

  • Nautical charting and safe navigation: ensuring charted depths are conservative relative to likely water levels.
  • Dredging and port maintenance: controlling dredge depth relative to chart datum and verifying under-keel clearance margins.
  • Coastal engineering and construction: translating between CD, MSL, and national vertical datums for design elevations and clearances.
  • Flood and storm surge analysis: separating astronomical tide from meteorological residuals; communicating water levels relative to MSL and CD.
  • Seamless onshore–offshore mapping: integrating bathymetry (CD) with topography (land vertical datum) via geodetic transformations and separation models.

Key Takeaways (Aligned with the Post’s Discussion)

  • LAT is a tidal datum representing the lowest predicted astronomical tide under average meteorological conditions.
  • Chart Datum is the chart’s vertical zero for depths and tide heights; it is often based on LAT but may not equal LAT.
  • Actual depth varies with the tide and meteorological residuals; charted depth is reduced to CD for safety and consistency.
  • Operational hydrography requires rigorous control of instrument calibration, time synchronization, datum definitions, and uncertainty to produce defensible, safe navigation products.

Details & Context


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