Hello,
I am trying to figure out how Utility Network Management handles existing associations when editing network data, especially when splitting associated objects. Please see the following example based on Electric Foundation V2 Solution:
A cable is associated with three conduits (Image 1). The cable is split in two places, which automatically adjusts the associations.
The new containment associations seem to be computed due to geometric intersections, among other things. I have the following questions about this:
Many thanks for the help.
Jürgen
Solved! Go to Solution.
Hi Jurgen. In the Utility Network Foundation, by default we set all split policy's to the Utility Network default setting, which is DO_NOT_SPLIT. DO_NOT_SPLIT has the following behaviour: The container's content will not be split if the container feature is split. If a parallel content line feature is found, the content will be contained by both sections of the container feature. If the content line is not parallel, the content will be contained by the container feature that is closest to it. This is the default.
You can change the split policy by running the SetAssociationRole gp tool and changing the split policy the the specific asset type. This will require the UN network topology to be disabled. You can also change it in the Asset Package before apply by editing the table B_ASSOCIATIONROLE, changing the splitpolicy column for the desired asset types.
Hi Jurgen. In the Utility Network Foundation, by default we set all split policy's to the Utility Network default setting, which is DO_NOT_SPLIT. DO_NOT_SPLIT has the following behaviour: The container's content will not be split if the container feature is split. If a parallel content line feature is found, the content will be contained by both sections of the container feature. If the content line is not parallel, the content will be contained by the container feature that is closest to it. This is the default.
You can change the split policy by running the SetAssociationRole gp tool and changing the split policy the the specific asset type. This will require the UN network topology to be disabled. You can also change it in the Asset Package before apply by editing the table B_ASSOCIATIONROLE, changing the splitpolicy column for the desired asset types.
Hi John,
Thank you very much for your answer. This makes the behavior a bit clearer to me. Meanwhile I could also find the place in the ArcGIS Pro documentation where this behavior is described. I still hope it's okay if I ask a few follow-up questions.
Your description assumes splitting a container. In my example, however, I split the content and the containers remain intact. Nevertheless, the associations of the newly created line sections to the containers are adjusted. Is the split policy you described for containers also responsible for this?
The documentation talks about a "system algorithm" in this context (https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/containment.htm). Is there more detailed information about this algorithm?
Are there other split policies besides the split policy for containers and the split policy for attribute domains that have influence on the associations in the utility network?
It would also be important for me to know if one can configure point objects in the Utility Network to split line objects when placed on them.
Many thanks and best regards,
Jürgen