I recently migrated data to the electric utility network. In our old database, overhead electric lines could be snapped to poles.
I realized I can't do this in the UN because poles are stored in the structure network and overhead electric lines are stored in the electric network. I tried creating a rule to allow connectivity between the two features, but it seems you can't allow connectivity between domain network features and structure network features.
Since you can't snap an overhead line (electric line) to a pole (structure junction), how do you represent poles in the electric network? Or do you just keep them out entirely and only represent them in the structure network?
Solved! Go to Solution.
You use attachment and containment associations to create relationships between structure and domain features that allow you to see which structures are supporting which subnetworks or to include them in your trace results.
If you have a device attached to the pole this will happen automatically, but if you don't have any other equipment at a pole you can place a junction feature on the line then attach that junction to the pole. In the electrical model these are line ends and attachment junction features.
You use attachment and containment associations to create relationships between structure and domain features that allow you to see which structures are supporting which subnetworks or to include them in your trace results.
If you have a device attached to the pole this will happen automatically, but if you don't have any other equipment at a pole you can place a junction feature on the line then attach that junction to the pole. In the electrical model these are line ends and attachment junction features.
Ahh. Thank you for explaining, that makes sense.
When I place a MV line end feature on the end of an overhead line, it snaps to the end of the line at first, but then when I define the asset type of the line end as "Overhead line end MV" and click apply, the feature shifts away form the end of the line. Do you know why this is happening?
That sounds like an attribute rule is firing.