From CAD plans to an operable utility-network GIS
How to convert plans, spreadsheets and construction records into a utility-network cadastre that supports operations without inventing accuracy or connections.
Converting a CAD plan to a GIS layer does not automatically turn a drawing into an operable utility cadastre. It may preserve geometry while losing the connection between assets, construction date, material, status, source or confidence. It can also appear more positionally accurate than anyone has verified in the field.
The aim of a responsible migration is more precise: leave a network whose assets, relationships and evidence can answer an operational question without concealing what still needs confirmation. That discipline applies to water, sewer, gas and comparable infrastructure.
GeoSAT's utility-network cadastre service can structure that process. For the complete operating model, read how to structure a utility network cadastre and use the local GeoJSON topology checklist as an initial review, not a certification.
Treat drawings as evidence, not a single truth
A DWG file can contain useful layers, local symbols, labels, dimensions, repeated blocks and lines without asset meaning. It may represent a design, as-built work, a partial update or an undated copy. Before conversion, create an inventory for each source:
- Name, date, owner, declared coordinate system and covered territory.
- Evidence type: design, as-built, survey, operations, maintenance report or unvalidated reference.
- Layers, blocks, text and attributes that may represent assets or relationships.
- Gaps, duplicates, conflicts between sources and use restrictions.
Keep the original file and link it to its derived GIS version. Deleting the drawing to “clean” the database removes a useful part of the audit trail.
Design the model before mass digitisation
Do not use one line class for every part of the network. Separate the objects that operations need to query and maintain. An initial model can include:
| Object | Decisions it should document |
|---|---|
| Linear segments | Network type, material, diameter, status, flow direction where applicable, date and source. |
| Point assets | Valves, hydrants, chambers, manholes, connections, stations or other elements for the service. |
| Relationships | Which segment connects to which asset, continuity, hierarchy and known or pending condition. |
| Evidence | Plan, record, photograph, survey, work order or inspection that supports each datum. |
| Quality status | Confirmed, digitised from source, inferred, queried or awaiting fieldwork. |
Mandatory attributes and controlled values should come from the utility's actual work and the applicable technical framework, not inherited layer names. For drinking water and basic sanitation, Colombia's Resolution 0330 of 2017 adopts RAS; confirm with the responsible organisation which provisions, manuals and contractual specifications apply to the particular scope.
Convert in reviewable stages
- Inventory and prioritisation. Identify sources, coverage and risk. Begin with areas or assets where information enables frequent decisions, not with the number of files available.
- Semantic matching. Relate every CAD layer, block and label to an object, attribute or rule in the model. Where no reliable match exists, mark it as pending; do not invent equivalence.
- Spatial alignment. Declare each source's reference, the control or transformations used and the method applied. If reference is uncertain, the output must state unknown or limited spatial quality.
- Topology and relationships. Review disconnected endpoints, duplicates, overlaps, crossings that should connect, connections that should be separate, and point assets outside their associated segment.
- Field sampling and acceptance. Check a representative set of assets and critical areas. Record findings, corrections, exclusions and remaining confidence by area.
Fieldwork does more than correct geometries. It can confirm whether an asset still exists, is operational, belongs to a different network, or whether a drawn relationship was a plan simplification.
Control semantics, position and connectivity separately
A network can pass visual review and still fail in operation. Use separate checks:
- Semantics: unique identifier, required attribute, unit, controlled value and permitted status.
- Position: declared reference system, coordinate source, date and accuracy evidence where available.
- Connectivity: rules for nodes, endpoints, intersections, discontinuities and relationships between line and point assets.
- Time and source: who reported each datum, when, where it came from and which version superseded it.
Not every error has the same urgency. A valve without a material value may be an inventory observation; a segment that appears to connect hydraulically isolated sectors can change a maintenance decision. Define severity and a correction route before converting thousands of features.
Procure defensible outcomes, not apparent completeness
A strong scope distinguishes what is delivered as confirmed, digitised from a document, inferred and awaiting verification. It also requires visible source and cutoff date, delivery of the data dictionary, and documented export of data and evidence.
Do not request survey-grade positional accuracy when only reference cartography exists. If positioning is needed for construction, design or a decision with a defined tolerance, procure the survey and control as a testable activity. The IGAC publishes Colombia's National Geodetic Network and the MAGNA-SIRGAS framework, which help document fieldwork reference; the exact method belongs in the specification.
Next step
Choose a pilot zone where plans, operations knowledge and field verification are available. Convert the sources, run controls, review the model with people who maintain the network and measure which questions the database can now answer. Then scale using the corrected rules and evidence.
GeoSAT can prepare the inventory, data model, conversion plan and acceptance tests. The result should not promise every CAD line is accurate; it should reveal what is known, what is confirmed and how the network will be maintained after migration.