Mapping water network assets with GNSS and reliable field records
Build a water asset inventory that links visible features, operational identifiers, photographs and documented positioning methods.
Agree the water asset inventory scope
Start by listing the water network objects to be captured and the decisions the inventory will support. Valves, hydrants, meters, chambers and service markers may require different attributes and observation points. Agree whether the project is creating a first inventory, checking existing records or documenting construction. These purposes lead to different reconciliation and approval workflows.
Define the asset owner’s identifier convention before collecting points. Keep operational identifiers separate from survey point numbers, because one asset may have several observations over time. Include fields that allow an asset to remain unidentified pending review. Forcing the crew to select an existing record without adequate evidence can create a convincing map of the wrong network objects.
Continue learning CORS and network RTK: understanding the reference service
Define exactly what the coordinate represents
A visible cover can be offset from the valve or chamber below it. Record the physical target observed by the surveyor and distinguish it from the asset interpretation. If the asset owner requires a derived position, document the evidence and method used to derive it. Do not assume that the geometric centre of every cover represents the underground component of interest.
GNSS positions do not establish pipe depth or buried alignment by themselves. Treat measurements from inspection, locating instruments or construction records as separate evidence. Record whether a depth is to the top of a pipe, its centreline, an invert or another specified reference. Without that definition, an apparently complete numeric field can be misleading during maintenance or design.
Continue learning GNSS utility asset mapping: position, identity and evidence
Prepare forms that work at the asset
Use a field form with clear labels, units and controlled lists for common values. Include an unknown option with a reason rather than requiring speculative answers. Required fields should be limited to information the crew can reasonably establish. Test the form with several real asset types before full deployment, including an inaccessible chamber and an asset with a missing label.
Plan for offline capture where cellular service is unreliable. Preserve unique identifiers, photographs and observation times until synchronisation is complete. Define how conflicts will be resolved if two crews visit the same asset. A reliable form workflow should protect the connection between geometry and attributes even when the network connection disappears halfway through a field session.
Continue learning GNSS mapping for disaster assessment: rapid data with traceable quality
Choose positioning methods for constrained locations
Water assets may lie beside buildings, beneath tree cover or inside compounds. Inspect the sky view and surrounding reflective surfaces before accepting a GNSS observation. Consider receiver quality indicators together with repeat checks and project requirements. A fixed solution label alone cannot prove that every local reflection, antenna setup mistake or reference mismatch has been removed.
Use a documented offset or alternative survey method where direct GNSS observation is unsuitable. Record the offset reference, direction, distance and measurement method. Keep the original measured point as part of the observation evidence. This allows the office reviewer to understand how the asset position was obtained instead of seeing only a final coordinate with no explanation of its derivation.
Continue learning Recording drainage assets with GNSS and clear field evidence
Capture operational context without guessing
Photograph the asset label, overall surroundings and relevant visible details. Record access restrictions, cover condition and whether the object was opened or only observed externally. Do not infer valve status, pipe material or connection direction from appearance alone when the project requires verified operational information. Refer unresolved questions to the asset owner through the agreed review process.
Link photographs and notes to the asset identifier and observation record. A general folder of unlabelled images becomes difficult to reconcile after hundreds of assets have been visited. Include enough surrounding context to distinguish nearby covers. Where a label conflicts with the existing database, preserve both values and flag the discrepancy rather than silently choosing whichever seems more plausible.
Continue learning CORS and network RTK: understanding the reference service
Check both spatial and network consistency
Observe suitable control checks and repeat selected asset positions according to the survey plan. Compare the results against agreed positional criteria. Then review the data as a network inventory: look for duplicate identifiers, improbable feature locations and inconsistent attribute combinations. These checks test different problems and should not be collapsed into a single quality flag.
Network geometry from records may not align with newly surveyed surface assets. Investigate whether the discrepancy reflects an approximate record map, a reference mismatch or an incorrect asset match. Do not shift surveyed assets to make the map look tidy without evidence. Keep measured positions, record-derived lines and any approved interpretation distinguishable in the delivered dataset.
Continue learning GNSS utility asset mapping: position, identity and evidence
Validate the receiving system and handover format
Export a sample early and load it into the water utility’s intended system. Confirm that long identifiers, leading zeros, dates, coded values and photograph links survive. Check whether the receiving system expects two-dimensional points or a defined elevation field. A third coordinate without a stated height reference should not be treated as a usable engineering elevation.
Provide a data dictionary and provenance fields with the final dataset. Explain the coordinate reference, observation methods, quality assessment and unresolved assets. Include a list of records requiring owner review. The delivery should support maintenance decisions while making clear which information was directly observed, derived from another measurement or carried forward from an existing record.
Continue learning GNSS mapping for disaster assessment: rapid data with traceable quality
Support updates after the first survey
Establish a revisit process that adds a new observation to the asset history. Record replacement, removal or relocation through the asset owner’s approved lifecycle rules. Avoid creating a duplicate asset every time a new coordinate is collected. Compare new and previous positions with attention to their methods and reference systems before interpreting a difference as physical movement.
Keep the original survey evidence available for later disputes or maintenance planning. A water network inventory becomes more valuable when future crews can understand why a position or attribute was accepted. GNSS contributes the spatial foundation, but the durable result comes from linking that position to the correct object, a clear observation record and a maintained asset management process.
Continue learning Recording drainage assets with GNSS and clear field evidence
Document an inaccessible valve chamber
A crew may reach a mapped chamber but be unable to open it under the project’s access arrangements. Record the visible cover position, identifier, condition and the fact that the interior was not inspected. Do not populate underground valve position, pipe depth or operating status from assumption. Existing records can be linked as another source, with their date and provenance kept separate from the new surface observation.
Create a follow-up issue if the missing information is required for the inventory. The asset owner can then arrange an authorised inspection or another suitable investigation. When that evidence arrives, add it to the same asset history and retain the earlier observation. This workflow produces a useful partial record immediately while preventing later users from mistaking unverified underground attributes for measurements made during the GNSS visit.
Continue learning CORS and network RTK: understanding the reference service
Practical checklist
- Separate visible cover positions from underground interpretations.
- Preserve stable asset identifiers and linked photographs.
- Test an export in the water utility’s receiving system.
Plan your GNSS setup
Compare the EQ10 and EQ20 receiver specifications, then discuss the configuration and support your project needs.
Compare GNSS receivers
