Dredging Volume Computation

Cover image
Published: Olalekan Odunaike  |  Author: Omar Ahmed  |  Source: LinkedIn
Tags: #average_end_area, #computation, #cross_section, #dredging, #grid_based, #hydrographic, #hydrospatial, #survey, #tin_to_tin, #volume

Technical Explanation

Technical Explanation: Dredging Volume Computation in Hydrographic and Geodetic Practice

What the Image Communicates

The image illustrates a typical post-dredge hydrographic survey scenario: a survey vessel collects bathymetric data over a dredged area, and the resulting seabed model is compared to a pre-dredge (or design) model to compute dredged volume. The text in the image highlights three common computation approaches used in hydrospatial workflows:

  • TIN-to-TIN (Triangulated Irregular Network surface differencing)
  • Grid-based (raster/cell-based surface differencing)
  • Average End Area (cross-section method)

Conceptually, all three methods estimate the volume between two reference surfaces (before/after, or existing/design) within a defined boundary. The selection of method should be driven by project objectives (payment vs. engineering control), seabed morphology, required uncertainty, and survey line density.

Core Definitions and Concepts

Dredging Volume

Dredging volume is the quantity of material removed (or placed, for reclamation) between two epochs or between an existing seabed and a design template. In hydrographic terms, it is calculated as:

Volume = ∫∫ (Surfacereference − Surfacecomparison) dA over a defined area.

Depending on the contract, “reference” may be pre-dredge, design, or a specified control surface. “Comparison” is typically the post-dredge survey surface.

Hydrospatial Surfaces

Bathymetry points are converted into surfaces to enable differencing:

  • TIN surface: irregular triangles capturing detail where data is dense; efficient for irregular sampling.
  • Grid (raster) surface: regular cells with a single depth value per cell; straightforward for repeatable differencing and reporting.

Computation Methods Referenced in the Image

1) TIN-to-TIN Method

TIN-to-TIN computes volume by building a TIN for each epoch (e.g., pre- and post-dredge), then integrating the vertical separation between the two triangulated surfaces across the boundary polygon.

Advantages:

  • Works well with irregularly spaced hydrographic soundings.
  • Can preserve sharp features (e.g., dredge cut edges) if data supports them.
  • Common in hydrographic software for precise surface differencing.

Disadvantages / risks:

  • Results can be sensitive to triangulation rules (breaklines, maximum triangle size, edge handling).
  • Requires careful control of boundary effects and extrapolation outside soundings.
  • May be less transparent to non-technical stakeholders than grid-based reporting.

2) Grid-Based (Raster) Method

Grid-based computation creates a raster for each epoch at a defined cell size (e.g., 0.5 m, 1 m, 2 m). Volume is computed by summing (depth difference × cell area) for all cells inside the boundary.

Advantages:

  • Highly repeatable and easy to audit (cell size, interpolation, and boundary are explicit).
  • Supports standardized reporting and heatmaps (cut/fill maps).
  • Often preferred for operational monitoring and contract deliverables.

Disadvantages / risks:

  • Choice of cell size strongly affects results; too coarse smooths features, too fine may amplify noise and interpolation artifacts.
  • Interpolation method (mean, shoalest, nearest, CUBE, kriging, etc.) influences computed volumes.
  • In sparse data areas, gridding can introduce bias if not constrained by survey design.

3) Average End Area (Cross-Section) Method

Average End Area computes volume along a corridor using cross-sections at regular spacing. For consecutive sections, volume is approximated as:

V ≈ (A1 + A2)/2 × L, where A1 and A2 are end areas and L is distance between sections.

Advantages:

  • Simple, widely understood in civil/earthworks contexts.
  • Useful for channels where design control is specified by section templates.
  • Can align well with dredging production management along centerline chainage.

Disadvantages / risks:

  • Less representative for complex seabed morphology outside section lines.
  • Highly dependent on section spacing and how each cross-section is extracted from the surface.
  • May under/over-estimate where changes occur between sections (e.g., localized shoals or pockets).

Instrumentation in Hydrographic Dredging Surveys

Bathymetric Sensors

  • Singlebeam Echo Sounder (SBES): economical, common for smaller areas and control lines; requires denser line planning for reliable surfaces.
  • Multibeam Echo Sounder (MBES): provides full coverage and is typically preferred for dredging acceptance, shoal detection, and robust volume estimates.

Positioning and Attitude

  • GNSS (RTK/Network RTK/PPP): provides horizontal and vertical positioning; vertical strategy must be consistent with the project datum (tide vs. GNSS tide/VDatum approach).
  • INS/MRU (IMU): measures heave, pitch, roll; critical for MBES and for accurate seabed modeling.
  • Gyrocompass or GNSS heading: provides heading; dual-antenna GNSS heading is common on smaller vessels.

Sound Speed Measurement

  • SVP/CTD casts: profile sound speed through the water column for ray-tracing corrections.
  • Sound speed sensor at transducer: real-time near-surface sound speed for MBES beamforming.

Ancillary

  • Tide gauge (if using observed tides): brings depths to chart datum (e.g., LAT) or project datum (e.g., MSL).
  • Settlement plates / density checks (optional): for placed material or soft bottoms where “true bottom” definition matters.

Survey Setup, Calibration, and Field Procedures

Vessel and Sensor Geometry

Accurate volume computation depends on rigorous control of the vessel reference frame and sensor offsets:

  • Reference point selection (typically GNSS antenna reference point or vessel reference frame origin)
  • Lever arms (X/Y/Z offsets from reference point to transducer, IMU, antennas)
  • Alignment angles (roll/pitch/yaw misalignment between sonar and IMU)

Patch Test / Calibration

For MBES, a patch test is used to calibrate timing (latency), roll, pitch, and yaw (heading) biases. These are essential because small angular errors can produce significant depth and horizontal errors across the swath, directly impacting computed cut/fill volumes.

Bar Check and SBES Verification

SBES systems may use a bar check to verify draft and sound speed assumptions in shallow water. Even when SVP is used, a practical verification step is valuable for confidence and traceability.

Geodetic Frames, Coordinate Reference Systems, and Datums

Horizontal Reference Frame

Dredging projects typically require a defined horizontal CRS, for example:

  • ITRF/WGS84-derived GNSS frame (realized through RTK/PPP)
  • National datum (e.g., ETRS89, NAD83, or local grid)
  • Projection (e.g., UTM zone or a local engineering projection)

All epochs (pre- and post-dredge) must be processed in the same horizontal CRS to avoid false volume differences due to datum shifts.

Vertical Reference: LAT, MSL, and Separation Models

Vertical consistency is a dominant factor in dredging quantities.

  • LAT (Lowest Astronomical Tide): a chart datum used for navigation and dredging acceptance in many jurisdictions. Reducing soundings to LAT requires tide models or observed tides tied to LAT.
  • MSL (Mean Sea Level): used for engineering, coastal works, and some national vertical references; not interchangeable with LAT without a defined relationship.

Vertical workflows commonly follow one of two strategies:

  • Tide-based reduction: measured water levels from a tide gauge (and zoning if required) applied to observed depths.
  • GNSS-based vertical referencing: ellipsoidal heights from GNSS are transformed to the project vertical datum using a geoid model and/or hydrodynamic separation surfaces (e.g., ellipsoid-to-LAT).

For dredging, it is critical to state clearly whether computed depths/volumes are referenced to LAT, MSL, or another project datum, and to document the applied separation model and its uncertainty.

Time Synchronization and Latency Control

Hydrographic systems are multi-sensor and require precise timing:

  • GNSS time (UTC) is commonly the master clock.
  • 1PPS and NMEA time messages may be distributed to sonar and INS.
  • Latency (timing offset between position, attitude, and sonar) must be measured and applied; uncorrected latency causes horizontal displacement of soundings, which can distort dredge cut edges and bias volumes.

For MBES volume computations, timing control is not optional; it is a primary contributor to surface fidelity.

Data Processing Workflow (End-to-End)

1) Data Acquisition and Logging

  • Plan line spacing to meet required coverage and uncertainty.
  • Log raw sonar, raw GNSS/INS, sound speed, and tide (if applicable).

2) Apply Core Corrections

  • Sound speed (surface + profile) and ray tracing (MBES)
  • Draft/settlement and waterline reference
  • Tide or GNSS vertical transformation to project datum (LAT/MSL)
  • Heave, pitch, roll, heading, and sensor offsets
  • Latency and any smoothing/filters documented and justified

3) Cleaning and Outlier Rejection

  • Automated filters (range, angle, reject spikes) followed by manual review
  • Special attention to dredging environments: turbidity, aeration, and slope edges

4) Create Surfaces

  • Build pre-dredge and post-dredge surfaces using consistent parameters
  • Document interpolation method, gridding resolution, and any breaklines

5) Compute Volume

  • Define the computation boundary (dredge limits, acceptance area, or payment polygon)
  • Compute cut/fill and net volume using TIN-to-TIN, grid-based differencing, or cross-sections
  • Report both gross cut, gross fill (if applicable), and net quantities with units and datum

6) Reporting and Deliverables

  • Surface difference plots and statistics
  • Sounding density/coverage maps
  • Metadata: datum statements, calibration, uncertainty, processing settings

QA/QC, Uncertainty, and Auditability

Why Uncertainty Matters for Volume

Volume is an integrated quantity. Small systematic vertical biases (e.g., a constant 0.05 m datum error) over a large area can produce large volume differences. Therefore, dredging projects should control and document:

  • Vertical uncertainty (tide model/gauge, GNSS+geoid, heave, sound speed)
  • Horizontal uncertainty (GNSS solution quality, heading, latency)
  • Surface model uncertainty (grid size, interpolation, data density)

Common QA/QC Checks

  • Crosslines/checklines: quantify consistency and detect biases
  • Repeatability: re-run a subset and confirm stable differences
  • Patch test validation: confirm no residual roll/pitch/yaw artifacts
  • Tide/vertical checks: compare gauge vs. GNSS-derived water level when possible
  • Sound speed stability: monitor refraction artifacts (smiles/frowns) in MBES

Method Selection as a QA/QC Decision

In practice, teams often compute volume using more than one method (e.g., grid-based and TIN-to-TIN) as a reasonableness check. Differences should be explainable through resolution, interpolation, and boundary handling rather than unexplained processing variability.

Real-World Applications

  • Dredging payment and verification: compute removed quantities within contract limits and to the specified datum (often LAT).
  • Navigation safety and compliance: confirm achieved depths and identify remaining shoals.
  • Port and channel maintenance planning: prioritize areas of infill and estimate future dredging needs.
  • Environmental management: quantify sediment removal/placement, support turbidity and habitat constraints.
  • Construction support: verify excavation for quay walls, pipelines, cable routes, and reclamation.

Practical Guidance on Choosing a Method

  • Use TIN-to-TIN when your data spacing is irregular, you need faithful representation of complex morphology, and you can control triangulation parameters and breaklines rigorously.
  • Use Grid-based when you need repeatable, auditable reporting and clear control over resolution; ensure cell size matches survey density and project tolerances.
  • Use Average End Area when the project is section-driven (channel templates, chainage reporting) and you have sufficiently tight section spacing to represent variability.

Key Takeaway

The image’s central message is operationally correct: after dredging, the survey team re-surveys and computes volume by comparing two seabed representations. In professional hydrography and geodesy, the reliability of that volume hinges less on the chosen mathematical method and more on datum control (LAT/MSL), sensor calibration, time synchronization, sound speed management, and disciplined QA/QC. When these fundamentals are rigorously managed, TIN-to-TIN, grid-based differencing, and cross-section methods become consistent tools suited to different reporting and contractual needs.

Details & Context


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