Why not add everything that is not in the symbol set of map.army?

[silly goober]

Specifically, I would very much like to see all symbols in the link below.

https://upload.wikimedia.org/wikipedia/commons/9/99/Military_Symbology_Guide.svg

Additionally, I would like some tactical tasks to be added such as engagement, assault, or engage with fire. Map.army misses out a lot of NATO symbols, and it would make a great addition to add all them to the symbol set.

[www.map.army]

Silly, thank you for your message and great to hear that you are using https://www.map.army.

Thank you for your request regarding the symbols in https://upload.wikimedia.org/wikipedia/commons/9/99/Military_Symbology_Guide.svg

We have to admit that we do not know the source of this ‘Quick Guide’. www.map.army and the backend web services which enable the military symbology base on MIL-STD-2525 Symbology Standards. Please check Chapter ‘MIL-STD-2525A’ in https://en.m.wikipedia.org/wiki/NATO_Joint_Military_Symbology. In the external links of the same Wikipedia article, you can find links to download the standards.

In short, we are fully compliant to MIL-STD-2525C. This builds the base line for interoperability between different Systems.

Please do not hesitate to contact us should you have further questions on https://www.map.army.

Kind regards
Martin from the map.army team

[Jay Smart]

 MIL-STD-2525C is out of date already for more then 10 years. 

There are changes in  MIL-STD-2525D https://www.jcs.mil/Portals/36/Documents/Doctrine/Other_Pubs/ms_2525d.pdf
For example symbols of machine gun in  MIL-STD-2525C  and  in MIL-STD-2525D are different

[www.map.army]

Jay, thank you for your message and great to hear that you are using https://www.map.army. You are absolutely correct that MIL-STD-2525C is not the latest version. Currently MIL-STD-2525E is the active standard. And the Symbology Standards Management Committee (SSMC) is working on MIL-STD-2525F.


However, for the free demo application hosted on map.army we do stick to MIL-STD-2525C. This is the last version of the MIL-STD-2525 standards which does not require a dictionary that defines the valid combination of Base Symbol, Modifier I and Modifier II out of all the possibilities. Such a dictionary becomes a requirement if an application should support abbreviation creation and support for multi-language.

Please do not hesitate to contact us if you should have further questions on https://www.map.army.

Best Regards

[Reuben Ellett]

It would be fantastic if it was updated though. It is very quickly becoming irrelevant as the symbology is so out of date (E.G. not able to create light armoured wheeled infantry)

[www.map.army]

Reuben, thank you for your message and great to hear that you are using https://www.map.army.

We currently do not plan to update to the latest version of MIL-STD-2525 for the free version of https://www.map.army. This does ensure that we do meet the interoperability standards according to Multilateral Interoperability Programme [https://en.wikipedia.org/wiki/Multilateral_Interoperability_Programme].

Important Hint:
For map.army (pro) or our backend services we can offer such an upgrade on a project basis. Please let us know if you are interested and what national dictionary you are using (definition of valid symbols, symbol names, aliases and abbreviations).

Please do not hesitate to contact us should you have further questions on https://www.map.army.

Kind regards