SonarWiz 8.7.2: Keeping Marine Survey Evidence Connected

A cable-route survey can produce a convincing seabed mosaic while leaving the engineer uncertain about contact positions, sediment boundaries or gaps in coverage. SonarWiz is worth considering when those observations need to stay connected across acquisition, processing and interpretation. This research-based technical assessment uses official sources checked on November 8, 2026 UTC; we did not independently install or test the software.

Chesapeake Technology, Inc. develops SonarWiz. Its company history says Engadin Group acquired a majority stake from founders John and Eileen Gann in early 2025. The current download page identifies SonarWiz 8.7.2, released October 5, 2026, as the latest release. That maintenance update matters operationally: the release notes describe fixes for remembered Web License login and connections behind corporate proxies or TLS inspection.

Start with the survey deliverable, then choose the modules

The product portfolio covers sidescan, sub-bottom, bathymetry, single beam and magnetometry. That breadth does not mean a single entitlement covers every task. The 8.07 real-time user guide explicitly distinguishes acquisition licenses for bathymetry, sidescan, sub-bottom and single-beam collection. The SonarWiz 8 format matrix likewise ties import categories to the corresponding post-processing license.

For a route investigation, define whether the contract requires acoustic imagery, interpreted reflectors, bathymetric surfaces, magnetic anomalies or all of them. Then ask the supplier to map those deliverables to collection modules, office-processing seats and sensor-server versions. A list of supported sensor brands is too broad to establish compatibility with a particular head, firmware and logging configuration.

From raw pings to contacts and interpreted layers

Chesapeake’s sidescan documentation describes loading charts and background rasters, planning lines, acquiring sonar with navigation and other sensor inputs, and monitoring GPS quality and coverage. Post-processing includes navigation repair, layback configuration, bottom tracking, gain controls and contact capture. The vendor states that its real-time gain controls affect the display rather than raw data. For engineering review, that distinction supports keeping acquisition records separate from presentation choices; it does not establish the positional accuracy of a contact.

A useful acceptance exercise would follow one raw line through navigation correction, bottom selection, mosaic generation and a contact report. Check what happens when the towfish position differs from vessel navigation, how a manual bottom-track edit is recorded, and whether a second interpreter can recover the same source observations. These are proposed procurement checks, not results obtained here. The documented report outputs include PDF, OpenOffice, Microsoft Word and HTML, while survey-map outputs include GeoTIFF and GeoPDF.

The sub-bottom product page documents manual or automatic bottom tracking, navigation repair, tide/draft correction using Datum Align to Bathy Grid, swell filtering, reflector annotation and an isopach/thickness tool. It also describes a 3D viewer combining lines, DTMs, mosaics and digitized features. Layer thickness remains an interpretation requiring an explicit velocity and datum basis; an attractive section alone is not an acceptance criterion. Ask how the proposed workflow records those assumptions and handles ambiguous reflectors before relying on its deliverables for burial or geohazard decisions.

Treat file exchange as a configuration check

The official format matrix, updated August 18, 2025, is more useful than a universal compatibility claim: it reports PASS, FAIL and NOT TESTED results against V8.04.00 for individual sensor/format combinations. Those older results are not a certification of 8.7.2. For example, an extension such as XTF or JSF does not by itself establish support for every record subtype. Use representative files, including navigation and ancillary channels, to confirm the exact import and export path with the vendor.

For a project combining sonar and magnetic interpretation, our Oasis montaj assessment provides context for the separate geophysical processing decision. Further downstream, OrcaFlex addresses coupled offshore structural analysis; a survey-derived seabed model may inform that work, but neither this assessment nor the cited sources establish an automatic connector. Coordinate reference systems, vertical datums, units and interpretation provenance need an agreed handover specification. A general-purpose SonarWiz API contract was not verified in the reviewed sources; confirm automation requirements separately.

Windows, field licensing and the cloud-support boundary

The system requirements page lists Windows 10 through Windows 11, administrator installation, approximately 2 GB of installation space, at least 8 GB RAM, DirectX 11 graphics and a 1024 × 768 minimum display. These are vendor requirements, not a sizing result for a full survey archive. The same page supports Windows instances on AWS and Azure while also stating no support for VM environments and no tested Mac support. Obtain written approval for the exact hosted or virtual configuration rather than interpreting cloud support as blanket virtualization approval.

The license-platform note describes USB, dongle-free, network and evaluation arrangements, but was updated in 2022. It predates the Web Licensing introduced in 8.6.0 and the offline-use and secure-environment activation changes listed for 8.7.0 in the current release history. It therefore cannot settle current offline durations, transfers or all field-use rights. Before mobilization, confirm the exact license mechanism, loss-of-connectivity behavior, replacement procedure and collection entitlements. The download page ties major/minor updates to a current EMA subscription and warns that older versions cannot always be supported; confirm the support term and response arrangements in the order.

When a narrower processor deserves a separate evaluation

For a primarily multibeam-processing assignment, QPS Qimera is a relevant alternative for that part of the workflow. QPS documents point-cloud editing, full ray-trace processing, patch-test and wobble tools, with separate package and add-on boundaries. Compare raw-format coverage, calibration diagnostics, correction history, required exports and licensed modules on the same survey dataset. This is not evidence that Qimera replaces SonarWiz’s entire sidescan/sub-bottom acquisition workflow, or that either package is faster or more accurate.

SonarWiz is a credible candidate when a team needs connected collection and interpretation of several marine survey data types. The evidence is strongest for the documented workflow, module boundaries and current release identity; it is weaker for the exact deployment, automation interface and commercial entitlement a buyer will receive. Prefer a focused alternative evaluation when the procurement is chiefly about multibeam processing, and make the SonarWiz purchase conditional on a demonstrated sensor-to-deliverable path, current compatibility confirmation and a field-license arrangement that survives the intended operating conditions.