Symbology Filtering for Circuits

JoshuaMoreno

Hi everyone, looking to recreate something similar using custom symbology. In doing so, our team wants to be able to filter out circuits while still seeing something similar to the attached screenshot for those devices/structures that contain multiple circuits. I know you can filter by the subnetwork name where two circuits are contained/associated but that still keeps the entire other circuit shown. Any ideas on how this can be done, if at all possible? Thank you!

GIS_kiwi4

@Joshua_Moreno - If the aim is to just symbolize the manhole then this might be one way to do it.
In the past we have have had some workarounds were you have the layer and a copy of the layer but this is one is filtered by a criteria (in your case it might look like SUPPORTEDSUBNETWORKNAME contains "::" )


You can extend the same principle to devices within the manhole and have a copy of the device layer but this time have them symbolized by SUBNETWORKNAME. 

This will have a slight impact on the map as it's querying the layer multiple times but it ay turn out to be acceptable. 

If you are after the indication of what subnetworks are present within the manhole then maybe an acceptable solution is labelling using the SUPPORTEDSUBNETWORKNAME of the Manhole.

I also notice you have splices which can be labelled with the particular subnetwork they are associated with. 

But for symbolizing the exactly way you highlighted in the picture I don't think there is a dynamic way.
You will need to duplicate the subnetwork layer (subnetwork - display)and clip it using a buffered manhole location and then use the double ended arrow symbology including the colours. This way is good because you maintain the orientation of the lines, the colours but it won't be dynamic unless you can trigger the process every subnetwork update. Maybe a overnight process

If you prefer to keep it simple and the subnetworks don't change frequently - simply maintain another layer that is drawn manually that you can throw onto the map. But this opens up the possibility for data mismatch.