ArcGIS Utility Network: Containment associations between Structure Network and Domain Network via Attributes

236
2
Jump to solution
04-22-2024 01:41 AM
HannesFoth
New Contributor

The Feature Class 'Structure Line' comprises the asset group Trassen (see green lines in the screenshot).
These should serve as containers for the asset group Rohre of the feature class 'Telekommunikation line' from the domain network.
Due to the multi-line representation of Rohre (see grey lines), containment associations via the geometry is not possible.
Trassen contain all the IDs of Rohre running through a Trasse in the ROHRE attribute field (see Attributtable in the screenshot).These are contained in the ID attribute field of Rohre.
Is it possible to carry out attribute-based containment associations via the ROHRE attribute field of Trassen and the ID attribute field of Rohre?

UT_Trasse_Containment.PNG


Thank you for your help

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

Associations aren't managed using primary/foreign key relationships, they are stored within the utility network. You can read more about containment associations here: Containment associations—ArcGIS Pro |  

To create/maintain associations you can use the modify associations tool, feature templates, or attribute rules. For your initial data-load you will need to use the import associations tool to import your existing associations using a flat file.

Documentation

View solution in original post

2 Replies
RobertKrisher
Esri Regular Contributor

Associations aren't managed using primary/foreign key relationships, they are stored within the utility network. You can read more about containment associations here: Containment associations—ArcGIS Pro |  

To create/maintain associations you can use the modify associations tool, feature templates, or attribute rules. For your initial data-load you will need to use the import associations tool to import your existing associations using a flat file.

Documentation

JoaquinMadrid1
New Contributor III

Also, @HannesFoth, following Robert's recommendations and as you configure the UN to support your containment (Association Role and the corresponding Association Rules) pay attention to the Deletion Semantics and Split Content Policy of your asset type(s) acting as Container.

Say you have a linear feature that contains either another linear feature or a non-spatial edge object. And you split the feature. Then,

If you configure Split Content as True:

  1. The longer segment of the split feature will be the original feature (shortened). Therefore, containing the original content and using the same containment association(s).
  2. The shorter segment, however, is a new feature with attribute values copied from the original feature (as long as the Split Policy of its coded value domain(s) are configured as Duplicate). But also, this shorter segment will contain a copy of the original content with the corresponding new association record(s)

If, on the other, the Split Content of the Association Role is set to False:

  1. The feature split behaves the same: longer-shorter/original-newcopy.
  2. But the original content now is shared between the two splits; i.e., a new containment association record is created between the original content and the new split segment.

Now say that you chose Split Content to be True. Then, if you were to merge the two segments back... you need to take into consideration your choice of the Deletion Semantics of the linear asset type acting as container. Since one of the segments will be deleted during the merge, Restricted will prevent you from doing so without first removing the association (whether deleting the contents or deleting the association leaving behind the content). If this is not the workflow that satisfies your editing requirements, you may want to consider configuring the Deletion Semantics as Cascade.

In essence, I am just pointing out that some configurations act together, and you need to be aware of the effects of one and the other with respect to your workflows.