Underground utility networks are among the most complex spatial datasets an organization can manage. Gas pipelines, water mains, electricity cables, and telecom ducts all share the same subsurface space, yet each follows its own logic, flow direction, and set of operational rules. Modeling routing for these networks underpins everything from maintenance planning to excavation safety, and getting it right starts with understanding what routing actually means in this context.
Whether you work for a water utility, a distribution network operator, or a government agency responsible for public infrastructure, the questions below will walk you through the core concepts, data requirements, and practical approaches behind underground network routing. We have structured this as a direct question-and-answer guide so you can jump straight to what matters most for your situation.
What is routing in underground utility network modeling? #
Routing in underground utility network modeling is the process of defining and representing how flow, signals, or connectivity move through a network of pipes, cables, or ducts buried beneath the surface. It establishes the logical and spatial paths between network components—from source points to end users—so that analysis tools can trace, simulate, and query the network accurately.
In practical terms, routing tells your system which direction water flows through a pipe, how an electrical fault propagates through a cable segment, or which customers are affected when a valve is closed. Without routing, you have a collection of geometric lines on a map. With routing, you have a functional model of a living infrastructure network.
Routing is distinct from simply drawing network geometry. A pipe drawn on a map has a shape and a location, but routing adds directionality, connectivity rules, and relationship logic. This is what makes it possible to run meaningful spatial analysis on the network rather than merely visualize it.
Why does accurate network topology matter for utilities? #
Accurate network topology matters because it determines whether your spatial model reflects how the network actually behaves. Topology defines the connectivity between network elements: which pipes connect to which junctions, which cables feed which substations, and which segments belong to the same logical circuit. Without correct topology, routing analysis produces unreliable results.
Consider a water utility trying to identify which customers lose supply when a specific valve is closed. If the topology contains errors—such as disconnected segments or incorrect node connections—the tracing algorithm will either miss affected customers or flag customers who are not actually impacted. This kind of error has real operational consequences, from incorrect outage notifications to flawed repair prioritization.
Topology errors and their downstream effects #
Common topology errors in underground network models include dangling lines that do not connect to anything, duplicate geometries, incorrect flow-direction assignments, and missing junction nodes at pipe intersections. Each of these breaks the logical chain that routing depends on. The farther downstream an analysis runs from the error, the more distorted the results become.
For utilities managing thousands of kilometers of buried infrastructure, maintaining clean topology is an ongoing data-quality task, not a one-time fix. Automated topology validation tools play a useful role here, flagging inconsistencies before they affect operational decisions.
What are the main approaches to modeling underground network routing? #
The three main approaches to modeling underground network routing are geometric modeling, topological network modeling, and hydraulic or load-flow modeling. Each serves a different purpose and requires a different level of data detail. Most utilities use a combination of all three, depending on the use case.
- Geometric modeling focuses on the spatial representation of network assets, capturing the physical location, shape, and dimensions of pipes, cables, and ducts. It is the starting point for any network model but does not, by itself, support routing analysis.
- Topological network modeling adds connectivity rules, directionality, and node-edge relationships to the geometry. This is what enables tracing, pathfinding, and impact analysis. It is the layer most relevant to routing.
- Hydraulic or load-flow modeling goes further by simulating actual flow behavior, pressures, voltages, and capacities within the network. This approach requires detailed engineering parameters and is typically used for operational planning and network design.
For most asset-management and operational workflows, topological network modeling provides the right balance of detail and practicality. Hydraulic modeling is valuable for specific engineering analyses but demands significantly more data preparation and computational resources.
How does network tracing work in a geospatial data system? #
Network tracing in a geospatial data system works by traversing the connected edges and nodes of a topological network model, starting from a defined point and following connectivity rules until a stopping condition is met. The result is a set of network elements—such as pipes or cables—that are logically connected to the starting point in a specific direction or under specific conditions.
A typical tracing operation might start at a pump station and follow all downstream pipes until it reaches either end-of-network points or a set of closed valves. The system uses the network’s topology to determine which segments are reachable and in what order. This is how utilities answer questions like “Which customers are downstream of this fault?” or “What is the shortest path between these two network nodes?”
Upstream and downstream tracing #
Tracing can run in two directions. Upstream tracing follows the network back toward the source, which is useful for identifying which supply points feed a given location. Downstream tracing follows the network away from the source, which is useful for impact analysis and customer notification. Many geospatial platforms support both modes and allow you to apply additional filters, such as stopping at specific asset types or valve states.
Trace isolation and barrier logic #
Barrier logic lets you define stopping conditions for a trace. A closed valve, a pressure-reducing station, or a network boundary can all act as barriers that halt the trace at that point. This makes tracing highly flexible for operational scenarios, allowing you to model real-world switching states and network configurations rather than always tracing the full theoretical network.
What data is needed to model routing for underground networks? #
To model routing for underground networks, you need accurate geometric data for all network assets, complete connectivity information between those assets, attribute data describing asset properties, and directionality or flow information where relevant. The quality of your routing model depends directly on the completeness and accuracy of these four data categories.
- Geometric data: The spatial location, depth, and extent of pipes, cables, ducts, and associated equipment such as valves, joints, and meters.
- Connectivity data: Information about which assets connect to which, including node positions at junctions, branches, and endpoints.
- Asset attributes: Material type, diameter, installation date, operational status, and capacity, all of which influence how the asset behaves in the model.
- Directionality data: For networks where flow direction matters, such as gravity-fed water systems or one-way gas distribution lines, you need to record or derive the direction of flow for each segment.
In practice, many utilities find that their data is incomplete or inconsistent across these categories. Legacy records may exist only on paper, field installations may not match design drawings, and different systems may use different identifiers for the same asset. Data integration and quality management are therefore just as important as the modeling process itself. Tools that support native data access and allow you to build relationships between multiple data sources help bridge these gaps without requiring a full data migration.
What tools and standards are used for underground utility routing? #
Underground utility routing relies on a combination of GIS platforms, network analysis tools, data-exchange standards, and industry-specific frameworks. Widely used standards include IMKL in the Netherlands for cable and pipeline information, CIM for electrical network modeling, and WaterML or EPANET formats for water network data. These standards define how network data is structured and exchanged between systems.
On the software side, GIS platforms with built-in network analysis capabilities form the core of most utility routing workflows. These platforms handle the topological modeling, tracing functions, and spatial analysis that routing depends on. In the Netherlands specifically, the KLIC framework governs how underground network information is shared between network operators and excavation contractors before any ground is broken, making it a practical standard for day-to-day routing and excavation-safety workflows.
Integration with field and enterprise systems #
Routing models do not exist in isolation. They need to connect with work order management systems, SCADA platforms, customer databases, and field inspection tools. This integration is what turns a routing model into an operational asset rather than a standalone analysis tool. Modern geospatial platforms support this through APIs, data connectors, and software development kits that allow routing data to flow into and out of the systems your teams already use.
At Spatial Eye, our spatial analysis capabilities are built specifically for this kind of connected infrastructure environment. We support routing, topology, and network tracing as core functions within our platform, and we design our solutions to integrate with the data sources and workflows that utilities and network operators already rely on. If you would like to see how this works in practice for your network, we would be happy to walk you through it.
