Update Subnetwork and Is Connected not updating

821
10
10-13-2020 02:03 PM
LindseyStone
Occasional Contributor III

I'm trying to implement a Water Utility Network and am having trouble with my taps or junctions.  We have serveral mains that have taps connected at vertex's in the span at the main.  Then a service line is connected to that tap.  If this tap is connected in the span of the main instead of the end the Is Connected tool and Update Subnetwork does not assign the service line or the tap to the system.  

I was looking at the Naperville data and it shows whole mains without the mains split at the taps for the service lines. I'm also tried splitting a line or making a line off a controllable value and it still doesn't work correctly.

I disable and re-enabled network topology hoping this would help.  I also verified under the Water Line that the Network Edge Connection Policy is set to Any Vertex on Water Mains and Service Lines

Tags (1)
0 Kudos
10 Replies
PaulLeBlanc1
Esri Contributor

If you place a starting point here and run an upstream/downstream trace, are the results what you expect? How about a connected trace?

If possible, sharing a small UN in file geodatabase would help. You can email it to me.

0 Kudos
LindseyStone
Occasional Contributor III

I did a Subnetwork trace and it sort of does it.  So it picks up the line I put the trace Location on and goes to the main and out.  However, down line it doesn't pick up any of the Not Connected Service lines.  As you can see the service line on the house on the left is at the end of main so it picked that up.  But the two on the right are in the middle of the main and they didn't get grabbed.

I can export my SDE as an asset package to a file geodatabase for you.  What is your email to send it to?

0 Kudos
VishApte
Esri Contributor

If "Update Subnetwork" or "Update Is Connected" tools does not update service tapping's "subnetworkname" or "inconnected" field, it probably means one of the following

1. Junction-Edge rule does not exist that allows the specific tapping (tapping's asset group and asset type) to connect to specific mains (Line's asset group and asset type). You can check network properties by right clicking UN topology class and find if matching record exists under Junction-Edge. If same tapping is moved to end/start vertex of the line and then   "Update Subnetwork" or "Update Is Connected" tool works, it means rule exists as Edge-Junction-Edge.

2. There is a tiny little gap between the tapping and line vertex. If you use Edit->Move command on tapping, does the line's vertex moves giving rubberband effect while you move the tapping? This will indicate if tapping is snapped.

or

3. The lifecyclestate value of the tapping at the vertex is not part of the subnetwork definition. But this should be same if you move tapping to the end of the line.

or

4. You have additional criteria for subnetwork definition that tappings at vertex doesn't satisfy. But this should be same if you move the tapping to the end of the line.

Hope this helps.

0 Kudos
MikeMillerGIS
Esri Regular Contributor

Also add

  • Working in a version.

LindseyStone
Occasional Contributor III

My original screenshot was looking at default when first enabling topology and updating the subnetwork.  If I tried to edit anything in the version, then it catches even less.  It doesn't update anything new.

0 Kudos
LindseyStone
Occasional Contributor III

1.Here is a screenshot of my Junction Edge Connectivity rules, which were all default within the UN.  I have it that allows tap to be connected to service lines of all kinds and allows taps to be connected to Water mains.

Now I did have to allow this rule for our circumstances as we have several cases that we have domestic service lines coming off a fire line at a tap.

2. If I try to move the tap then the main and the service all move with it.

3. The Life Cycle on all features are set to In Service

4. No aware of any additional definitions.  Is this the rules that I screenshot above?

0 Kudos
MikeMillerGIS
Esri Regular Contributor

We need to look at the X,Y and Z info at the vertices.  I have seen where the editor treats items as snapped, but they are not snapped in the utility network.  Editor tolerances are not the same as connectivity tolerances in the network.  When reviewing the values, you need to click in like you are editing the values of the vertices, as the UI rounds off for viewing. 

If you select the main and the fitting and run this script, you can see the vertices info.  Can you post the results?  Note: It may take a while due to an issue with subtype layers and DA cursors.  Make sure to have something selected or you will get the vertices for your entire layer.

fields = ['SHAPE@X', 'SHAPE@Y', 'SHAPE@Z']

print("***********Main***********")
fc = "Water Line\\Water Main"
with arcpy.da.SearchCursor(fc, fields, explode_to_points=True) as cursor:
    for row in cursor:
        print(row)

print("***********Fitting***********")
fc = "Water Junction\\Fitting"
with arcpy.da.SearchCursor(fc, fields, explode_to_points=True) as cursor:
    for row in cursor:
        print(row)

Here is an example output, I bolded the vertex that fitting and main share.

***********Main***********
(1030655.1770261787, 1861107.9398856163, 0.00010000000474974513)
(1030652.9670568444, 1861106.5150197, 0.00010000000474974513)
(1030649.2898988463, 1861104.1439614445, 0.00010000000474974513)
(1030588.8188911788, 1861065.1581470296, 0.00010000000474974513)
(1030579.5249465108, 1861059.1660330296, 0.00010000000474974513)
(1030525.9440169297, 1861024.6211546138, 0.00010000000474974513)
(1030513.5339367613, 1861016.6208425313, 0.00010000000474974513)
(1030496.82990193, 1861005.852163285, 0.00010000000474974513)
(1030404.9609911777, 1860950.2259621993, 0.00010000000474974513)
***********Fitting***********
(1030513.5339367613, 1861016.6208425313, 0.00010000000474974513)

0 Kudos
RandallChew
Occasional Contributor II

I am running into the same problem with another water dataset.  Pro 2.5.2, Enterprise at 10.7.1.  Testing in a file gdb the subnetwork propagates out just fine, however when rebuilding in Enterprise it keeps stopping at a fitting and moving no further.  Lifecycle status is active, disabled/enabled network topology.  Deleted and recreated the line/fitting.  Ran this snip and they share junctions.  I'm not sure what to do at this point as again, it is working just fine in a file gdb...

 

0 Kudos
SSMIC3038
Occasional Contributor II

Randall, encountering a very similar problem. did you resolve and is there any insight you could pass along?

0 Kudos