Closed topowright-zz closed 6 years ago
From @csmoore on January 23, 2018 21:26
@lfunkhouser @joebayles - do we have:
I believe the added image files were confined to:
This question might be premature, but thought I'd ask just in case there is a long lead time requesting/obtaining
From @joebayles on January 25, 2018 15:9
@csmoore we have the final version of APP-6D in Box. I believe you are correct with everything else. Check https://github.com/Esri/joint-military-symbology-xml/pull/396 for the SVGs.
From @csmoore on February 7, 2018 15:52
Just to update this task - when I looked this a couple weeks ago - here is what I found and updated
The changes from 2525D.0 (06/2014) to App6D.1 (10/2017) that were readily identifiable by just skimming the standard were:
While I was reviewing his, I went ahead and made the data updates I thought would be required for items 2-4) in branch: https://github.com/Esri/military-features-data/tree/csm/app6d-dev - To see/understand the primary changes needed, look at this commit: https://github.com/Esri/military-features-data/commit/615e4b05dd29376fefd22da8a488520d20d6e179
So this should be ready to at least attempt going through the process of creating the style and datamodel/GDB with this branch.
Also while reviewing the PR mentioned above I noticed some issues that might prevent using the JMSML source data - https://github.com/Esri/joint-military-symbology-xml/pull/396#issuecomment-361315594 but that repo/data is not needed at this time with the manual changes made in https://github.com/Esri/military-features-data/commit/615e4b05dd29376fefd22da8a488520d20d6e179
Example Frame Label Differences:
From @csmoore on February 24, 2018 1:1
Note: Updated the original issue comment above with high-level plan, potential subtasks, etc.
From @csmoore on March 8, 2018 17:48
This is in the Sprint plan so going to move in progress and verify there are no issues creating a style with the latest SVGs using Pro only.
From @lfunkhouser on March 8, 2018 21:55
@csmoore This is an epic and needs to be broken down into issues not just pulled in and worked on. There is no understanding among the team of what this issue means. The high-level plan needs to be broken down into manageable issues that can be worked on and closed out.
From @csmoore on March 9, 2018 12:17
@lfunkhouser - OK - I was just going to work on the first task above "Update stylx creation process to use Pro 2.0" but can wait until this complete item is planned+ready to work on - moving task back
This issue was moved to ArcGIS/military-symbology-styles#88
From @lfunkhouser on January 19, 2018 15:57
Support for APP-6(D) is needed for compliance with NATO systems. The APP-6(D) dictionary will support Runtime and ArcGIS Pro.
(Updated with potential tasks/plan)
Preparation
Stylx (Icons)
Stylx (Labels)
Dictionary Renderer
The other tasks below are not needed for the stylx creation, but are part of testing the overall solution
GDB
Military Overlay
Pro Symbol Editor
Copied from original issue: Esri/military-features-data#293