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 not visible in Sample Symbol Dictionary in 10.1.1

MarcoHüther

The labels in the SymbolDictonaryApp sample are only visible for a few symbols. For Air Tracks for example no labes are visible. In version 1.0 it works. Here is a screenshot:

[ATTACH=CONFIG]21488[/ATTACH]

screenshot.png

MdOmerHossain_0-1762445055842.png

Vind meer berichten getagd met

Accepted answers

All comments

MarkBaird

Hi

I'm assuming you are using 2525c symbology here.

We recently identified an issue with the UniqueDesignation section of the message which is typically used for adding labels to 2525C symbols. The problem is a case issue, so if you use "uniquedesignation" in your message instead it should work.

Does this help?

Mark

MarcoHüther

The problem still exists but only for a few symbols. Ground Tracks for example have an label, but Air Tracks not.

MarkBaird

I can see this too. I'll talk to the symbol dictionary team and report back...

Mark

CarlosColón-Maldonado

Was this resolved in 10.2?

CarlosColón-Maldonado

Will this be resolved in 10.2.3?

ChristopherMoore

Unfortunately, setting the properties to get the correct labels to show up using the MessageProcessor has been somewhat of a point of confusion, the Github repo that hosts this data attempts to clarify this here:

https://github.com/Esri/military-features-data/tree/master/data/mil2525c#modifier-label-fields

But I believe those properties names listed there have only been tested using the latest version so hopefully these will also match your version of the software. I *think* the only thing that changed from version to version was in older versions Case/Capitalization was not significant and in the newer versions the casing of the properties do matter. Hope it helps.

CarlosColón-Maldonado

Unfortunately, setting the properties to get the correct labels to show up using the MessageProcessor has been somewhat of a point of confusion

You aren't kidding!

... the Github repo that hosts this data attempts to clarify this

Where have you been for the last 10 months?;)
Thanks for the link.

I believe those properties names listed there have only been tested using the latest version so hopefully these will also match your version of the software. I *think* the only thing that changed from version to version was in older versions Case/Capitalization was not significant and in the newer versions the casing of the properties do matter.

I believe you have correct thinking. I'll give these instructions, and those on the link, a try and see what happens. Yes, this certainly helps. I appreciate your response.

CarlosColón-Maldonado

I'd like to report that the unpublicized properties listed in the aforementioned link completed most of my requirements, except one. The "datetimevalid" property seems to add a "/,", along with new line character to the displaying label. When I call 'this.setProperty("datetimevalid", timeFunction);' where 'timeFunction' equates to "172025ZAPR2014", I get the display below. Is there a workaround to this?

Screenshot-datetimevalid property.png

CarlosColón-Maldonado

After further testing, I learned that the "higherformation" property label behaves similarly to that of "datetimevalid" property label, except it doesn't include the comma after the forward slash. I've also tried all of the related properties pertaining to tactical graphics ("additionalinfo2", "uniquedesignation2", "zmax" and "zmin") on symbol codes of dimension type "Tactical Graphics", and none of them displayed any labels.

CarlosColón-Maldonado

The "datetimevalid" property seems to add a "/,", along with new line character to the displaying label. When I call 'this.setProperty("datetimevalid", timeFunction);' where 'timeFunction' equates to "172025ZAPR2014", I get the display below. Is there a workaround to this?

After inspecting the SQLite database, I noticed that the property requires three additional entries, "[datetimevalid] ,", which are suppose to indicate "DTG, ALTITUDE/DEPTH, LOCATION". How is this property suppose to be set? Can this property be explained because I have not seen this behavior on military fielded systems?

ChristopherMoore

I believe that property you mention: "[datetimevalid] ," is 4 separate properties from that Table mentioned ( https://github.com/Esri/military-features-data/tree/master/data/mil2525c#modifier-label-fields ) "datetimevalid" + "x" + "y" + "z"

In the standard (2525C) those x, y, z are the location and are on the same line/label as datetime.

Unfortunately, because of how the label is specified if you set one of the properties, it will turn them all on/set visible.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.