dehmer
commented
1 year ago Disclaimer: I'm not an author of milsymbol and only give information I THINK is true.
Letter/alpha (15-char) SIDCs are defined in APP6C or MIL-STD 2525C (or older).
I'm not too familiar with milsymbol extension mechanism, but I can imagine that is quite hard to invent new SIDCs since a SIDC carries quite some semantics. I guess introducing new coding schemes or (battle) dimensions will lead nowhere, because they are simply not handled. But I can be wrong about this. Messing with existing coding schemes/dimension may produce unexpected results, since ranges of function ids are tested for specific meanings or requirements for different styling.
Introducing new Echelon will most probably not work. Even though only '-A' (team) up to '-N' (command) are taken, the SVG draw instructions are hard coded and cannot be extended.
Saying that, I'm currently playing with the idea to rewrite milsymbol to easily provide the possibility to add/register new symology standards only from (static) configuration files. Our software has quite some demand for additional/different 1-point symbols. I have some basic code working, but completely migrating APP6 C/D and 2525 B/C/D from milsymbol would be pretty demanding (but probably possible.)
spatialillusions
https://litpolukrbrig.wp.mil.pl/u/APP-6D_JOINT_MILITARY_SYMBOLOGY._16_October_2017.pdf
thats the APP 6D which contains only some number based sidcs
Background of the question is: I need to introduce a new set of symbols for non-military purposes and need to introduce new sidcs (as well as echelons btw) ; but it seems that the lib relies on the "correct" sidcs - so, is there any documentation about these letter based sidcs?
regarding the echelons - there is an Echelon defined between Platoon and Company (basically 4 circles, like two squads next to each other) - its not implemented so far (?)