MBES Survey System Integration

LinkedIn image 1
Published: Olalekan Odunaike  |  Author: Adnan Ali  |  Source: LinkedIn
Tags: #bathymetry, #gnss, #gyrocompass, #hydrographicsurvey, #hydrography, #marinesurvey, #marinetechnology, #mbes, #mru, #multibeamechosounder, #offshoresurvey, #seafloormapping, #soundvelocity, #surveysystems, #twozansurveys

Technical Explanation

Overview of the Image: “MBES Survey System Integration – Sensors, Connections, and Data Flow”

The image is a simplified system diagram showing a typical Multibeam Echo Sounder (MBES) hydrographic survey setup installed on a small survey vessel. It illustrates (1) the main sensors required to compute georeferenced bathymetry, (2) how measurements flow into hydrographic acquisition software, and (3) how MBES acoustics form a swath (a footprint of seabed soundings per ping) that is later processed into a seabed surface or charting product.

Key components depicted include a laptop running acquisition software, primary and secondary GNSS antennas, a gyrocompass, a motion sensor (MRU/IMU), a sound velocity profiler (SVP), and the MBES transducer emitting multiple beams across-track to build a high-density bathymetric point cloud. A second image shows a coastal marine scene (likely contextual), but the primary technical content is in the MBES integration diagram.

Core Definitions in Hydrography and Geodesy

Bathymetry and Swath Mapping

Bathymetry is the measurement and modeling of underwater depth and seabed morphology. In MBES, one ping produces many depth estimates (soundings) across a swath, enabling efficient coverage of large areas with high spatial density compared to single-beam echo sounders.

The image labels “swath angle (256–512)” which appears to mix swath opening angle (degrees) with a typical number of beams. In practice:

  • Swath opening angle is commonly specified in degrees (e.g., 90°–160° total), varying by system and settings.
  • Beam count may be 128/256/400/512+ depending on model and mode.

MBES Range and Depth Principle

Depth is derived from acoustic two-way travel time and sound speed. For each receive beam, the system estimates a slant range; then, with steering angle information (beam angle), vessel attitude, and sound speed profile, it computes an XYZ position for each sounding in a defined coordinate reference frame.

Instrumentation Shown and What Each Sensor Contributes

1) Multibeam Echo Sounder (MBES) and Transducer

The transducer (shown hull-mounted) transmits and receives acoustic pulses using an array. MBES uses either:

  • Beamforming on receive (and often transmit), producing many narrow beams; or
  • Phase-differencing / interferometric techniques in some systems.

The diagram shows outer beams and a nadir region. Outer beams increase coverage but are more sensitive to sound speed errors, attitude errors, and seabed slope.

2) Motion Reference Unit (MRU) / IMU (Roll, Pitch, Heave)

The image labels a “Motion Sensor (to calculate roll, pitch & heave).” This unit measures:

  • Roll (rotation about longitudinal axis),
  • Pitch (rotation about transverse axis),
  • Heave (vertical motion of vessel), and sometimes
  • Yaw rate and accelerations (if IMU-grade).

Motion compensation is fundamental: uncorrected roll/pitch directly tilts beams, shifting seabed soundings laterally and vertically; heave affects all depths.

3) Gyrocompass (True-North Heading)

The “GYRO → Compass” element indicates a gyrocompass providing true heading (not magnetic). Accurate heading is essential to rotate the swath correctly into geographic coordinates and to ensure consistent line overlaps. In small-vessel operations, a GNSS heading system (dual-antenna) often substitutes for or complements a gyrocompass.

4) GNSS Positioning (Primary and Secondary)

The diagram shows:

  • Primary GNSS “to get a positioning & calculate tide” (interpretable as position + vertical referencing), and
  • Secondary GNSS (for heading) indicating a dual-antenna baseline used to compute heading.

In modern hydrography, the GNSS subsystem may provide:

  • Horizontal position (RTK, network RTK, PPP, or DGPS as appropriate),
  • Ellipsoidal height (used for GNSS tide / vertical referencing), and
  • Heading (from a two-antenna system) if no gyro is used or as redundancy.

5) Sound Velocity Profiler (SVP) and Sound Speed Control

The SVP in the image is shown as a cast instrument. It measures sound speed versus depth through the water column, capturing stratification (temperature, salinity, pressure effects). This profile is used for:

  • Ray-tracing (refraction correction) of the acoustic beams,
  • Improving accuracy in outer beams and variable water masses,
  • Reducing artifacts such as “smiles/frowns” and across-track depth bias.

Best practice also includes a surface sound speed sensor (SSS) near the transducer to correct immediate transducer-level sound speed; many systems require both SSS (real time) and SVP (periodic casts).

6) Hydrographic Data Acquisition Software

The laptop represents acquisition/control software that collects, time-tags, and merges data streams (MBES, GNSS, heading, motion, sound speed) to produce preliminary georeferenced soundings in real time and record raw data for post-processing.

System Geometry and Setup: Integration Matters

Lever Arms and Sensor Reference Points

Hydrographic georeferencing depends on knowing the 3D offsets (lever arms) between sensors (GNSS antenna reference points, IMU center, transducer reference point) measured in the vessel reference frame. These must be surveyed accurately (typically to millimeter–centimeter level, depending on required IHO order and depth regime) and documented consistently.

Alignment Angles (Mounting Misalignment)

Even with correct lever arms, small angular misalignments between the MBES and IMU frames produce systematic errors. Typical alignment angles include:

  • Roll alignment (transducer roll vs IMU roll),
  • Pitch alignment, and
  • Yaw/heading alignment (boresight in azimuth).

Frequency Choice: Shallow vs Deep Water

The diagram notes that shallow surveys often use high frequency (HF) and deep surveys use low frequency (LF). This aligns with physics:

  • HF (e.g., 200–700 kHz): higher resolution, shorter range, more attenuation; typical for harbors and nearshore.
  • LF (e.g., 12–70 kHz): longer range for deep water, larger footprints, typically lower detail.

Calibration and Validation (Patch Test and System Checks)

Patch Test (Boresight Calibration)

To achieve rigorous bathymetry, an MBES system typically undergoes a patch test to determine residual misalignments and timing biases. Standard components:

  • Latency (timing offset): detected by running reciprocal lines or dynamic maneuvers over a feature.
  • Roll bias: derived from overlapping lines run in opposite directions over a flat seabed or slope.
  • Pitch bias: derived from lines run in opposite directions over a distinct feature/slope.
  • Yaw (heading) misalignment: derived from crossing lines over a feature, analyzing along-track displacement.

Sound Speed Validation

Frequent SVP casts (and correct application of surface sound speed) are a primary control on data quality. Indicators of sound speed issues include across-track curvature, mismatches between adjacent lines, and beam-dependent depth biases.

Performance Checks

Additional checks typically include bar checks (where applicable), GNSS quality monitoring, IMU status (alignment, aiding), and crossline analysis to quantify repeatability.

Geodetic Frames, Datums, and Vertical Referencing (LAT/MSL)

Horizontal Datum and Coordinate Reference Frame

Bathymetry products must be delivered in a well-defined horizontal datum and projection (e.g., WGS 84 / ITRF realizations, regional datums, UTM zones, or national grid). In offshore contexts, WGS 84 (with an explicit epoch/realization) is common; in coastal/national charting, a national datum may be mandated.

Vertical Datum: LAT and MSL

The image mentions “calculate tide,” which in hydrography connects to vertical datum reduction. Two commonly referenced datums are:

  • LAT (Lowest Astronomical Tide): widely used for nautical charting because it is a conservative datum for under-keel clearance. Charted depths reduced to LAT tend to be shallower (safer for navigation).
  • MSL (Mean Sea Level): used for engineering, coastal studies, and some scientific products, representing an averaged sea level surface over a defined period.

Tide Reduction vs GNSS Tide (Ellipsoidal Referencing)

There are two broad approaches for reducing observed depths to a chart datum like LAT:

  • Tide gauge approach: observe water levels at a tide station, transfer corrections to the survey area (with zoning/TCAR where needed), and apply to depths.
  • GNSS-based vertical referencing (“GNSS tide”): use precise GNSS ellipsoidal heights plus a separation model that relates ellipsoid, geoid, and chart datum (e.g., ellipsoid-to-LAT via VDatum-style or national models). This can reduce dependency on local gauges but requires robust models, careful QC, and consistent epochs.

Geodetically, surveyors must manage relationships among the reference ellipsoid, the geoid (often approximating MSL), and the chart datum surface (LAT or other). Errors in these surfaces directly appear as vertical biases in delivered bathymetry.

Time Synchronization: The Hidden Backbone of Integration

The image emphasizes “processing all data coming from GPS–Motion Sensor–SVP–MBES,” which is only valid when streams are accurately time-tagged and aligned.

Why Timing Matters

At typical survey speeds, a 0.05–0.10 second time offset can create significant horizontal displacement of soundings; combined with slopes, this becomes vertical error. Time synchronization affects:

  • Position vs ping time,
  • Heading and motion interpolation to ping time,
  • Heave timing (especially in rough seas),
  • Sound speed updates and real-time beam steering (depending on system).

Typical Synchronization Methods

  • 1PPS (one pulse per second) from GNSS to timestamp pings and/or discipline a survey clock,
  • NMEA/serial time messages and time-stamped UDP packets,
  • PTP (IEEE 1588) in networked architectures for precise multi-sensor timing.

A rigorous installation includes documented latency values, cabling/interface specifications, and verification tests under motion.

Data Processing Workflow: From Raw Pings to Deliverables

1) Acquisition and Logging

During acquisition, the system logs raw acoustic data, navigation, attitude, sound speed, and system metadata. Real-time displays provide coverage, data density, and quality indicators (beam QC flags, bottom detect confidence, heave/motion status, GNSS quality).

2) Post-Processing Navigation and Attitude

Common steps include:

  • GNSS post-processing (if not RTK) and smoothing/quality filtering,
  • Heave filtering (true heave estimation vs delayed heave depending on system),
  • Heading validation (gyro vs GNSS heading comparisons, spike removal).

3) Sound Speed and Refraction Corrections

SVP casts are edited and applied across time and space. In areas with strong stratification or changing water masses, frequent recasts and/or underway profiling are essential to prevent refraction artifacts.

4) Cleaning, Editing, and Surface Generation

Bathymetric processing generally includes:

  • Automatic filters (range, angle, amplitude/quality, TPU-based filters),
  • Manual review in cross-sections (particularly outer beams and over complex terrain),
  • Creation of a gridded surface (DTM) at an appropriate resolution,
  • Computation of volumes for dredging applications where required.

5) Corrections and Ancillary Products

  • Sounding reductions to LAT/MSL (tide or GNSS-tide method),
  • Backscatter processing (if recorded) for seabed characterization,
  • Feature detection and object investigation workflows (e.g., contacts/hazards).

QA/QC and Uncertainty: Making Data Defensible

Total Propagated Uncertainty (TPU)

A defensible MBES product requires estimating and controlling Total Propagated Uncertainty. TPU typically incorporates:

  • GNSS horizontal and vertical uncertainty,
  • Heading uncertainty and its effect on outer beams,
  • Roll/pitch/heave uncertainty and timing,
  • Lever arm and alignment uncertainties,
  • Sound speed uncertainty and profile mismatch/refraction effects,
  • Acoustic detection uncertainty (bottom detect, footprint effects, noise).

TPU is often evaluated against IHO S-44 survey order requirements (where applicable) and validated using crosslines, repeat lines, and comparisons to control areas or known reference surfaces.

Practical QC Techniques

  • Crossline analysis: confirm that independent passes agree within tolerance.
  • Line-to-line consistency: check for striping, steps, and refraction smiles.
  • Beamwise residual checks: identify outer-beam bias and noise growth with angle.
  • Coverage verification: ensure specified overlap and no holidays (gaps).
  • Datum sanity checks: confirm correct ellipsoid, geoid, and chart datum transformations.

Real-World Applications Tied to the Diagram

The image’s stated use cases align with standard hydrographic and geospatial workflows:

  • Navigation channel mapping: high-density MBES supports safety-of-navigation surveys, detection of shoals, and confirmation of maintained depths.
  • Dredging monitoring and volume calculations: repeat MBES surfaces enable cut/fill analysis and quantity verification for dredge contracts.
  • Seabed inspection and hazard detection: identification of obstructions, boulders, debris, pipelines/cables (often paired with side-scan sonar and/or backscatter).
  • Nautical chart updates: provision of validated reduced soundings and derived products suitable for cartographic generalization and update workflows.
  • Offshore survey and marine technology integration: MBES systems form a central component in route surveys, pre-installation assessments, and site characterization when combined with geophysics and positioning.

Connecting the Image to Best Practice in Hydrographic/Geodetic Operations

The diagram correctly communicates the essential concept: MBES data quality is a systems-integration outcome. A multibeam alone does not “make a map.” Hydrographic success requires:

  • Rigid, well-measured installation geometry (lever arms and frames),
  • High-quality heading and attitude for beam steering and georeferencing,
  • Appropriate sound speed measurement and application,
  • Strict time synchronization and latency control,
  • Explicit datums and robust vertical referencing (LAT/MSL via tide or GNSS methods),
  • A disciplined processing workflow with documented QA/QC and uncertainty reporting.

When these elements are executed correctly, the MBES swath shown in the image becomes a traceable, geodetically consistent 3D representation of the seabed suitable for navigation safety, engineering, environmental assessment, and offshore development.

Details & Context


Credit: Article assembled by Olalekan Odunaike from a LinkedIn post by Adnan Ali.