GIS & Geospatial Intelligence
GIS and utility mapping: from survey to asset intelligence
- Discipline
- GIS & Geospatial Intelligence
- Markets
- Building & Infrastructure · Business Services · Cities & Government · Environment · Industry · Resources & Waste · Transportation · Water & Utilities
Overview
An asset map becomes operationally useful when location is connected to identity, condition and ownership. Before surveying, define the accuracy requirement, coordinate reference system, required attributes and evidence needed to distinguish observed assets from inferred routes.
Plan collection and validation together. Capture the survey method, date, positional confidence and source evidence for each record. Use consistent asset IDs and controlled attribute lists. Resolve topology issues such as disconnected lines, duplicate nodes and ambiguous intersections before relying on network analysis.
Publish a clear update process for field corrections and newly installed assets. Preserve the previous revision and review changes before they affect operational decisions. Restrict sensitive infrastructure information according to the project access policy. A attractive map should never conceal unknown locations or uncertain connectivity.
For a connected utility network, plan validation of both the geometry and the engineering relationships. Two features that appear to touch on a map may not be connected in the stored network. Conversely, a geometric intersection may represent assets that cross at different elevations without a physical connection. Capture the evidence needed to distinguish these cases and include unresolved relationships in the engineering review.
Define a small set of data-quality checks before collection begins: mandatory fields, valid units, permitted values, identifier uniqueness and location confidence. Run those checks during field work so the team can correct missing evidence while access is still available. Keep the original observations and the reviewed interpretation separate. Include approximate or inferred features in the map with a clear confidence attribute.
A handover should include the dataset, its data dictionary, coordinate information, validation report and maintenance procedure. OGC publishes geospatial interoperability standards; select formats and interfaces against the project exchange requirement rather than choosing a format only because one tool exports it. The receiving team should be able to identify the authoritative dataset and explain how subsequent corrections become accepted updates.
Further reading
Key considerations
- Define the operating question and asset boundary.
- Record input quality, units, ownership and revision.
- Agree review responsibilities and acceptance criteria.
- Verify project-specific requirements before implementation.
Related solutions
Product capabilities
- Define the operating question and asset boundary.
- Record input quality, units, ownership and revision.
- Agree review responsibilities and acceptance criteria.
- Verify project-specific requirements before implementation.
