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

Migrating Pole–Conductor Relationships to Structural Associations

LyudmilaBoyadzhieva

Hi there,

I’m planning to migrate my many-to-many relationship table between poles and conductors into structural attachment associations. Currently, the client can list all conductors attached to a selected pole, or all poles along a given conductor. I’m trying to understand how the client will continue to retrieve this same information once the data is represented using associations.

Thanks in advance!

source db.png

SubaKrishnan_6-1742921822522.png

タグ付きの投稿をもっと見る

Accepted answers

RobertKrisher

Structural attachments are used to associate the connectivity of the domain network with the structure that support that network, which is a different requirement than what the customer has. The Feature restrictions page of the ArcGIS Help shows that you cannot directly attach a Line to a Junction. Any feature can only have a single attachment, so even if you could attach a line to a pole the M:N cardinality would be a problem.

If you want to model these as structural attachments, you'll need to attach a device or junction to the pole that is connected to the line. This overcomes both the restrictions (structure/line and M:N), but requires using select by location to show which poles/conductors are related.

You could also bring over the relationship class.

JohnAlsup

In the Utility Network, if you enable "Include Structures" on the subnetwork definition, then when update subnetwork is run, the subnetwork name field will be populated with all the subnetwork names that this structure is associated with. The only other thing you would need to do is create a junction feature on the line and then create a Structural Attachment association between each junction and the pole. This would be a way to obtain the same information as your previous relationship class using standard utility capabilities.

All comments

JohnAlsup

In the Utility Network, using the Electric Foundation as a model, you would place a ElectricJunction feature, probably a MV Attachment Point on the line where each pole is located. Then create an attachment association between the ElectricJunction you created and the StructureJunction Pole feature. Then when you select your pole, you will see everything it is attached to, even if multiple circuits. If you want each wire associated to the pole, then you would need to create an Electric Junction feature placed on each wire.

RobertKrisher

You could also bring over the relationship class.

LyudmilaBoyadzhieva

Thank you for the quick reply. I understand the feature restrictions.

I've attached a new example featuring a pole with a structural attachment (a connection point). The attribute pane correctly shows their relationship: the pole has one structural attachment, and the connection point is attached to the pole.

However, the conductors connected to this connection point are not visible. It appears we would need to migrate the relationship class and keep this information outside the Utility Network.

image.png

JohnAlsup

Can I ask what the business purpose of this is? If it is for a user to see what conductors are mounted on a pole? Is it for some system to calculate pole load?

LyudmilaBoyadzhieva

Hi John, sorry for the late reply. At present, they use this relation mainly for reporting — for example, to extract all poles with earthing that are on a specific conductor/line, or to determine how many circuits a pole supports and which ones. They also plan to use it for AMS in the future.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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