nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Labels & Arcade Expression- is this a bug or by design?

evtguy

I've spent some quality time with Pro identifying its deficiencies in the context of my personal workflows and ran across this. I took a layer of cities and tried to label the polygons using the name field which has the city name but stored as all caps ("LOS ANGELES", "SAN DIEGO", etc).

No matter- I'll just add an Arcade expression and convert the labels to proper case on the fly:

Proper($feature.NAME)

Hmm. My labels are still all caps. This goes on for awhile. I tried different permutations of label expressions, VBScript vs Arcade, etc and I still could not get anything but upper case labels. I finally noticed that the Text Symbol Style I had selected was the Landform/Physical Region style, which shows an example of two letter As, both upper case. I changed my text symbol style to Landmark/POI and I finally get proper case labels.

So- was this by design or a bug? I didn't see anything in the help documentation that Arcade (or any label expression) will not override properties of the selected Text Symbol Style. I'm using Pro v2.1.0

Thoughts?

Steve

Encontre mais publicações marcadas com

Accepted answers

Mark Bockenhauer

The textcase in the symbol properties is not over-ridden by Arcade expressions.

Your expression works when Textcase is set to Normal, as part of the text symbol properties.

When text case is not Normal, Arcade expression does not apply.

For both pictures above the expression was defined:

Mark

All comments

deleted-user-sYHsW3p_gN5o

Agreed, Xander, but I think Steve still has a point in that the help documentation ought to have a warning about this somewhere. Or maybe a link to a troubleshooting guide.

XanderBakker

As I understand this is not a restriction of Arcade. It is a matter of the order that is applied in the process. The Arcade expression will transform the text correctly. The last step is to apply a style to the text. If the style implies that all text is displayed in upper case, it does not matter what happened before (upper case translated to proper case), since it will display all characters in upper case. In this case the importance is to understand the effect a style has on your labels.

evtguy

Thanks, Mark. As you point it out, that makes sense. I know that I did not see that myself but there are multiple dimensions of options in Pro. Perhaps the help documentation can be updated to reflect this restriction that Arcade (and other expression languages) respects.

Thanks again-