How Utility Data Becomes GIS Layers

Utility data becomes useful when it is structured, repeatable, and tied to a coordinate system. Turning field observations into GIS layers helps municipalities, engineers, and asset managers make better decisions over time. Without that structure, data stays trapped in notebooks, PDFs, and individual memory, none of which scale.

Why GIS Matters for Utility Management

GIS is not just a mapping tool. For utility owners and infrastructure managers, it is the backbone of asset lifecycle management. When utility features live in a GIS, they become queryable, analyzable, and shareable across departments and stakeholders.

Accurate GIS records support decisions across the entire asset lifecycle:

• Planning and design: Engineers can see what exists before they draw new alignments, reducing conflicts and redesign
• Emergency response: When a main breaks or a cable is hit, dispatchers need to know what is nearby, where shutoffs are, and what else is in the corridor
• Capital improvement: Rehab and replacement programs prioritize based on age, material, and condition data stored in GIS
• Regulatory compliance: Many municipalities and PUC reporting requirements are easier to meet when asset data is centralized and current

The alternative (relying on institutional knowledge and paper maps) works until someone retires, a record gets lost, or a crew hits something nobody knew was there. GIS eliminates that single point of failure. When combined with design-phase utility investigation, GIS data becomes a living reference that improves with every project.

CAD vs. GIS: Understanding the Difference

CAD drawings and GIS layers are not the same thing, and confusing them causes problems. CAD files (DWG, DXF) are design documents. They show geometry, but they are not spatially referenced by default and they do not carry structured attribute data the way GIS does.

A CAD line representing a water main might show size and material in a label, but that information is not queryable. In a GIS, that same line carries a structured attribute table: pipe diameter, material, install date, owner, confidence level, and anything else the schema requires. You can filter, analyze, and report on it.

Many organizations receive CAD deliverables from engineering firms and then struggle to incorporate them into their GIS. The conversion is not automatic. It requires cleanup, attribute mapping, and spatial registration. Starting with GIS-native field capture avoids that translation step entirely.

Field Capture

Field capture typically starts with identifying features and documenting what is actually present: utility paths, access points, appurtenances, and any visible attributes. This includes opening manholes, valve boxes, and handholes to record what is physically observable rather than relying on record drawings that may be decades old.

For sewer infrastructure, field capture often includes manhole invert documentation: rim-to-invert depths, pipe sizes, materials, and flow directions. These measurements feed directly into GIS feature attributes and give hydraulic modelers the data they need without requiring a separate field visit.

GNSS Positioning

Using GNSS-enabled workflows (such as Trimble Catalyst DA2), feature locations can be captured in the field and tied to real-world coordinates. Accuracy depends on environment, workflow, and collection standards.

For most utility GIS work in Colorado, sub-meter accuracy is sufficient for asset management purposes. Survey-grade positioning (centimeter-level) is typically reserved for engineering design or regulatory submissions. Understanding the difference matters because over-specifying accuracy drives up cost without improving outcomes, while under-specifying it creates records that cannot be trusted.

Coordinate Reference Systems in Colorado

Getting the coordinate reference system (CRS) right is foundational. In Colorado, most utility GIS work uses one of three common systems:

• Colorado State Plane (North or Central): The most common CRS for municipal and utility GIS in Colorado. Uses NAD83 datum. Northern Colorado utilities typically use the North zone; the Front Range and metro Denver area fall in the Central zone.
• WGS 84 (EPSG:4326): The global standard used by GPS devices and web maps. Data is often collected in WGS 84 and then projected into State Plane for delivery.
• UTM Zone 13N: Sometimes used for larger-scale or federal projects in Colorado.

Delivering data in the wrong CRS means features will appear shifted, sometimes by hundreds of feet. Before any field capture begins, confirm the client's CRS requirements and verify that your collection workflow matches. This is one of the most common and most preventable errors in GIS data delivery.

Attributes & Structure

GIS value comes from attributes, not just lines on a map. Common attributes include:

• Utility type (water, electric, fiber, sewer, etc.)
• Material (when known/visible)
• Diameter/size (when known/visible)
• Depth notes (when verified)
• Confidence/verification notes
• Install date or approximate era (when available)
• Owner or responsible entity
• Collection date and method

The schema, meaning which attributes you collect and how they are structured, should align with the client's existing GIS data model. Delivering data that does not match their schema creates manual rework. Ask for their feature class definitions before you go to the field.

Data Cleaning and QC Before Delivery

Raw field data is never ready for delivery without review. Between collection and handoff, data goes through a cleaning and QC process:

• Removing duplicate or erroneous points
• Verifying attribute completeness (no blank required fields)
• Checking topology (lines snap to points, no dangles or overlaps)
• Validating coordinates against known reference points
• Reviewing photos and notes for consistency with geometry
• Projecting data into the client's CRS if different from collection CRS

This step is where most of the value is added. Anyone can collect a point. Delivering a clean, structured, schema-compliant dataset that integrates without friction is what separates useful data from noise.

Integration with ESRI and ArcGIS Systems

Most Colorado municipalities and utility owners run their GIS on ESRI's ArcGIS platform, whether that is ArcGIS Pro, ArcGIS Online, or Portal. Deliverables need to be compatible with these systems.

Common delivery formats include:

• File geodatabases (.gdb) for bulk delivery
• Shapefiles for simpler datasets or legacy systems
• Hosted feature layers for ArcGIS Online or Portal
• CSV or GeoJSON for lightweight integrations

For organizations using ArcGIS Online or Portal with Collector/Field Maps, field data can sometimes be captured directly into hosted feature services, eliminating the export-import cycle entirely. This approach works well for ongoing programs where the same features are being inventoried repeatedly.

Deliverables That Actually Help

A good deliverable is one that can be used again. Depending on scope, that may include:

• Feature layers (hosted or file-based)
• Shapefiles / geodatabases
• Maps or exhibits for project files
• Photo documentation linked to features
• Attribute summary reports for stakeholder review

Long-Term Value of Building Accurate Records

Every project is an opportunity to improve the overall record. When utility data is collected once and stored properly, it compounds in value. The second project in the same corridor benefits from the first. Emergency responders benefit from both. Capital planning benefits from the full history.

Organizations that treat GIS as an ongoing investment rather than a one-time project cost end up with a system that genuinely reduces risk and improves decision-making. The ones that treat it as a checkbox end up collecting the same data repeatedly because nobody can find or trust what was collected before.

The goal is long-term clarity: fewer unknowns, fewer repeats, and a system that becomes more accurate over time instead of resetting with every project. That starts with capturing the right data, structuring it correctly, and delivering it in a format that integrates without friction.