Skip to content
TOKNAV

RESULTS AND PROCESSING

Hydrographic Survey Data Examples: Points, Grids and Sonar Images

Read a real gridding-report example and explore TOKNAV-supplied terrain and sonar screenshots. Understand what each output tells you before specifying the deliverables for a survey.

3,117 input records become 6,400 grid nodes

The supplied seven-page GridDataReport — underwater terrain data records a processing run generated on April 13, 2026. Its input filename is an underwater-terrain CSV. This date identifies the report generation, not a confirmed field-survey date.

3,117Input records reported
KrigingPoint interpolation method
6,400Output nodes · 64 × 100 grid
Values transcribed from the supplied report
Report fieldRecorded valueHow to interpret it
Original / active data (pages 1–2)3,117 / 3,117Record counts reported by the processing software; raw acquisition data are not provided with this example.
Method (page 5)Kriging, PointThe surface is interpolated from the input records.
Grid dimensions (page 6)64 rows × 100 columns6,400 output nodes are not 6,400 independently measured soundings.
Filled / blanked nodes (page 6)6,400 / 0A fully filled grid does not demonstrate complete measured coverage.

The report does not establish the survey equipment, coordinate and vertical references, independent check results or measurement uncertainty. Its standard deviation and standard error describe the data or grid; they are not an accuracy test against independent reference measurements.

A single-beam terrain-model example

Supplied terrain-model screenshot in Surfer
Terrain-model visualization from the supplied single-beam materials. Its correspondence to the gridding report above has not been established; they are shown as separate examples.

A rendered surface helps explain shape, but a complete delivery should also distinguish measured lines from interpolation and identify data gaps. Request a readable scale, units, coordinate reference and processing description with the final model.

Watch the acquisition and export workflow →

Multibeam point-cloud and surface views

These supplied screenshots show several views of underwater terrain. The BlueView software labels are retained. They illustrate result formats; the source images do not establish the vessel model, sonar configuration or a project acceptance grade.

Wide plan view of a supplied terrain dataset
Wide plan view: useful for seeing the context and extent of the displayed dataset.
Side view of a supplied underwater terrain dataset
Side view: compare changes in the displayed terrain profile.
Plan view of a connected terrain survey area
Plan detail: inspect the shape of the displayed survey area.
Perspective view of a supplied multibeam surface
Perspective view: interpret relative terrain shape, with the final deliverable requiring units and a scale.
Point-cloud overview following a river bend
River overview: inspect the overall geometry of the displayed corridor.
Perspective point-cloud view across a river channel
Channel perspective: inspect cross-channel shape in the visualization.
Detailed perspective view of a riverbed point cloud
Channel detail: a closer view of the displayed bed geometry.
Oblique view of a river point cloud in processing software
Oblique view: compare the point representation with the other river views.

See the multibeam equipment installation · Plan the full sensor package

Side-scan mosaic: an imaging output

Supplied yellow-toned side-scan sonar mosaic
Supplied side-scan mosaic. No target identity, survey location or depth-accuracy claim is assigned to this image.

Side-scan imagery and a bathymetric surface answer different questions. For inspection work, specify the targets of interest, image coverage, positioning requirements and the method for confirming interpretations.

Watch side-scan installation →

What makes a survey result traceable?

  • Source sonar and positioning records linked to a dated project and equipment configuration.
  • Coordinate and vertical references, sensor offsets, water-level and sound-velocity corrections.
  • Processing settings, rejected or reacquired data and a distinction between measured and interpolated areas.
  • Independent check lines or reference checks, documented differences and the agreed acceptance criteria.

Use IHO S-44 or the applicable project specification to define requirements. These examples do not establish compliance with a survey order.

Download the project and data-quality checklist

WhatsApp