{"action":"opened","issue":{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/513","repository_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml","labels_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/513/labels{/name}","comments_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/513/comments","events_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/issues/513/events","html_url":"https://github.com/Esri/joint-military-symbology-xml/issues/513","id":352229563,"node_id":"MDU6SXNzdWUzNTIyMjk1NjM=","number":513,"title":"18-XXX-UK Boundary Amplifier Clarification","user":{"login":"joebayles","id":5016557,"node_id":"MDQ6VXNlcjUwMTY1NTc=","avatar_url":"https://avatars1.githubusercontent.com/u/5016557?v=4","gravatar_id":"","url":"https://api.github.com/users/joebayles","html_url":"https://github.com/joebayles","followers_url":"https://api.github.com/users/joebayles/followers","following_url":"https://api.github.com/users/joebayles/following{/other_user}","gists_url":"https://api.github.com/users/joebayles/gists{/gist_id}","starred_url":"https://api.github.com/users/joebayles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joebayles/subscriptions","organizations_url":"https://api.github.com/users/joebayles/orgs","repos_url":"https://api.github.com/users/joebayles/repos","events_url":"https://api.github.com/users/joebayles/events{/privacy}","received_events_url":"https://api.github.com/users/joebayles/received_events","type":"User","site_admin":false},"labels":[{"id":572363247,"node_id":"MDU6TGFiZWw1NzIzNjMyNDc=","url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/labels/B%20-%20APP-6","name":"B - APP-6","color":"d4c5f9","default":false},{"id":239324578,"node_id":"MDU6TGFiZWwyMzkzMjQ1Nzg=","url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/labels/C%20-%20Proposed","name":"C - Proposed","color":"f7c6c7","default":false},{"id":656111421,"node_id":"MDU6TGFiZWw2NTYxMTE0MjE=","url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/labels/S%20-%20Assigned%20to%20Committee","name":"S - Assigned to Committee","color":"D9D9D9","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/milestones/8","html_url":"https://github.com/Esri/joint-military-symbology-xml/milestone/8","labels_url":"https://api.github.com/repos/Esri/joint-military-symbology-xml/milestones/8/labels","id":3260007,"node_id":"MDk6TWlsZXN0b25lMzI2MDAwNw==","number":8,"title":"APP-6(D)(1)","description":"Upcoming Version of NATO APP-6","creator":{"login":"joebayles","id":5016557,"node_id":"MDQ6VXNlcjUwMTY1NTc=","avatar_url":"https://avatars1.githubusercontent.com/u/5016557?v=4","gravatar_id":"","url":"https://api.github.com/users/joebayles","html_url":"https://github.com/joebayles","followers_url":"https://api.github.com/users/joebayles/followers","following_url":"https://api.github.com/users/joebayles/following{/other_user}","gists_url":"https://api.github.com/users/joebayles/gists{/gist_id}","starred_url":"https://api.github.com/users/joebayles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joebayles/subscriptions","organizations_url":"https://api.github.com/users/joebayles/orgs","repos_url":"https://api.github.com/users/joebayles/repos","events_url":"https://api.github.com/users/joebayles/events{/privacy}","received_events_url":"https://api.github.com/users/joebayles/received_events","type":"User","site_admin":false},"open_issues":15,"closed_issues":0,"state":"open","created_at":"2018-04-11T19:44:57Z","updated_at":"2018-08-20T17:35:38Z","due_on":"2019-12-31T08:00:00Z","closed_at":null},"comments":0,"created_at":"2018-08-20T17:35:38Z","updated_at":"2018-08-20T17:35:38Z","closed_at":null,"author_association":"COLLABORATOR","body":"STATEMENT OF THE PROBLEM:\r\nUK system implementers have identified an issue with the amplifiers associated with Boundaries. In APP-6(D)(1) Para 8.2. the templates for the boundaries fields T and AS are used to describe both of the units or formations associated with the boundary. When encoding the symbol and transmitting via NVG it is impossible to differentiate between one instance of the name / geographical entity code and the second instance.\r\n\r\n![Extract from APP-6(D)(1) Table 8-2](https://user-images.githubusercontent.com/5016557/44356450-3bb1e800-a464-11e8-8a1f-bae8fd488066.png)\r\n\r\nAPP-6(A) Figure 2b and Table III shows the use of modifier fields T and T1 to describe the unique designation of the units or formations. Para 505. provides guidance on the use of numbering the fields.\r\nExtract from APP-6(A) Para 505. - \"In figure 3b, certain fields can be displayed more than once within a graphic. The unnumbered fields should be filled before the numbered fields, (i.e., fields W, H, and T should be used before fields W1, H1, and T1).\"\r\n\r\n![Placement of modifiers for points, areas, lines, and boundaries](https://user-images.githubusercontent.com/5016557/44356461-44a2b980-a464-11e8-8cbc-c072a457b615.png)\r\n\r\nThe NVG binding document for APP-6(A) for boundary symbols also provides the description for the modifiers as T and T1.\r\n\r\n![Extract from DRAFT ADatP-4733 Vol NVG APP-6(A) Binding](https://user-images.githubusercontent.com/5016557/44356474-4e2c2180-a464-11e8-87fb-befb14cdc588.png)\r\n\r\nAPP-6(A) and NVG Bindings correspond but APP-6(D)(1) does not have the facility to differentiate between multiple instances of fields T and AS when used on Control Measure Boundaries.\r\nAmplifier \"T\" already is broken out into T1 and T2 within APP-6(D)(1) and MIL-STD-2525D Chg 1 Draft (Jan 18). The amplifier harmonization SCP 18-006-UK left these amplifiers unchanged.\r\nT1 = Points - Purpose or Servicing Unit (APP-6(D)(1) Para 8.3.5.).\r\nT1 = Lines - Other lines that have a specific purpose and are also named as phase lines (such as restrictive fire line “RFL”) should have the primary purpose in the Field T1 labelled on top of the line at both ends of the line inside the lateral boundaries or as often as necessary for clarity. (APP-6(D)(1) Para 8.4.3.).\r\nT2 = Controlling Headquarters for fire support coordination measures. (APP-6(D)(1) Para 8.4.4.).\r\n\r\nPROPOSED SOLUTION:\r\nThe inclusion of the following text to explain the use of multiple instances of an amplifier in order to fully represent an object can be used.\r\nIn some cases, a tactical symbol may require multiple instances of a given amplifier in order to fully create or represent an object: examples of these fields are H, T, W and Y. The unnumbered fields shall be filled before the numbered fields (i.e., fields W, H and T shall be used before fields W1, H1 and T1).\r\nField AS can be split into AS and AS1 on the boundary templates as the amplifier has not already been allocated. Field AS must be linked with field T and Field AS1 must be linked with field T1 when used with boundaries.\r\nField T1 could be broken into two; lines and points, with a further subdivision of lines into Boundaries and Lines. The original field T will not be affected. Field T1 will need to have definitions in the amplifier table updated to reflect the multiple uses. Field T1 when associated with the specific symbol and associated SIDC will require a change in its use.\r\nSee Annex A to this SCP for the amendment instructions.\r\n\r\n![image](https://user-images.githubusercontent.com/5016557/44356628-be3aa780-a464-11e8-827d-e52abaf60171.png)\r\n\r\nGraphically (from a drawing perspective) all boundaries are identical. The placement of the boundary dictates whether it is a Lateral, Forward, or Rear boundary. SIDC \"110100 BOUNDARY\" should be used to depict all boundaries and SIDCs for the Lateral, Forward and Rear Boundaries, 110101, 110102 and 110103 should be removed from APP-6(D) and the examples left in for explanation purposes only."}}
{"actor":{"display_login":"joebayles"}}