search

Esri / military-symbology

A user-focused add-in for searching, creating, and editing military symbols in ArcGIS Pro.
Apache License 2.0
39 stars 10 forks source link

BUG-000113750 Military Symbol Editor: "Command and Control Lines" are not implemented according to Mil-Std 2525B Change 2 #233

Closed lfunkhouser closed 6 years ago

lfunkhouser commented 6 years ago
Salesforce ID: BUG-000113750
Salesforce Submitter: Jordan Bush
Salesforce Submit Date: 5/04/2018 12:21 PM
Salesforce Bug Type: Usability
Salesforce Severity: Medium
Repro Data: \\<>\sf_filestore\PRD\Attachments\Defects\BUG-000113750
Work Around: (n/a)
Product: ArcGIS Pro
Functional Category: ArcGIS for Defense
Client Platform: (n/a)
Version Found: 2.0
Planned Version Fixed: (n/a)
Steps to Repro: 1. Tested with ArcGIS Pro 2.1.2 with English locale (customer indicated version 2.0 and German locale) 2. ​Install the Military Symbol Editor (MSE) Add-in (https://solutions.arcgis.com/defense/help/military-symbol-editor/) 3. In a new project launch the MSE 4. In the MSE window Search Fire Support Lines 5. In case of MIL-STD-2525B w/CHANGE 2 specification page 483 and 484, TABLE B-IV, Hierarchy: 2.X.4.2.2.1 and 2.X.4.2.2.2, Template Graphic and Parameters Description 6. In case of MIL-STD-2525B w/CHANGE 2 specification page 483, TABLE B-IV, Hierarchy: 2.X.4.2.2.1, Template Graphic and Parameters Description 7. In case of MIL-STD-2525B w/CHANGE 2 specification page 483 and 484, TABLE B-IV, Hierarchy: 2.X.4.2.2.1 and 2.X.4.2.2.2, Template Graphic and Parameters Description 8. In case of MIL-STD-2525B w/CHANGE 2 specification page 67 ,TABLE XI and page 68, Figure 13 See attached PDFs and PNG for specs and details 1. Mil-Std 2525B chg 2 implementation: It is possible to define attributes which are not required by the standard (e.g. Echelon [B], Speed[Z], Additional Information [H]) 2. Mil-Std 2525B chg 2 implementation (only 2.X.4.2.2.1 Fire Support Coordination Line): For „planned“ / “anticipated” symbols the Line should be dashed) 3. Mil-Std 2525B chg 2 implementation: There ist no possibility to input a „Phase Line Identifier“ T1 4. Mil-Std 2525B chg 2 implementation: The date should be implemeted in traditional military notation If not given seconds SS may be left out (DDHHMMZMONYY) Comment:
lfunkhouser commented 6 years ago

There are four issues associated with two symbols logged in this single issue.

  1. Adding attributes that are not required by the standard. We can look into if there is a way to add validation for the attributes based on symbol set or another relevant grouping of symbols. Currently there is one schema that applies to all tactical graphic lines.
  2. Planned/anticipated symbols require the line to be dashed. It would be good if there way a setting to allow this to happen at the core level. More research is needed to determine if this can happen.
  3. Not all options are available under the Label tab. To fix this, add the option to label Unique Designation 1. There is a workaround for displaying the Phase Line Identifier. This can be added through the attribute table - Enter a value for Unique Designation 1 [T1] attribute and it will label the Phase Line.
  4. The workaround would be to make this a string; however, you lose the date-time value/functionality. Research is needed to see about adding DTG as a date-time format to be applied as a setting.
BobBooth commented 6 years ago

@lfunkhouser - re #4, we should be able to use a Python label expression and the strftime method on the datetime object to represent it in the label as desired. https://docs.python.org/2/library/datetime.html#strftime-and-strptime-behavior http://strftime.org/

lfunkhouser commented 6 years ago

This issue was moved to ArcGIS/military-symbology-styles#52