CAT_03 // Bathymetry

Bathymetry Model Sync: Keeping the Seafloor Map Current

Published
Reading time
2 min
Textured seafloor-like surface seen from above
Photo: @liodp via Unsplash

A six-month-old terrain model put a mooring 220 m off target. Here is how the synchronization process now works, and why the seafloor model is versioned like code.

Mooring M-09 in the Mariana array settled 220 m shallower than planned because the slope beneath it was steeper than the terrain model said. The model was six months old. In most of the ocean, six months is nothing. On an active trench slope, it was enough.

What “synchronized” means

The Bathys bathymetry model is a gridded terrain surface, 25 m resolution in surveyed corridors and 250 m elsewhere, that every other module reads: pressure mapping uses it for slope, the deployment planner uses it for settle-depth prediction, the anomaly console uses it to decide which moorings are topologically connected.

Synchronization is the process of merging new survey data into that surface and pushing the new version to every operator and every mooring controller. The engine log line Bathymetry model synchronized means all three consumers now agree on the same seafloor.

The new process

Three changes came out of the M-09 incident:

  1. Every transit is a survey. Vessels carrying Bathys hardware now run multibeam continuously between waypoints. The Mariana transit alone added 1,900 km² of 25 m coverage.
  2. The model is versioned like code. Each sync produces an immutable version with a diff report: cells changed, maximum depth delta, maximum slope delta. Operators can pin a deployment to a version and see exactly what changed before accepting the next one.
  3. Slope deltas gate deployment. If the planned mooring footprint sits on a cell whose slope changed by more than 2° in the last sync, the deployment planner refuses to proceed without an explicit override.

What changed under M-09

The diff for the post-transit sync showed a maximum slope delta of 5.3° in the M-09 footprint and a depth delta of 214 m, close enough to the observed 220 m offset that we consider the model now accurate to within our settle-depth tolerance.

Why this matters beyond Mariana

Trench slopes are the extreme case, but sediment fans, canyon walls and any seafloor near active volcanism move on timescales the array cares about. A bathymetry model that is versioned, diffed and continuously refreshed is not an accessory to the sensor array. It is one of its sensors.