What New Zealand's 3D Coastal Programme Reveals About Nearshore Surveys

What Happened

Toitū Te Whenua Land Information New Zealand (LINZ) is running a three-year programme to map up to 40% of New Zealand’s coastline – dynamic, environmentally sensitive shoreline where land meets sea in some of the Southern Hemisphere’s most challenging survey conditions. The programme targets seamless coverage from roughly 200m inland out to about 25m below the waterline, across an area on the order of 10,000km². The 3D Coastal Mapping Programme integrates aerial topobathymetric lidar, boat-deployed multibeam echosounder (MBES) acoustics, and satellite-derived bathymetry (SDB) to produce continuous elevation and seafloor datasets across the land-water interface. Its purpose is baseline data for coastal change, sea-level rise, and natural-hazard planning – tsunami and earthquake response among them.

NV5 Geospatial is delivering the South Island component, with TCarta supplying persistent satellite-derived bathymetry and water-clarity analytics. The survey scope includes steep topography, sediment-laden coastal waters whose suspended loads defeat single-sensor approaches, and areas with constrained access windows. NV5’s operational model uses near-daily satellite water-clarity assessments – built on the diffuse attenuation coefficient at 490nm (Kd490) – to inform flight planning, matching lidar acquisition to clarity windows and judging whether a poor result warrants a reflight or reflects persistent conditions unlikely to improve.

The programme works on the premise that no single technology captures the entire nearshore zone reliably. Topobathymetric lidar provides seamless land-to-sea coverage where water clarity permits, with usable penetration in clearer coastal water typically into the low tens of metres. Multibeam fills the gaps – deeper zones, turbid plumes from river discharge, areas with dynamic seafloor where repeat acoustic data confirms change. Satellite analytics act as the planning layer, indicating which areas are lidar-viable on any given day and which require the acoustic backup.

Why This Matters

Most offshore survey managers encounter the nearshore zone as an operational problem, not a technical specialty. Your cable route runs from 2,000m water depth to the beach. Your wind farm export cable crosses 8km of surf zone and intertidal flat before reaching the substation. Your port expansion requires dredge volumes calculated across the boundary where your vessel-mounted MBES loses bottom lock and your UAV-mounted lidar can’t penetrate turbidity.

The standard procurement response is to specify “seamless coverage from MLLW to +10m” and assume the survey contractor sorts it out. Then you receive two datasets with a coverage gap, a vertical offset of a few decimetres that nobody can explain, and a polite request for a contract variation to remobilise.

LINZ’s approach demonstrates what actually works when you take nearshore integration seriously: you plan for multiple sensors from the start, you acquire the environmental intelligence (turbidity, clarity, sea state) that determines which sensor works where, and you accept that operational flexibility costs less than remobilisation. National mapping agencies operate on multi-year programmes with public oversight. You operate on compressed project schedules with a capital-allocation committee that wants to know why the geophysical budget just increased. The technical lessons transfer directly.

The Reality on Deck

On a cable route survey the nearshore crossing is routinely the highest-risk segment of the entire project. Not because the water is deeper or the seabed is harder. Because it is the only place where the MBES vessel cannot operate, the lidar aircraft cannot guarantee penetration, and geodetic control crosses the boundary between terrestrial GNSS networks and offshore acoustic positioning.

The industry tendency is to treat this as a minor data-acquisition problem. Specify IHO S-44 Order 1a, add a note about “lidar where suitable”, and assume the contractor has done this before. Then the failure modes line up:

• The topobathymetric lidar dataset stops well short of target depth because turbidity from a river plume – visible on Sentinel-2 imagery for months – exceeded the water-clarity limit for laser penetration
• The MBES vessel collected only partial shallow coverage before sea state forced it offshore
• The resulting gap sits exactly where the cable crosses a shallow rocky reef the geotechnical contractor now cannot sample
• The programme director wants to know whether the gap matters for the HDD exit point or whether it can be interpolated

You cannot interpolate across a data gap where the seabed morphology might include a metre-scale vertical step. LINZ’s solution – persistent SDB as a planning layer, multi-sensor redundancy designed into the acquisition plan, adjustments driven by environmental data – addresses exactly this failure mode. Offshore managers planning nearshore work need to adopt the same model, or budget for the remobilisation.

Where Clients Get It Wrong

1. Specifying Vertical Uncertainty Without a Datum Strategy

Specifications often require tight vertical uncertainty (say 0.15m) across the land-sea boundary without defining how the contractor achieves datum consistency between terrestrial levelling networks (tied to local mean sea level benchmarks), vessel-mounted GNSS/IMU positioning (using an ellipsoidal height transformed to chart datum via a separation model), and airborne lidar (using PPP or ground-validated RTK with ellipsoid-to-orthometric corrections).

New Zealand operates a nationwide horizontal datum (NZGD2000) and a national vertical datum (NZVD2016) realised through the NZGeoid2016 geoid model, which provides ellipsoid-to-orthometric separation nationwide. A programme referencing this single framework gives every sensor a common vertical reference. A North Sea wind farm survey, by contrast, might reference ETRS89, with the vessel working in LAT via a UKHO separation model, the aerial lidar in ODN via OSGM15, and the client wanting soundings in LAT but topography in ODN. That introduces several independent sources of decimetre-level vertical offset that show up as step discontinuities in the final surface model.

Before you mobilise any nearshore survey, produce a single-page datum strategy document. Define the input datums for each sensor, the transformations applied, the reference datum for final deliverables, and the test method for verifying datum consistency across sensor boundaries. If you cannot write this document, you do not understand how your datasets will merge.

2. Single-Sensor Specifications in Multi-Sensor Environments

Clients specify bathymetric lidar as the primary sensor because it is faster and cheaper than boat-based MBES. Then they add a clause: “MBES backup in areas where lidar does not achieve specification.” This transfers the risk of lidar failure to the contractor, who must now mobilise an MBES vessel as contingency, but provides no guidance on where backup is required.

LINZ’s model inverts this. SDB and water-clarity analytics – derived from multispectral satellite data such as Sentinel-2, with clarity tracked through parameters like Kd490 – provide a reconnaissance layer showing turbidity, depth limits, and areas where lidar will likely fail. TCarta delivers this intelligence to NV5 to inform flight planning rather than discovering the problem mid-acquisition, so MBES is planned for the turbid zones rather than scrambled as a variation.

For offshore survey managers: if you are working in an environment with river discharge, sediment plumes, or seasonal turbidity variation (essentially any nearshore zone outside of tropical atolls), commission SDB reconnaissance before you finalise the survey plan. It is a modest line item against the geophysical cost. You will either confirm that single-sensor lidar is viable, or identify the areas requiring MBES before the contractor prices contingency mobilisation into their rate.

3. Ignoring Environmental Windows Until Weather Delays Start

The standard offshore survey schedule allocates weather contingency as a percentage of operational days – typically 15-25% depending on season and location. Nearshore work requires environmental contingency for turbidity, river flow, and biological access restrictions that have nothing to do with wind speed or wave height.

New Zealand’s South Island coast spans environmentally sensitive zones and waters where turbidity varies sharply between winter storm discharge and summer low-flow conditions. NV5’s operational model uses near-daily water-clarity analytics to adjust acquisition within the available windows, prioritising areas where clarity permits lidar penetration and deferring turbid zones to MBES acquisition or later lidar passes.

The failure mode in commercial work is familiar: a river-plume-fed survey area where turbidity makes bathymetric lidar unviable for much of a fixed survey window, while the contract specifies fixed mobilisation dates and offers no mechanism to adjust the schedule. The outcome is partial lidar coverage, an emergency MBES mobilisation, and a multi-month delay waiting on a vessel to fill the remaining gaps.

Before you issue the ITT, identify the non-weather environmental constraints: river discharge data for the past five years, satellite turbidity time-series, biological access restrictions from local authorities, and seasonal clarity windows. Build these into the schedule as hard constraints, not as contractor risk.

4. Underestimating the Geodetic Control Problem

Offshore GNSS positioning is comparatively simple. You operate in open sky, your PPP solution typically converges to sub-decimetre horizontal in 20-30 minutes, and your IMU provides heading and attitude with no magnetic interference. Nearshore work requires terrestrial control points for lidar calibration, intertidal zones where GNSS multipath from cliff faces degrades accuracy, and transitions between offshore PPP positioning and shore-based RTK networks.

LINZ operates a network of continuous GNSS stations (PositioNZ) providing RTK corrections nationwide, supplemented by campaign control points where the lidar contractor requires local validation. The 3D Coastal Programme uses this infrastructure to ensure that airborne lidar, boat-based MBES, and terrestrial survey data all reference the same geodetic framework with sub-decimetre consistency.

Your renewables project in a developing market has none of this. The national geodetic network ends 15km inland. The offshore positioning contractor uses PPP with ITRF2020 coordinates. The lidar subcontractor wants five ground control points with 0.05m vertical accuracy to calibrate the IMU boresight. And your survey manager assumes that “everything is WGS84” so it will merge automatically.

WGS84 is not a datum – it is a coordinate system family with multiple realisations that differ by up to 2m depending on which reference frame and epoch you use. If your nearshore survey spans the land-sea boundary, you need a geodetic control plan that specifies: reference frame (e.g., ITRF2020 epoch 2024.0), control point network with published coordinates, transformation parameters to local datum if required, and validation method for cross-sensor agreement. Writing the plan is cheap; the control-point fieldwork it specifies is the cost. That modest line item eliminates the most common cause of the “why do these datasets not merge” site meeting.

What National Mapping Agencies Understand About Multi-Sensor Integration

LINZ operates under different constraints than commercial survey contractors. It runs a multi-year programme with public-sector oversight, and stakeholder groups that include local councils, infrastructure agencies, and scientists who will use the data for years to come. It cannot deliver partial coverage with a data gap and a contract variation request.

This forces a level of technical rigour that offshore survey managers should adopt but often do not:

Acceptance that no sensor works everywhere. Topobathymetric lidar is faster and cheaper than MBES in clear, relatively shallow water. It fails in turbid water or below the depth the laser can penetrate. MBES works at any depth and in any turbidity, but costs more, requires vessel mobilisation, and cannot capture the intertidal zone. SDB gives broad spatial coverage at coarse resolution and metre-scale vertical uncertainty – inadequate for engineering surveys, well suited to planning which areas require higher-resolution sensors. A national mapping programme budgets for all three because operational efficiency depends on using the right sensor in the right place.

Environmental intelligence as a primary input, not an afterthought. TCarta’s water-clarity analytics inform NV5’s flight planning rather than being checked after a failed acquisition. This is not a luxury for national programmes; it is basic operational efficiency. If your lidar contractor mobilises to site without knowing whether the water clarity supports penetration to the specified depth, you have transferred a predictable risk to the contractor and you will pay for it through contingency pricing or variations.

Stakeholder requirements drive priority sequencing, not survey logistics. LINZ’s real-time adjustment model allows prioritisation of areas where hazard modelling or infrastructure planning has immediate need, even if this creates logistical inefficiency for the survey contractor. Offshore managers typically optimise survey lines for mobilisation efficiency – run the cable route end-to-end, complete the wind farm in sequential rows, minimise transits. Then you discover that the consenting authority needs the landfall data for the environmental impact assessment that closes in six weeks, but your plan puts that area in month four of the six-month survey.

If your project has regulatory, consenting, or engineering milestones that depend on specific survey areas, communicate these to the contractor before mobilisation and accept the cost of non-optimal survey sequencing. The cost of re-prioritising the survey is lower than the cost of missing the consenting window.

Practical Recommendations for Nearshore Survey Planning

If you are planning a cable route survey, wind farm export cable, port development, or any other project where seamless land-sea data matters:

Commission SDB reconnaissance during feasibility. Budget a modest line item for satellite-derived bathymetry and water-clarity time-series covering your survey area. This provides turbidity statistics, coarse depth profiles, and identification of areas where lidar will likely fail. Use this to write a realistic multi-sensor specification instead of a single-sensor optimistic one.

Write a one-page geodetic control plan before you mobilise. Define reference frame, epoch, control point requirements, and transformation parameters to local datum. Circulate to all survey contractors (lidar, MBES, geophysical, geotechnical) and require written confirmation that they can deliver data in the specified frame. The document itself costs almost nothing to write, yet it prevents the majority of datum-integration failures.

Budget a distinct environmental contingency, separate from weather. Nearshore turbidity, biological restrictions, and tidal windows are not weather. They require separate schedule buffers. If your project is in a river-influenced coastal zone, identify the low-turbidity season from historical satellite data and schedule lidar acquisition accordingly.

Specify sensor crossover zones and mandate overlap data for QC. Require that MBES and lidar both acquire data in a 100m-wide crossover zone where both sensors are viable. Use the crossover statistics (mean difference, standard deviation, spatial bias) to verify datum consistency before you accept the survey. IHO S-44 requires crossover analysis for uncertainty validation. Enforce it.

Do not interpolate across data gaps in the nearshore zone. The seabed morphology in the surf zone and intertidal area is far more variable than in deep water. A data gap of even a few tens of metres might contain a rock outcrop, a scour channel, or a reef that matters for cable route engineering. If your specification requires full coverage, enforce it. If you accept gaps, accept the geotechnical risk that comes with them.

LINZ’s 3D Coastal Mapping Programme is not directly comparable to a commercial offshore survey – it has longer timescales, different cost structures, and a requirement to serve multiple stakeholders rather than one project director. But the technical approach – multi-sensor planning from the start, environmental intelligence driving operational decisions, geodetic rigour across sensor boundaries – is exactly what offshore managers should adopt for nearshore work.

The alternative is the approach seen too often: specify single-sensor coverage, assume the contractor will solve the integration problem, and discover at the data delivery meeting two datasets with a vertical offset, a horizontal gap, and a request for an extension to remobilise.

---

Based on: The Art of Mapping the Edge