Giters

Esri / joint-military-symbology-xml

Joint Military Symbology Markup Language is a data encapsulation of MIL-STD-2525D and APP-6(D).

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

APP6 Support in ArcGISRuntimeQt 100.3

JoergTurla opened this issue · comments

commented

Does the next release of ArcGISRuntimeQt (V100.3) supports APP6 symbology? If this is so, which relase will be supported?

commented

APP-6(B) is supported now if that is the version you are looking for:
http://solutions.arcgis.com/defense/help/military-symbology-styles/

commented

I found a APP-6(D) stylx file too:

https://github.com/Esri/military-features-data/blob/dev/military-symbology-styles/app6d/app6d.stylx

Are both supported in the future?

In APP-6(B) stylx some information are missing to handle input of multipoint symbols (e.g. gct_strings). The APP-6(D) seems to be complete.

commented

@JoergTurla APP-6(D) and APP-6(B) are both supported in the latest update release of ArcGIS Runtime SDKs, version 100.3, which was released July 2018. There is a current issue pertaining to the missing gct_ in the stylx development repository, Esri/military-features-data#319. If there is other information missing from the stylx files in order to support ArcGIS Runtime 100.3, please log an issue with Esri Support Services or in https://github.com/Esri/military-features-data.

commented

Hi!
I think that there are a couple of issues are also relevant:
A colleague of a different department generated some BUGS regarding MIL2525B:
We verified some of them in our department using MIL2525D and APP6D. From our point of view it looks like a general issue.
Some of the bugs are 'New' or 'Under Consideration', some "In Product Plan'.

I assume that if a BUG is accepted for a specific symbol or a general issue (like line style in 'BUG-000113738 When implementing MIL-STD 2525B Change 2, "planned“ / “anticipated” line symbols are not dashed.'), this issue is solved in all (or at least most) stylx!?
Or do we have to created additional cases regarding our the symbology we are using: APP6D and MIL252D?
This would increase the number of bugs.
I don´t want to make it more complicated than necessary. I just want to remind...

Here is an incomplete list of the bugs:

  • BUG-000113355 The Military Symbol Editor is missing the ability to add specific required symbol attributes from Table IV of the MIL-STD-2525B Change 2 standard.

  • BUG-000113744 In the Military Symbol Editor, the Light Line symbology for planned or anticipated does not match documentation specification.

  • BUG-000113781 Symbol with the SIDC "GMPSE----*** X" is titled "Shelter" in the Military Symbol Editor (Mil-Std 2525B chg 2), not as "Earthwork, Small Trench or Fortification" (2.X.3.3.1) as defined in Mil-Std.

  • BUG-000113698 The Military Symbol Editor tool does not have the correct symbology for the Assault Position in the 2525B Change 2 settings.

  • BUG-000113738 When implementing MIL-STD 2525B Change 2, "planned“ / “anticipated” line symbols are not dashed.

  • BUG-000113739 When implementing MIL-STD 2525B Change 2 / MIL-STD 2525D, the "Echolon“-attribute (size indicator) [B] is missing in the line.

Thank you