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; } } }

Electric Utility Network - Terminal Connections failed

VickyWang

Create and apply an Electric Utility Network asset package.

Trace a subnetwork from start (circuit breaker) to end (transformer) successfully (there are few distintrubition lines and transformers are in the subnetwork).

Used the Network Topology 'Validate' successful.

Move a transformer of the subnetwork; the lines do not move along with the transformer's movement.

Then, use the Terminal Connections tool of Network Topology that shows "Device must be connected to the line."

The Edge-Junction rule that allows the distribution line and transformer are connected with their asset group and asset type.

The line has populated from/to device (transformer).
The subnetwork controller name is Unknow for both line and transformer. Their 'Is Connected' status is 'True'.

1) What will be wrong in the setting? possible wrong attribute setting or value missing?

2) I assume the line will go with the point to have rubberband behavior when the point and line are connected. But it doesn't. What will be the possible fault?

Thanks

#Electric Utility Network

#EUNM

#connectivity

Find more posts tagged with

Accepted answers

VickyWang

Try to re-publish the feature services that are used by the Utility Network project.

My case is that the feature services was republished but use the different name (hence, different rest endpoint).

It has the above issue when using the old ArcGIS pro project but updates the source to new feature services.

Try to create a new ArcGIS project and grab the new feature services seems behavior the same as what it should be.

All comments

VickyWang

Thanks, Melissa, the above issue is solved.

We've also found some transformer or devices does not have connectivities with distribution lines due to the coordinates of points and lines that are not actually connected. The data were imported from other systems and also re-projected to different projections. Which causes there are some tolerance between point and line. Aim to use gen un GP process with tolerance can connect them back again.

MelissaJarman

Thanks Vicky for coming back and posting more info for how you resolved this. Please comment if you think there are more follow-ups needed.

VickyWang

Try to re-publish the feature services that are used by the Utility Network project.

My case is that the feature services was republished but use the different name (hence, different rest endpoint).

It has the above issue when using the old ArcGIS pro project but updates the source to new feature services.

Try to create a new ArcGIS project and grab the new feature services seems behavior the same as what it should be.

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.