Utility Network Diagrams - Symbolizing Reduction Edges by Circuit Attribute (ELE_HV_Circuit)

[ByjuKG]

Hi everyone,
I’m creating a High Tension Utility Network diagram. In my diagram map, ELELine features are symbolized by the ELE_HV_Circuit attribute (unique values).

However, when multiple ELELine features are aggregated into a Reduction Edge, the diagram shows a dashed line, and the Reduction Edge does not carry (or inherit) the ELE_HV_Circuit value—so I can’t symbolize it the same way.

How can I symbolize Reduction Edges based on the same circuit attribute (or otherwise make Reduction Edges render like ELELine by circuit)?

Thanks!

(Byju)

[gis_KIWI4 · Accepted solution]

@ByjuKG - If you want to keep the symbology maybe try other layout options like removing vertices rather than using reduction edges.

That being said there is an "info" field on Reduction Edges that you could try to populate.

https://pro.arcgis.com/en/pro-app/latest/help/data/network-diagrams/network-diagrams-frequently-aske...

@AnneYvonneBlin might be able to help further. 

[ByjuKG]

@gis_KIWI4 Thanks for these two suggestions. I would like to use the "info" field add-in approach.  Other approach of removing vertices will not help as my ELELines have two points only and they are connected via ELEJunction on Tower locations to form a longer line.

Meantime, I have discovered another possibility to symbolize the Reduction Edges as per the original ELELine's ELE_HV_Circuit attribute. 

- Add ELELine to the diagram map as a layer

- Use "Add Join" function on the reduction edges layer. (Right click on Reduction Edges layer and select "Joins and Relates > Add Join")

Now we can use the GP tool "Apply Symbology from Layer" or directly change the Symbology of Reduction Edge layer.

Since the symbology is not persisted, I would like to develop an Add-In to populate "info" field on reduction edges.  If anyone has a sample pro-add-in that updates the "info" field, please share.

Thanking you in advance!

(Byju)

[AnneYvonneBlin]

Hi @ByjuKG 
@gis_KIWI4 is right. Starting with UN v7 and TN v4, each diagram feature class includes a new field called Info that you can fill and manage at your convenience using custom code. For example, this custom code can retrieve attribute values on diagram features that are aggregated under a reduction edge and bring up these attributes on that edge. Among our public ArcGIS Pro SDK Community Sample add ins, you can find two add-ins samples that exemplify how to fill that Info field:

• Bring Up Subnetwork Names On Diagram Edges
• Count Aggregated Network Elements

Please also note that, in very specific situations, you can set up Collapse Container rules or Reduce Junction rules on your diagram template to aggregate diagram features while preserving the original lines.

Example with a Reduce Junctions rule
Suppose a network that includes complex edges.
You select two connected complex edges as inputs like in the map below and generate a diagram.
Sample diagrams generated from two connected complex edges selected as inputs
By default, based on a template set up with no rule, the diagram opens as in the NoRule diagram map at the left in the above screenshot => all the junctions along the two input connected complex edges are represented in the diagram.
If you set up a Reduce Junction rule on your diagram template to simplify the diagram by reducing all junctions connecting two junctions in such a diagram, the diagram builder generates the diagram shown in the ReduceDegree2Junctions_DefaultRule diagram map (circled in blue above). You end up with a reduction edge (the dashed blue line) that aggregates the 2 input complex edges and all the junctions along them.
However, you can constraint the Reduce Junction rule to limit the reduction process along each complex edge. In this case, you end up with a diagram as in the ReduceDegree2Junctions_ConstrainedRule diagram map (circled in black above).

The differences in the Reduce Junction rule settings to get one or the other diagram are highlighted in the next screenshot. To constraint the reduction along each complex edge, you can set up the Connected edge constraints section and specify the attribute to control between two adjacent diagram edges. In this case, the junction is only reduced when the specified attribute is the same on the adjacent edges:
Reduce Junction rule settings to reduce junctions that connect two other junctions with or without constraint on the connected edges

Example with a Collapse Containers rule
You select a line in your network map. This line connects two junctions which are "contents" of two containers.
By default, based on a template set up with no rule, the diagram generated from that input line, opens as in the NoRule diagram map at the left in the screenshot below.
Sample diagrams generated with or without Collapse Containers rules

Suppose you want to generate a diagram where the two containers are collapsed.
To do so, you set up a Collapse Container rule on your diagram template. Without any specific constraints on this rule, the diagram builder generates the diagram shown in the CollapseContainers_DefaultRule diagram map (circled in blue above) => You end up with a reduction edge (the dashed blue line) between the two collapsed containers. This is the default behavior.
However, you can adjust the Collapse Container rule settings to keep the initial line. To do so, you must disable the Aggregate reconnected edges option. In this case, you end up with the diagram in the CollapseContainers_ConstrainedRule diagram map (circled in black above).
The differences in the Collapse Containers rule settings to get these two diagrams are highlighted in the next screenshot. 
Collapse Container rule settings to preserve lines between collapsed containers (or not)

Hopping this helps
Anne-Yvonne

[ByjuKG]

@AnneYvonneBlin Thank you very much for your detailed message.  

• Only the "info" attribute technique worked for me.
• I created an add-in to pull the ELE_HV_Circuit value from my ELELine features to the Reduction Edges. 
• Following API call helps me save the "Info" data: networkDiagram.SetDiagramElementInfo(filter, elementInfos);
• For the above API to work, I had to upgrade my network to 7.0 using the "UpgradeDataset" GP tool

My add-in project is attached. This add-in attach a text value to "Info" field.  

I have another requirement regarding layout of reduction edges that are nearly parallel and cose to each other. All edges falling within such a corridor must bend together and should be kept parallel and close together. ESRI's standard layouts functions does not help. I might also need a custom layout module.

After that, I need  yet another function to place available Towers along the path of reduction edge. When the reduction edge is moved / adjusted, these tower indicaters should also move together.  Pity that the standard tools don't have options to capture all such details that are needed in a diagram map!

[AnneYvonneBlin]

Hi @ByjuKG  
About "I have another requirement regarding layout of reduction edges that are nearly parallel and close to each other. All edges falling within such a corridor must bend together and should be kept parallel and close together.", did you give a try by applying the Partial Overlapping Edges layout? This layout could complete with good results when applying on a selection set of diagram edges.
Note that the zip file you attached looks to be empty

[ByjuKG]

@AnneYvonneBlin Sorry for the empty zip file.  That one was my first upload! When I try now to upload, I do see 146 KB indicator next to the file name.

The Partial Overlapping Edges Layout do help me. Thanks for pointing it out. But I need to really zoom in to see they are not overlapping. 

I have three parallel reduced edges. When I apply "Square Edges", I get two paths: one red line alone and the other two lines together  (blue line and dashed red line), as in the picture, on the right side of the M666 node. 

If I apply Partial Overlapping Edges, and zoom in, I can see separate lines.

Well, I still need a custom layout for bending these lines together like "Square Edges" layout. Is there a technique to avoid that custom development?

Regards,

Byju

[AnneYvonneBlin]

@ByjuKG, did you try applying the Partial Overlapping Edges with various Buffer Width and Offset distance parameters?