Locating and fixing parallel pipes

Any referenced datasets can be downloaded from "Module downloads" in the module overview.

Step-by-step:

Depending on your model, you may have pipes that legitimately run in parallel between nodes in your water distribution system. But sometimes, parallel pipes can occur as a result of duplication, so it is important to review these areas.

Parallel pipes are identified as pipes sharing the same start and end nodes and are not required to share identical vertices. You can use the Locate/Fix Parallel Pipes tool to review these locations and fix any errors.

  1. Open the appropriate .aprx file in ArcGIS Pro.
  2. From the ribbon, InfoWater Pro tab, click Initialize.
    The InfoWater Pro tab of the ribbon with Initialize called out as being selected
  3. From the Model Explorer, Command Center tab, expand Utilities > Locate Parallel Pipes.
  4. Double-click Show as Domain.
    The Model Explorer, Command Center tab, Network Review/Fix and Locate Parallel Pipes folders open, with Show as Domain highlighted

Two parallel pipes are found in this example and displayed in the Message Board.

The Message Board reporting the results of the Locate Parallel Pipes operation and the number of parallel pipes that were found

  1. To zoom in on the location, on the InfoWater Pro ribbon, Domain panel, select the Zoom to Domain tool.
    The InfoWater Pro ribbon, Domain panel, with the Zoom to Domain tool highlighted
  2. Examine the network configuration.
    The Network map displaying the parallel pipes highlighted in red

Notice that one pipe is highlighted in red. To correct this, re-draw the pipe with false vertices so you can see the parallel pipes.

  1. Turn on the labels to see the node IDs. From the Contents panel, right-click Junction and select Label.
    The Contents panel with Junction > Label highlighted
  2. On the InfoWater Pro ribbon, Edit panel, expand the Edit drop-down and select Redraw Pipe.
    The InfoWater Pro ribbon, Edit panel with Edit > Redraw Pipe tool highlighted
  3. Select the pipe to be redrawn; you can see that it flashes blue, signifying that it is selected to be redrawn.

IMPORTANT: When selecting a pipe, make sure that the pipe you intend to re-draw is indeed the one that flashes. If you accidentally select another pipe, and it flashes blue, you will consequently redraw the wrong pipe. To fix this, simply re-select the correct pipe. If you do happen to redraw the wrong pipe, then there is no undoing it—you would need to draw it again or reimport it.

  1. Click the starting node.
  2. Click to add two false vertices away from the pipe.
  3. Double-click the end node to finish re-drawing the pipe.
    The network map displaying the redrawn parallel pipe with two false vertices
  4. Look at the attributes of each pipe. On the InfoWater Pro ribbon, Edit panel, click the Select tool.
  5. Select your redrawn pipe.

Notice that attributes exist in the Model Explorer for this pipe.

The Model Explorer attributes for the redrawn pipe

  1. Now select the original pipe.

This time, there is no attribute data associated with it. After investigation, it is determined that this pipe does not exist and can be deleted.

The Model Explorer attributes for the existing pipe without any associated attribute data

  1. On the InfoWater Pro ribbon, Edit panel, expand the Edit drop-down and select Delete Pipe.
  2. Select the pipe to be deleted.
  3. Click OK to confirm.
    The InfoWater Pro ribbon Edit panel, with the Edit drop-down highlighting the Delete Pipe tool

You can now redraw the pipe to remove the false vertices that you added.

  1. On the InfoWater Pro ribbon, Edit panel, expand the Edit drop-down and select Redraw Pipe.
  2. In the Network map, click the start junction.
  3. Double-click the end node.

The pipe is now straight.

The Network map showing the path of the newly redrawn pipe

  1. In the Edit panel, click Select to avoid editing other pipes.

IMPORTANT: This fix could be flagged to your GIS department to fix and re-import; however, that may not be necessary, as the one-to-one relationship between the unique IDs and features is maintained.