nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

10: Invalid connectivity - Sewer laterals can't connect to mains via tap

TanyaWright1

Hello,

I am setting up a sewer utility network using the essentials foundation and adding attributes onto the data model. When I got to the enable topology stage all of my sewer laterals and sewer mains are shown as errors when they are connected by a tap. They do not have an error if connected by a different asset type like a coupling or if connected by a manhole (sewer device). The junction- edge rule for taps look to be the same as for couplings so I don't understand why it is giving an error. I tried adding a edge-junction-edge rule but that did not get rid of the error. The sewer mains also allow for any vertex connectivity. Any ideas of what I am missing?

Thank you for your help!

Find more posts tagged with

Accepted answers

GIS_kiwi4

Could you check the Z values of the Taps that were migrated?
If the Z values aren't the same as the lines then they are not connected even if they are coincident.

All comments

GIS_kiwi4

@TanyaWright1 - The first thing to check would be the connectivity rules but you've confirmed the rules exist.

Another thing to check would be if the terminal configuration (if any) is correctly used when connecting the two lines.
Could you describe what the error on the dirty area is?
That might give us a way forward.

TanyaWright1

Hello, here is a snapshot of the error from the dirty area.

To add an update: I removed an existing tap and added a new tap and the dirty area went away. So it is recognizing the connectivity of new taps, but not the data I migrated over (which is geometrically correct). Any ideas why that could be or how to fix it?

GIS_kiwi4

@TaN - Did you use the append tool to migrate the data?
The append tool doesn't trigger an "edit" for the UN to make the connections.
https://community.esri.com/t5/arcgis-utility-network-questions/load-data-into-existing-un/m-p/1563577#M4610

TanyaWright1

I used the "Load Data Using Workspace" tool for migrating all of the data. (using this workflow: https://doc.arcgis.com/en/arcgis-solutions/latest/reference/migrate-data.htm)

I just tried adding a new tap between an existing lateral and main and it did not create an error. I then moved an existing tap off the lines and then snapped it back onto the lateral end point where it joins the main and it created the error. So any new taps I create it is ok with but my existing tap data it doesn't like. The only difference I can see in attribution is the assetid and rotation are populated in my existing data.

GIS_kiwi4

Could you check the Z values of the Taps that were migrated?
If the Z values aren't the same as the lines then they are not connected even if they are coincident.

RobertKrisher

@gis_KIWI4 I would specifically say that they are coincident on the x/y plane, but because the utility network is 3d they won't be connected unless the tap/main/service all have the same x/y/z coordinate.

GIS_kiwi4

@TanyaWright1 - were you able to find the root cause?

TanyaWright1

@gis_KIWI4 @RobertKrisher

Thank you both for your help!

Yes, the Z value was different between the taps and the sewer mains. I ran the Update Feature Z geoprocessing tool and that removed my topology errors.

Thank you for your time in helping me resolve this! I really appreciate it!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.