Draw Rules for Antitank Ditch and Wall
joebayles opened this issue · comments
From Esri/military-symbology#273
The point ordering for these two items is reversed, in both 2525C and 2525D.
Looking at the point order, some draw left to right, and others draw right to left, if the teeth are to be oriented the same way.
| Code | Name | Direction |
|---|---|---|
| 25290201 | Antitank Ditch-Under Construction | Right to Left |
| 25290202 | Antitank Ditch-Completed | Right to Left |
| 25290203 | Antitank Ditch Reinforced with Antitank Mines | Left to Right |
| 25290204 | Antitank Wall | Left to Right |
This issue also affects Obstacle Line (25290100), which is Right to Left.
FYI @ottenw, @wmcgrane, @mepler, @Twornicki
Concur with existence of this problem; will add to draw rules scrub / update I'm working on.
3 of 5 are drawn right to left, 2 of 5 are drawn left to right. My CP will change the 2 left to right so all 5 are drawn right to left.
Now that I am actively working on the change proposal to fix this issue, my initial thoughts on how to fix it may not be the best solution. All of the five obstacle lines listed in this issue share the identical draw rule Line1 in MIL-STD-2525D(1). In looking at these lines in the standard, I'm thinking they should have a draw rule and templates that have as much in common with wire and fence obstacles as possible. I'll have a working draft change proposal this week for the gentlemen listed in this issue.
Mr. Otten:
Is this issue OBE via the SP you submitted recently on draw rule changes, or is this a separate issue?
Bill
Bill McGrane
Chair, SSMC (Mil-Std-2525 Joint Military Symbology)
DISA BDE4
Standards Management Branch
Comm: 301-225-7383
DSN: 312-375-7383
…-----Original Message-----
From: Bill Otten <notifications@github.com>
Sent: Wednesday, May 1, 2019 2:05 PM
To: Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mcgrane, William M (Bill) CIV DISA BD (US) <william.m.mcgrane.civ@mail.mil>; Mention <mention@noreply.github.com>
Subject: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
________________________________
Now that I am actively working on the change proposal to fix this issue, my initial thoughts on how to fix it may not be the best solution. All of the five obstacle lines listed in this issue share the identical draw rule Line1 in MIL-STD-2525D(1). In looking at these lines in the standard, I'm thinking they should have a draw rule and templates that have as much in common with wire and fence obstacles as possible. I'll have a working draft change proposal this week for the gentlemen listed in this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub < Caution-#518 (comment) > , or mute the thread < Caution-https://github.com/notifications/unsubscribe-auth/ACHFG3OHEWPQ5VSIPRSHFX3PTHLTZANCNFSM4FS7SHUQ > . <Caution-https://github.com/notifications/beacon/ACHFG3MAG7BEHO5L6UP22HDPTHLTZA5CNFSM4FS7SHU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODUN45EQ.gif>
CLASSIFICATION: UNCLASSIFIED
Good Morning Bill (McG),
Happy Monday! I will have a new SP for this. It has expanded a bit in scope as I am looking at all lines within control measure symbology that include a "line decoration" and/or words to the effect of a reference to the decoration and "face towards the enemy" or "towards the obstacle". It'd on close to the top of my SCP drafting list so I would imaging I will be sending the draft to Carlos sometime this week.
Have a great day!
V/R,
Bill Otten
Senior Systems Engineer
PM Mission Command, TMD
SETA contractor support
CACI, INC. – FEDERAL
PM Mission Command Field Office
4722 Rideout Road, room C22B413
Redstone Arsenal, Alabama 35805
Office: 256-842-1948
Mobile: 443-243-9777
william.r.otten.ctr@mail.mil
Please consider the environment before printing this email
…-----Original Message-----
From: Mcgrane, William M (Bill) CIV DISA BD (US)
Sent: Monday, June 3, 2019 5:52 AM
To: Esri/joint-military-symbology-xml <reply@reply.github.com>; Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mention <mention@noreply.github.com>; Otten, William R CTR USARMY PEO C3T (USA) <william.r.otten.ctr@mail.mil>; Epler, Michael S [US] (MS) (Contr) <Michael.Epler@ngc.com>
Subject: RE: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518)
Mr. Otten:
Is this issue OBE via the SP you submitted recently on draw rule changes, or is this a separate issue?
Bill
Bill McGrane
Chair, SSMC (Mil-Std-2525 Joint Military Symbology)
DISA BDE4
Standards Management Branch
Comm: 301-225-7383
DSN: 312-375-7383
-----Original Message-----
From: Bill Otten <notifications@github.com>
Sent: Wednesday, May 1, 2019 2:05 PM
To: Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mcgrane, William M (Bill) CIV DISA BD (US) <william.m.mcgrane.civ@mail.mil>; Mention <mention@noreply.github.com>
Subject: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
________________________________
Now that I am actively working on the change proposal to fix this issue, my initial thoughts on how to fix it may not be the best solution. All of the five obstacle lines listed in this issue share the identical draw rule Line1 in MIL-STD-2525D(1). In looking at these lines in the standard, I'm thinking they should have a draw rule and templates that have as much in common with wire and fence obstacles as possible. I'll have a working draft change proposal this week for the gentlemen listed in this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub < Caution-#518 (comment) > , or mute the thread < Caution-https://github.com/notifications/unsubscribe-auth/ACHFG3OHEWPQ5VSIPRSHFX3PTHLTZANCNFSM4FS7SHUQ > . <Caution-https://github.com/notifications/beacon/ACHFG3MAG7BEHO5L6UP22HDPTHLTZA5CNFSM4FS7SHU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODUN45EQ.gif>
CLASSIFICATION: UNCLASSIFIED
Okay, great. Looking forward to seeing that SCP.
Bill
Bill McGrane
Chair, SSMC (Mil-Std-2525 Joint Military Symbology)
DISA BDE4
Standards Management Branch
Comm: 301-225-7383
DSN: 312-375-7383
…-----Original Message-----
From: Otten, William R CTR USARMY PEO C3T (USA) <william.r.otten.ctr@mail.mil>
Sent: Monday, June 3, 2019 8:17 AM
To: Mcgrane, William M (Bill) CIV DISA BD (US) <william.m.mcgrane.civ@mail.mil>; Esri/joint-military-symbology-xml <reply@reply.github.com>; Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mention <mention@noreply.github.com>; Epler, Michael S [US] (MS) (Contr) <Michael.Epler@ngc.com>
Subject: RE: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518) (UNCLASSIFIED)
CLASSIFICATION: UNCLASSIFIED
Good Morning Bill (McG),
Happy Monday! I will have a new SP for this. It has expanded a bit in scope as I am looking at all lines within control measure symbology that include a "line decoration" and/or words to the effect of a reference to the decoration and "face towards the enemy" or "towards the obstacle". It'd on close to the top of my SCP drafting list so I would imaging I will be sending the draft to Carlos sometime this week.
Have a great day!
V/R,
Bill Otten
Senior Systems Engineer
PM Mission Command, TMD
SETA contractor support
CACI, INC. – FEDERAL
PM Mission Command Field Office
4722 Rideout Road, room C22B413
Redstone Arsenal, Alabama 35805
Office: 256-842-1948
Mobile: 443-243-9777
william.r.otten.ctr@mail.mil
Please consider the environment before printing this email
-----Original Message-----
From: Mcgrane, William M (Bill) CIV DISA BD (US)
Sent: Monday, June 3, 2019 5:52 AM
To: Esri/joint-military-symbology-xml <reply@reply.github.com>; Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mention <mention@noreply.github.com>; Otten, William R CTR USARMY PEO C3T (USA) <william.r.otten.ctr@mail.mil>; Epler, Michael S [US] (MS) (Contr) <Michael.Epler@ngc.com>
Subject: RE: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518)
Mr. Otten:
Is this issue OBE via the SP you submitted recently on draw rule changes, or is this a separate issue?
Bill
Bill McGrane
Chair, SSMC (Mil-Std-2525 Joint Military Symbology)
DISA BDE4
Standards Management Branch
Comm: 301-225-7383
DSN: 312-375-7383
-----Original Message-----
From: Bill Otten <notifications@github.com>
Sent: Wednesday, May 1, 2019 2:05 PM
To: Esri/joint-military-symbology-xml <joint-military-symbology-xml@noreply.github.com>
Cc: Mcgrane, William M (Bill) CIV DISA BD (US) <william.m.mcgrane.civ@mail.mil>; Mention <mention@noreply.github.com>
Subject: [Non-DoD Source] Re: [Esri/joint-military-symbology-xml] Draw Rules for Antitank Ditch and Wall (#518)
All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.
________________________________
Now that I am actively working on the change proposal to fix this issue, my initial thoughts on how to fix it may not be the best solution. All of the five obstacle lines listed in this issue share the identical draw rule Line1 in MIL-STD-2525D(1). In looking at these lines in the standard, I'm thinking they should have a draw rule and templates that have as much in common with wire and fence obstacles as possible. I'll have a working draft change proposal this week for the gentlemen listed in this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub < Caution-#518 (comment) > , or mute the thread < Caution-https://github.com/notifications/unsubscribe-auth/ACHFG3OHEWPQ5VSIPRSHFX3PTHLTZANCNFSM4FS7SHUQ > . <Caution-https://github.com/notifications/beacon/ACHFG3MAG7BEHO5L6UP22HDPTHLTZA5CNFSM4FS7SHU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODUN45EQ.gif>
CLASSIFICATION: UNCLASSIFIED