Hello. We are working on an UN electrical domain, which has two tiers: distribution and transmission, and we need to use NVR for distribution and ABC for transmission. Is this possible? And, how all of this work with the propagation?
I have been working in a Foundation environment and I see this:
But I'm not sure how it works.
Solved! Go to Solution.
The domain assigned at the field is what is shown in the Trace dialog for the network attribute. That is why we have a domain that shows the values of phases for transmission and distribution. You can assign different domains per subtype, but make sure the codes are aligned, as the values for the network attribute are defined in the trace and then evaluated per feature, regardless of domain.
@YulissaCamacho - I believe this is possible.
rom your requirements the equivalent domain description would look like -
0 | De-energized |
1 | R or C |
2 | V or B |
3 | VR or BC |
4 | N or A |
5 | NR or AC |
6 | NV or AB |
7 | NVR or ABC |
For more on attribute propagation -
https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/attribute-propagation.htm
From what I understand you want a separate phase lists for your distribution and transmission tiers.
You can create 2 separate phase network attributes (Electric_Distribution_Phase_Attribution and Electric_Transmission_Phase_Attribution) and assign them to the respective subtypes.
As for the attribute propagation, you will need to set them up in the subnetwork definition of each tier.
So, in each tier’s subnetwork definition, you would reference the correct phase attribute (transmission vs distribution).
Hi, thank you for your prompt response.
So, is it possible to assign different network attributes to each subtype?
@YulissaCamacho - I think what I meant was.
Create 2 domains - Electric_Distribution_Phase_Attribution and Electric_Transmission_Phase_Attribution
Add them as Network Attributes - Distribution_Phase and Transmission_Phase
Apply the domains to the subtypes
So you distribution lines attribute Phases will have the Electric_Distribution_Phase_Attribution domain assigned to it. Similarly Transmission lines will have the Electric_Transmission_Phase_Attribution domain assigned to it.
You should now be able to use them in setting up propagation and use them in tracing.
====================================================================
A note that I have not seen it done the 2 domain way and there might be some pitfalls to be aware of specially with subtypes which could be in one or more tiers. Someone more experienced might be able to weigh in here.
An easier way would be to consider if you can have one domain approach where 1 might indicate R or C and the user deciphers what phase it is based on the asset/tier they are looking at.
0 | De-energized |
1 | R or C |
2 | V or B |
3 | VR or BC |
4 | N or A |
5 | NR or AC |
6 | NV or AB |
7 | NVR or ABC |
The domain assigned at the field is what is shown in the Trace dialog for the network attribute. That is why we have a domain that shows the values of phases for transmission and distribution. You can assign different domains per subtype, but make sure the codes are aligned, as the values for the network attribute are defined in the trace and then evaluated per feature, regardless of domain.
Adding to what @MikeMillerGIS said (and going against what @gis_KIWI4 said in his second response). You only want to have one network attribute assigned to the field. As long as the codes are the same, you can have different domains assigned to each subtype. As long as they have the same codes, you could use different domains for each subtype of a class on the same field.
I'm not sure if we allow you to assign multiple network attributes to the same field, but even if you did you are going to get yourself in trouble when configuring your subnetwork definitions. When possible you want to have similar subnetwork definitions across your tiers, especially when features can exist in multiple tiers. If you don't, then when we are trying to mark subnetworks as dirty we don't know which tier's subnetwork definition to use and this can result in unexpected behavior.
@YulissaCamacho I just confirmed that you cannot assign more than one network attribute to the same field on the same class. Once a field is set to be a network attribute, it no longer appears in the list of available fields.
Network Attribute Assignments
Set Network Attribute Tool
Thanks for all your help, I think we can work with this.