What are crossing pipes?

Crossing pipes is a data validation tool that finds and helps fix potential error: pipes that intersect on the map but are not connected by a junction.

Why these warnings might be a problem?

Hydraulic models, like those in epanet-js, are "node-link" systems that require a junction (node) to transfer water between pipes (links). If two pipes cross without a shared junction, the model assumes they are not connected and treats them like an overpass on a highway, leading to inaccurate simulation results.

If this is intentional (e.g., a small distribution main running over a large transfer main), it's fine.

If this is an error (e.g., two water mains are supposed to be connected at a cross-intersection), the model is topologically incorrect. This will lead to errors in the simulation, such as:

• Incorrect pressure calculations.
• Wrong flow paths.

The crossing pipes tool automatically scans the entire network geometry to find every location where two pipe lines cross, flagging them as "potential issues" for you to review.

How is it handled?

This tool will find the locations, letting you analyse the situation and decide if the crossing should have a junction or not.

The workflow goes as follow:

1. Detection: select the tool in network review, placed in the left sidebar.
2. Reporting: epanet-js will generate a list of all potential issues.
3. Navigation: when clicking an issue in the list, the application will navigate to that specific location on the map.
4. User Action: The user must then decide how to handle the issue:
   • Fix the Issue: If the pipes should be connected, the user must correct the topology. This is often done by splitting one or both pipes at the intersection and adding a new junction that connects all of them.
   • Discard the Issue: If the pipes are not supposed to be connected (a "false positive"), the user simply dismisses the warning and moves to the next item on the list.

Related articles

Orphan assets

Proximity check

Connectivity trace