RTK That Fixes but Does Not Agree: Mangrove Pipeline Control
You are the survey technologist on a 12 km pipeline route survey through mangrove creeks near Oloibiri, Bayelsa State. The GNSS base receiver sits on a 1970s control pillar whose published coordinates are in the Nigerian Transverse Mercator projection on the Minna datum. The rover is configured to output NTM directly. Over two days it reports fixed solutions with 13 to 15 satellites and PDOP between 1.9 and 2.3, yet repeat observations on the same detail points scatter by 0.4 to 0.8 m horizontally. Baselines from the base reach 9 km. Check shots to two other pillars differ from their published values by 0.35 m and 1.12 m. Midday sessions are clearly worse than early morning. The contractor needs coordinates in 48 hours to start clearing, and the project manager says the fix is fixed, so just average the shots and send them.
1. Separate what is causing the repeat scatter from what is causing the disagreement with the published pillars. What would you check first, and what does each symptom tell you?
Read the worked answer
Two different faults are being conflated.
Internal precision. 13 to 15 satellites with PDOP 1.9 to 2.3 means the satellite geometry is adequate, so a 0.4 to 0.8 m repeat scatter is not a sky-view problem. The prime suspect is the base: a 9 km single-baseline RTK link in the tropics sits at the edge of ionospheric decorrelation, and the midday deterioration matches the diurnal ionospheric pattern. Secondary suspects are multipath under the mangrove canopy, a low elevation mask, and a base position obtained by averaging rather than by an authoritative coordinate. Check the mask setting, how the base coordinate was entered, and whether the antenna was centred over the pillar mark.
External accuracy. Differences of 0.35 m and 1.12 m, unequal in magnitude and not in a single direction, are not the signature of one rigid transformation error, which would give a nearly uniform shift. So treat them as evidence that the pillars themselves, or the base coordinate, are unreliable.
First actions: compute inter-pillar distances from the published coordinates and compare with measured, inspect the pillar descriptions and any resurvey records, and occupy the base independently. Report nothing to the contractor until the control question is settled.
2. Set out the control procedure you would adopt so that the delivered coordinates are defensible, including how you handle the datum and projection.
Read the worked answer
- Do not derive the base coordinate from the RTK session. Occupy each of the three pillars with static GNSS for 60 to 90 minutes, logging at 1 s, with a clear horizon and antenna height measured vertically and slant as a check.
- Process in ITRF, then derive the transformation to Minna datum and NTM from the pillars that agree, using a 2D Helmert with at least three common points, and inspect the residuals point by point. Residuals above roughly 0.1 m mean the control set is inconsistent and must be referred to the state Office of the Surveyor-General rather than forced.
- Apply the projection correctly: scale factor at the site longitude and meridian convergence. A datum shift alone is not a coordinate conversion.
- Establish two new stable marks off the corridor and carry control for detail with a closed total station traverse between them. Use RTK for detail only, with independent check shots onto control every 2 km and at each end of the route.
- Confirm which geoid model is in use before quoting any level, and never mix ellipsoidal heights with orthometric heights in the same deliverable.
Only after the transformation residuals and check shots are acceptable does the route detail get computed.
3. What must appear in the delivered report and coordinate file, and how do you handle the project manager's instruction?
Read the worked answer
The report must state the datum and realisation, the coordinate epoch, the projection with the scale factor and convergence applied, the transformation parameters and their residuals, the control hierarchy with each monument's condition, and the independent check results including the 0.35 m and 1.12 m pillar differences. Accuracy claims must be supported by those checks, not asserted. Record the processing software, version and settings, and the observation log.
On the manager's instruction: averaging repeated fixes improves the internal estimate and does nothing about the external disagreement. The scatter and the pillar differences are exactly what later as-built and boundary work will rest on, so issuing them as final control is the one option that is closed.
Practical response: issue a written note offering the coordinates as provisional relative positions in a stated datum, clearly labelled, with a re-issue date after control is resolved; deliver the detail they need for mobilisation on that basis. If pressure continues, escalate in writing to the registered surveyor in charge, because the seal and the liability sit with them, not with the averaging.