Skip to content

Tracing and cleaning a network

A network that draws correctly can still be connected wrongly. Pipes pointing uphill, a branch joined to nothing, a manhole that drains nowhere - none of these look wrong in plan, and all of them change the answer. Tracing is how you check connectivity rather than appearance.

Choose Trace network ▸ Trace upstream or Trace downstream, then click a node. The connected sub-network highlights, following the direction each link actually flows: from its from-node to its to-node.

Two questions this answers immediately:

“What drains through here?” Trace upstream from an outfall or a pinch point. Anything that does not highlight is not reaching it, which is either a genuine separate catchment or a connectivity error.

“Where does this go?” Trace downstream from a new connection or an inflow point and watch where it ends up. If it does not reach an outfall, it does not leave the model.

Trace network ▸ Find orphans / quality issues scans the whole network and reports what it finds. Each is worth a different reaction:

FindingWhat it usually means
IsolatedAn element connected to nothing. Almost always an import artefact
DanglingA link whose from-node or to-node does not exist
Dead endFlow arrives at a node and nothing leaves it
No drain to outfallFlow enters and never leaves. A missing link, or a genuinely closed system
Adverse slopeThe pipe runs uphill with no pump feeding it. Usually bad invert data or a pipe drawn backwards
Rising mainA pipe rising downstream of a pump. Listed separately because it rises by design
Bad outletA subcatchment discharging to something that is not there
Over-deep junctionA node far deeper than its neighbours. Often a units or datum error
Steep / flatSlopes outside the usual range. Worth a look, not necessarily wrong
LoopA circular path. Legitimate in a looped system, suspicious in a branched one

After a GIS import or a generated model, run the checks first and work down the list. Fixing connectivity before you touch hydraulics saves re-running everything twice, because a connectivity error changes every number downstream of it.

The reverse-direction fix is the common one: a conduit drawn from the wrong end shows as an adverse slope, and swapping its from-node and to-node corrects both the direction and the slope in one edit. Check the profile afterwards - see profile and HGL

  • because a genuinely mis-levelled invert looks the same in the list but does not go away when you reverse it.