Open joebayles opened 8 years ago
I noticed that the Utility modifier is not quite centered on the enemy frame (along with the echelon, which as stated below, is currently not allowed).
Is there a way to get a dump of complete symbols from you (Joe). I will manually review them an adjust as needed for the next release.
Mike
From: Joe Bayles [mailto:notifications@github.com] Sent: Wednesday, October 19, 2016 11:40 AM To: Esri/joint-military-symbology-xml Subject: EXT :[Esri/joint-military-symbology-xml] Space and Air Echelon and Mobility (#328)
Original question came from SMDC.
They reported a bug re: assigning echelon and mobility to Air tracks. Specifically, the echelon and/or the mobility amplifiers do not line up with the friendly frame. They work as expected in hostile, neutral, and unknown frames (see below). [10060100151102000700]https://cloud.githubusercontent.com/assets/5016557/19525793/03e239e0-95d7-11e6-8059-135a49e3a00f.png [10030100151102000700]https://cloud.githubusercontent.com/assets/5016557/19525805/09cd8dbe-95d7-11e6-82cc-db20893ce266.png
Responded to them that it wouldn't work, since it was never fixed. It wasn't fixed because it's not supposed to be possible. Echelon and Mobility are not valid in MIL-STD-2525D (see below). [image]https://cloud.githubusercontent.com/assets/5016557/19525037/8b4f82b4-95d4-11e6-81d2-cd35d6b54dab.png
Especially in the "a la carte" spirit of MIL-STD-2525D, this should change. It is possible to have a group of aircraft that might require an echelon (though the echelons might require additional names, like:
Additionally, we have aircraft that are ski-equipped (see below), which would match the requirement to use that mobility amplifier. [image]https://cloud.githubusercontent.com/assets/5016557/19525474/e5087d96-95d5-11e6-8dfd-0054226f1fc6.png
So, suggest the following course(s) of action:
FYI: @ottenwhttps://github.com/ottenw, @wmcgranehttps://github.com/wmcgrane, @Dbarnes1https://github.com/Dbarnes1
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/Esri/joint-military-symbology-xml/issues/328, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AG-ghdJbysXkrcyXQ_eMeTJqCr34CGmJks5q1jmygaJpZM4KbIOa.
@mepler Sure thing Mike, latest versions are here:
https://github.com/Esri/joint-military-symbology-xml/tree/dev/svg
Original question came from SMDC.
They reported a bug re: assigning echelon and mobility to Air tracks. Specifically, the echelon and/or the mobility amplifiers do not line up with the friendly frame. They work as expected in hostile, neutral, and unknown frames (see below).
Responded to them that it wouldn't work, since it was never fixed. It wasn't fixed because it's not supposed to be possible. Echelon and Mobility are not valid in MIL-STD-2525D (see below).
Especially in the "a la carte" spirit of MIL-STD-2525D, this should change. It is possible to have a group of aircraft that might require an echelon (though the echelons might require additional names, like:
Additionally, we have aircraft that are ski-equipped (see below), which would match the requirement to use that mobility amplifier.
So, suggest the following course(s) of action:
FYI: @ottenw, @wmcgrane, @Dbarnes1, @drdanstephens