2525D Control Measure .svg errors

[Dbarnes1]

Below is a list of Control Measure Points, Lines, and Areas that have been classified as 'minor symbol issues,' meaning that the svg/emf source symbols have their own internal errors. These were given to us by DISA, and therefore will eventually need to be addressed in conjunction with them.

Fixed?	SymbolName	Entity	Type	Whats Wrong?
- [ ]	Fires Areas : Position Area For Artillery (PAA) : Rectangular	240501	Area	Text label uses halo, should be line break
- [ ]	Fires Areas : Position Area For Artillery (PAA) : Circular	240502	Area	Text label uses halo, should be line break
- [ ]	Protection Areas : Minefield : Dummy Minefield-Dynamic	270706	Area	Missing dotted line on top of polygon
- [ ]	Maneuver Lines : Forward Line of Troops : Friendly Present	140101	Line	Semicircles Overlapping
- [ ]	Maneuver Lines : Forward Line of Troops : Friendly Planned or on Order	140102	Line	Semicircles Overlapping
- [ ]	Maneuver Lines : Forward Line of Troops : Enemy Known	140103	Line	Semicircles Overlapping
- [ ]	Maneuver Lines : Forward Line of Troops : Enemy Suspected or Templated	140104	Line	Semicircles Overlapping
- [ ]	Maneuver Lines : Principal Direction of Fire	140500	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Friendly Aviation	140601	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Friendly Direction of Main Attack	140602	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Friendly Direction of Supporting Attack	140603	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Friendly Planned or on Order	140604	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Feint	140605	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Enemy Confirmed	140606	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Direction of Attack : Enemy Templated or Suspected	140607	Line	Tip of Arrow Misaligned
- [ ]	Maneuver Lines : Ambush	141700	Line	Tip of Arrow Misaligned, potentially other issues
- [ ]	Maneuver Areas : Battle Position : Contain	151204	Line	Tip of Arrow Misaligned; Text label uses halo, should be line break
- [ ]	Maneuver Areas : Battle Position : Retain	151205	Line	Text label uses halo, should be line break
- [ ]	Maneuver Areas : Support by Fire	152100	Line	Improper placement of anchor points
- [ ]	Maneuver Areas : Search Area/Reconnaissance Area	152200	Line	Tip of Arrow Misaligned
- [ ]	Maritime Lines : Bearing Line	220100	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Electronic	220101	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Electronic Warfare (EW)	220102	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Acoustic	220103	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Acoustic (Ambiguous)	220104	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Torpedo	220105	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Electro-Optical Intercept	220106	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Jammer	220107	Line	Halo instead of line break
- [ ]	Maritime Lines : Bearing Line : Radio Detection Finder (RDF)	220108	Line	Halo instead of line break
- [ ]	Fire Lines : Munition Flight Path	260600	Line	Halo instead of line break
- [ ]	Protection Areas : Obstacle Effects : Fix	270503	Line	Improper placement of anchor points
- [ ]	Protection Areas : Obstacle Effects : Turn	270504	Line	Tip of arrow misaligned
- [ ]	Protection Areas : Obstacle Bypass : Difficult	270602	Line	Improper zig-zag
- [ ]	Protection Areas : Ford Difficult	271600	Line	Improper zig-zag
- [ ]	Protection Points : Vertical Obstructions : Overhead Wire	282003	Line	Improper placement of anchor points
- [ ]	Protection Lines : Antitank Obstacles : Under Construction	290201	Line	Improper triangle placement
- [ ]	Protection Lines : Antitank Obstacles : Completed	290202	Line	Improper triangle placement
- [ ]	Protection Lines : Wire Obstacles : Single Fence Wire	290302	Line	Improper spacing of X's along line
- [ ]	Protection Lines : Ferry	290700	Line	Tip of arrow misaligned
- [ ]	Mission Tasks : Block	340100	Line	Halo instead of line break
- [ ]	Mission Tasks : Breach	340200	Line	Halo instead of line break
- [ ]	Mission Tasks : Bypass	340300	Line	Tip of arrow misaligned; Halo instead of line break
- [ ]	Mission Tasks : Canalize	340400	Line	Halo instead of line break
- [ ]	Mission Tasks : Clear	340500	Line	Tip of arrow misaligned; Halo instead of line break
- [ ]	Mission Tasks : Delay	340800	Line	Improper curve alignment; Tip of arrow misaligned; Halo instead of line break
- [ ]	Mission Tasks : Disrupt	341000	Line	Halo instead of line break
- [ ]	Mission Tasks : Isolate	341500	Line	Halo instead of line break
- [ ]	Mission Tasks : Occupy	341700	Line	Halo instead of line break
- [ ]	Mission Tasks : Penetrate	341800	Line	Halo instead of line break; Tip of arrow misaligned
- [ ]	Mission Tasks : Relief in Place (RIP)	341900	Line	Tip of arrow misaligned
- [ ]	Mission Tasks : Retire/Retirement	342000	Line	Tip of arrow misaligned; Halo instead of line break; Improper curve alignment
- [ ]	Mission Tasks : Secure	342100	Line	Tip of arrow misaligned; Halo instead of line break
- [ ]	Mission Tasks : Seize	342300	Line	Halo instead of line break
- [ ]	Mission Tasks : Withdraw	342400	Line	Halo instead of line break; Tip of arrow misaligned, Improper curve alignment
- [ ]	Mission Tasks : Withdraw Under Pressure	342500	Line	Halo instead of line break; Tip of arrow misaligned; improper curve alignment
- [ ]	Command and Control Points : Contact Point	130500	Point	Extraneous Line
- [ ]	Maritime Points : Electromagnetic Fix	212400	Point	Improper zig-zag alignment
- [ ]	Sustainment Points : General Supply : NATO Multiple Class Supply Point	321706	Point	Improper numeral alignment

[csmoore]

@Dbarnes1 - you might want to add a column(s) with a brief description of the issue with the SVG graphic & the link to the SVG. But you and @abouffard can coordinate on this & the best way to capture the specific issues that need addressed.

Just looking at the first SVG on the list - I'm not sure what the issue is (particularly since I believe these are the same images used in the standard) - so we'll want to confirm/double-check that the issue is in fact with the SVG source, and not some error in the conversion/creation process that we are just now discovering when we look at the final product in Pro:

[Dbarnes1]

@csmoore According to the standard the PAA label should not have a halo, rather there should be line break in the polygon and plain black text. See image below for reference. Many of the symbols have minor issues like this. While the symbols are completely usable, this is something I wanted to log in case we ever get the chance to impact changes in the actual creation of the .svg's

[Dbarnes1]

@csmoore I updated the initial table with comments on what is specifically wrong with each symbol

[csmoore]

@Dbarnes1 thanks for clarifying those - that is some detailed testing :clap:

[Dbarnes1]

https://github.com/Esri/joint-military-symbology-xml/blob/master/svg/KNOWN_ISSUES.md @abouffard I'm wondering if we should merge these pages or figure out some better way of displaying all the svg issues for 2525D?

[wmcgrane]

Although these svg files come from DISA, we actually have a contractor create them. I'm not a graphic designer, so to better understand the issue, please explain what a "halo" is in this context? I have a hunch based on the conversation, but want to make sure I address the issue accurately. Thanks,

Bill McGrane Chair, Symbology Standards Management Committee DISA BDC/EE212 Messaging Standards Section Ft. Meade, MD 301-225-7383

-----Original Message----- From: Daniel Barnes [mailto:[email protected]] Sent: Friday, September 04, 2015 11:24 AM To: Esri/joint-military-symbology-xml Subject: Re: [joint-military-symbology-xml] 2525D Control Measure .svg errors (#217)

@csmoore https://github.com/csmoore According to the standard the PAA label should not have a halo, rather there should be line break in the polygon and plain black text. See image below for reference. image https://cloud.githubusercontent.com/assets/13024357/9687387/13216774-52de-11e5-864c-e72f865ea707.png Many of the symbols have minor issues like this. While the symbols are completely usable, this is something I wanted to log in case we ever get the chance to impact changes in the actual creation of the .svg's

— Reply to this email directly or view it on GitHub https://github.com/Esri/joint-military-symbology-xml/issues/217#issuecomment-137765290 . https://github.com/notifications/beacon/AI5TbdD8jEFugVP4j8XrTtDmTWXEiVu0ks5oua72gaJpZM4F3ikq.gif

[Dbarnes1]

@wmcgrane A halo is when a background outline appears surrounding the text. Example below shows a slight gray halo surrounding the text. What is more concerning is that the line in the background does not break where the text is placed.

This is what this symbol should ideally look like, according to the standard.

Daniel Barnes Cartography Esri, Military and Intelligence Solutions Team [email protected]

[joebayles]

@wmcgrane:

Halos provide an outline effect around text to emphasize it in a complicated map.

So, what @Dbarnes1 is saying is:

We have placed the label in the line, as opposed to on the line; but instead of a proper line break that allows for the label to be read, we simply "reserve" some pixels around the label text, and that doesn't translate well at all.

Unless I'm mistaken, the line and area symbols we used to originally populate the 2525D style dictionary were from 2525C, so Dan is painstakingly going through the entire rendered symbol dictionary and finding the deltas, and in may cases fixing them.

@Dbarnes1: We should ensure that the line break scales in size in relation to the text (I know you're tracking, just haven't seen it written anywhere).

[abouffard]

Deferred this issue on the basis that DISA (SSMC) does not have their 2525 administrative assistance in place, and it is unclear when that assistance will be available.

[joebayles]

@mepler to review.

[joebayles]

@mepler made some changes, assigning to him to review and check off items.

Some items are implementation-based (i.e. line gaps for labels). Suggest we discuss how to make them happen.

@Dbarnes1 @csmoore @lfunkhouser @kerryrobinson

[joebayles]

@wmcgrane @ottenw @mepler Please review.