[ENH] - Update symbology and labels for Segments, Divisions, and Branches

[pjdohertygis]

Which app?

Other

Describe requirements

Now that SARCOP has been used +100 incidents, including several that have very large geography with many waypoints - we need to revisit the symbology and labeling for Divisions and Branches. During the 2025 January CA Wildfires, @oviera-napsg put a lot of work into enhancing the symbology and labeling to make it more clear at variou scales. Let's document the following:

• Outline color (hex codes) and thickness
• Fill color and transparency
• Scale visibility for features
• Label text font, color/size, background color
• Label scale visibility

We will need to be well documented for the migration to v10.

Alternatives

Status quo

Other Relevant Info

Updated version

Note the new segment symbology for underway - change in color and transparent fill added to deconflict with primary search tracklogs.

Priority impact

p1 - time sensitive

Impact

This is something that has come up on several incidents - while it is really just a quality of life improvement, these add up!

[oviera-napsg]

User complication: Division (By Status) is a separate layer than Divisions. In order to make visual use of the status information but also reduce layer complexity, a custom "Transparency by Attribute" expression is used to adjust fill transparency at various scales, so as to be useful at some scales, but not get in the way of other relevant information at other scales, particularly Search Segments.

Turn on Transparency by attribute
Create a custom expression:

var scale = $view.scale;

var transparency = When(
scale >= 80000, 70, // 70% transparency at or more zoomed out than 1:80,000
scale >= 40000, 85, // 85% transparency between 1:40,000 and 1:80,000
100 // 100% transparency (fully invisible) at more zoomed in than 1:40,000
);

return transparency;

Condense the sliders to a high value of 100 and low value of 70.
Set the Transparency range to 100 and 40.00
Do not Include in legend

Divisions is usually the highest order of operational area that most high-data volume Teams are concerned with. I suggest that the Divisions layer become the anchor point from which all other Operation Area polygon layers derived their relative symbology: visibility range, label classes, etc.

[oviera-napsg]

(!) Need to revisit and rebuild following Feb 2025 Floording and Winter Storm activities in TX, KY, and VA, as well as federal exercises. Looks like we experienced symbology blow-ups across Deployment and Sandbox.