Static/Dynamic control measures question

kjellmf commented 9 years ago

In the official 2525D PDF you find that many control measures have a Static/Dynamic or Shape/Size attribute. I assume that static means that the control measure is a single point, while a dynamic one consists of multiple points/segments etc.

In the JMSML schema I can't find any static/dynamic data attribute. Is it instead represented by the GeometryTypeattribute? Should I interpret GeometryType= POINT as a static control measure?

abouffard commented 9 years ago

Good question @kjellmf . I'd like to see what @mepler and @wmcgrane have to say regarding the definition of static vs. dynamic in the control measure documentation. We have plans to add more geometric/draw rule intelligence to the XML, so this information will probably be better captured that way.

kjellmf commented 9 years ago

I'm trying to figure out how to draw control measures on a map (web.application). For point geometries I can use the SVGs bundled with JMSML directly. Line and area control measures are a lot harder to draw. More meta data in the XML, like for instance anchor points, will hopefully make this easier.

abouffard commented 9 years ago

Yup, that's the idea. Our own implementation has all those anchor points defined and maintained externally. I'd like to see them centralized inside JMSML so that all implementers are working from a common definition of these. Same goal for label placement logic/rules.

wmcgrane commented 9 years ago

All:

Yes, these terms should be more accurately defined in order to avoid any misinterpretation and incorrect usage. The definitions currently in the standard are as follows: Paragraph 3.2.14. Dynamic amplifier. An amplifier whose size and placement are based on the attributes of an object and can change as these attributes and the scale of the background change. Paragraph 3.2.41. Static amplifier. An amplifier whose size and placement are fixed and remain constant.

When 2525 was first developed, its focus was primarily focused on surface (land and sea) and non-surface (sub and air) objects and their movements/direction of movements. For example: Paragraph 5.3.6.12.3 states that "...the static direction of movement amplifier is a fixed length and identifies only the direction of movement of the object."

In every appendix is this definition of a text amplifier: "The purpose of the static text amplifiers described in the appendix is to standardize the display of additional alphanumerical information on identity, movement and location and capabilities." Likewise, there is a definition of a graphic amplifier: "Graphic amplifiers can be static, located in a fixed position in relation to a track’s symbol, or dynamic and move about the symbol based on the track’s characteristics."

However, when we get into the Command and Control, METOC, and Cyber appendices, we do not see these definitions spelled out as clearly. Theoretically, it could be deduced that the application of those terms used in these appendices have the same meaning and function. But I do agree that it might be a good idea to make those definitions explicit in all appendices, or perhaps define them more broadly in the base document, thus eliminating the necessity of having to replicate identical definitions in every appendix. Indeed, better geometric/draw rule intelligence will help to improve the implementation and rendering of the symbols.

Thus is the SSMC chair's opinion. But the definitive answer will be determined by the SSMC members, as I have no vote (except in a tie) :-)

Regards,

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

-----Original Message----- From: Andy Bouffard [mailto:notifications@github.com] Sent: Friday, February 27, 2015 12:43 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Good question @kjellmf https://github.com/kjellmf . I'd like to see what @mepler https://github.com/mepler and @wmcgrane https://github.com/wmcgrane have to say regarding the definition of static vs. dynamic in the control measure documentation. We have plans to add more geometric/draw rule intelligence to the XML, so this information will probably be better captured that way.

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

ottenw commented 9 years ago

Classification: UNCLASSIFIED Caveats: NONE Good Afternoon Everyone,

My two cents worth - as I believe that control measure symbols are a bit challenging due to their complexity and variety. As the original words in this thread stated "...the definition of static vs. dynamic in the control measure documentation", I thought I would first research the older versions of MIL-STD-2525 to see the origin and whether or not the usage has changed over time. I found that the term "Static/Dynamic" appears first in MIL-STD-2525B (January 1999), in section B.5.4. Interesting in that while it specifically states "The Static/Dynamic column indicates whether the tactical graphic's size is fixed or changes in proportion with the background projection", the actual column in Table B-IV is titled "Fixed/Dynamic".

For the purpose of clarifying static vs. dynamic in the draw rules for MIL-STD-2525D Control Measure Symbols, I would offer the following.

The words Static/Dynamic need to be removed from the draw rules for individual symbols.  If these words are needed, then they should be defined up front one time rather than being repeated over and over in the 255 pages of Appendix H.

With regards to lines and areas, I would offer that any symbol containing two or more points is dynamic, as it will change depending on the point location, distance between points, and the number of points.

That leaves only single point symbols.  A single point symbol could be considered static if the single point control measure's "... size is fixed ... in proportion with the background projection".  But is this something that should be defined within the standard, or left up to an implementer of the standard?  If a system operator changes the map/image background for example from a 1:50,000 topographic line map (TLM) to a 1:250,000 scale Joint Operational Graphic (JOG) map, should the size of the single point control measures be unchanged / fixed / static, should they scale proportionally in relation to the updated map or image background and become 5X smaller and perhaps unrecognizable, or should that be left to the system implementer as a user defined display preference?

If the definition of the words Static/Dynamic are changed/added, I would suggest not including the word "projection" in the definition.  Projection has a very specific meaning in the geospatial world, and its inclusion in MIL-STD-2525 could cause more confusion than clarification.

Bill McGrane, time permitting, next week's SSMC meeting could be a good forum/time to discuss this topic / issue.

Have a great day.

V/R,

Bill Otten

Senior Professional Systems Engineer PM Mission Command TMD / PD FSC2 SETA contractor support (CSC)

PM Mission Command Field Office 106 Wynn Drive 2D300-B2 Huntsville, AL 35805-1957 256-842-1948 BB: 443-243-9777 william.r.otten.ctr@mail.mil Please consider the environment before printing this email

From: wmcgrane [mailto:notifications@github.com] Sent: Tuesday, March 10, 2015 2:27 PM To: Esri/joint-military-symbology-xml Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

All:

Yes, these terms should be more accurately defined in order to avoid any misinterpretation and incorrect usage. The definitions currently in the standard are as follows: Paragraph 3.2.14. Dynamic amplifier. An amplifier whose size and placement are based on the attributes of an object and can change as these attributes and the scale of the background change. Paragraph 3.2.41. Static amplifier. An amplifier whose size and placement are fixed and remain constant.

When 2525 was first developed, its focus was primarily focused on surface (land and sea) and non-surface (sub and air) objects and their movements/direction of movements. For example: Paragraph 5.3.6.12.3 states that "...the static direction of movement amplifier is a fixed length and identifies only the direction of movement of the object."

In every appendix is this definition of a text amplifier: "The purpose of the static text amplifiers described in the appendix is to standardize the display of additional alphanumerical information on identity, movement and location and capabilities." Likewise, there is a definition of a graphic amplifier: "Graphic amplifiers can be static, located in a fixed position in relation to a track's symbol, or dynamic and move about the symbol based on the track's characteristics."

However, when we get into the Command and Control, METOC, and Cyber appendices, we do not see these definitions spelled out as clearly. Theoretically, it could be deduced that the application of those terms used in these appendices have the same meaning and function. But I do agree that it might be a good idea to make those definitions explicit in all appendices, or perhaps define them more broadly in the base document, thus eliminating the necessity of having to replicate identical definitions in every appendix. Indeed, better geometric/draw rule intelligence will help to improve the implementation and rendering of the symbols.

Thus is the SSMC chair's opinion. But the definitive answer will be determined by the SSMC members, as I have no vote (except in a tie) :-)

Regards,

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

-----Original Message----- From: Andy Bouffard [mailto:notifications@github.com] Sent: Friday, February 27, 2015 12:43 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Good question @kjellmf https://github.com/kjellmf . I'd like to see what @mepler https://github.com/mepler and @wmcgrane https://github.com/wmcgrane have to say regarding the definition of static vs. dynamic in the control measure documentation. We have plans to add more geometric/draw rule intelligence to the XML, so this information will probably be better captured that way.

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

Reply to this email directly or view it on GitHubhttps://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78128992.

Classification: UNCLASSIFIED Caveats: NONE

kjellmf commented 9 years ago

Thank you for the clarification regarding dynamic vs static control measures. From the comments I conclude that I can interpret entities with GeometryType="POINT" (default value) as static and other values as dynamic.

wmcgrane commented 9 years ago

Bill Otten: Thank you for your input. I could make the time to discuss by turning this into a CP and adding it to the list for discussion. That thought had crossed my mind, so if I get the opportunity this week, I will draft a CP sponsored by DISA, and with your permission, I will use the language you've stated below as part of the CP.

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

-----Original Message----- From: ottenw [mailto:notifications@github.com] Sent: Tuesday, March 10, 2015 4:36 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Classification: UNCLASSIFIED Caveats: NONE Good Afternoon Everyone,

My two cents worth - as I believe that control measure symbols are a bit challenging due to their complexity and variety. As the original words in this thread stated "...the definition of static vs. dynamic in the control measure documentation", I thought I would first research the older versions of MIL-STD-2525 to see the origin and whether or not the usage has changed over time. I found that the term "Static/Dynamic" appears first in MIL-STD-2525B (January 1999), in section B.5.4. Interesting in that while it specifically states "The Static/Dynamic column indicates whether the tactical graphic's size is fixed or changes in proportion with the background projection", the actual column in Table B-IV is titled "Fixed/Dynamic".

For the purpose of clarifying static vs. dynamic in the draw rules for MIL-STD-2525D Control Measure Symbols, I would offer the following.

The words Static/Dynamic need to be removed from the draw rules for individual symbols. If these words are needed, then they should be defined up front one time rather than being repeated over and over in the 255 pages of Appendix H.
With regards to lines and areas, I would offer that any symbol containing two or more points is dynamic, as it will change depending on the point location, distance between points, and the number of points.
That leaves only single point symbols. A single point symbol could be considered static if the single point control measure's "... size is fixed ... in proportion with the background projection". But is this something that should be defined within the standard, or left up to an implementer of the standard? If a system operator changes the map/image background for example from a 1:50,000 topographic line map (TLM) to a 1:250,000 scale Joint Operational Graphic (JOG) map, should the size of the single point control measures be unchanged / fixed / static, should they scale proportionally in relation to the updated map or image background and become 5X smaller and perhaps unrecognizable, or should that be left to the system implementer as a user defined display preference?
If the definition of the words Static/Dynamic are changed/added, I would suggest not including the word "projection" in the definition. Projection has a very specific meaning in the geospatial world, and its inclusion in MIL-STD-2525 could cause more confusion than clarification.

Bill McGrane, time permitting, next week's SSMC meeting could be a good forum/time to discuss this topic / issue.

Have a great day.

V/R,

Bill Otten

Senior Professional Systems Engineer PM Mission Command TMD / PD FSC2 SETA contractor support (CSC)

PM Mission Command Field Office 106 Wynn Drive 2D300-B2 Huntsville, AL 35805-1957 256-842-1948 BB: 443-243-9777 william.r.otten.ctr@mail.mil Please consider the environment before printing this email

From: wmcgrane [mailto:notifications@github.com] Sent: Tuesday, March 10, 2015 2:27 PM To: Esri/joint-military-symbology-xml Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

All:

Yes, these terms should be more accurately defined in order to avoid any misinterpretation and incorrect usage. The definitions currently in the standard are as follows: Paragraph 3.2.14. Dynamic amplifier. An amplifier whose size and placement are based on the attributes of an object and can change as these attributes and the scale of the background change. Paragraph 3.2.41. Static amplifier. An amplifier whose size and placement are fixed and remain constant.

When 2525 was first developed, its focus was primarily focused on surface (land and sea) and non-surface (sub and air) objects and their movements/direction of movements. For example: Paragraph 5.3.6.12.3 states that "...the static direction of movement amplifier is a fixed length and identifies only the direction of movement of the object."

In every appendix is this definition of a text amplifier: "The purpose of the static text amplifiers described in the appendix is to standardize the display of additional alphanumerical information on identity, movement and location and capabilities." Likewise, there is a definition of a graphic amplifier: "Graphic amplifiers can be static, located in a fixed position in relation to a track's symbol, or dynamic and move about the symbol based on the track's characteristics."

However, when we get into the Command and Control, METOC, and Cyber appendices, we do not see these definitions spelled out as clearly. Theoretically, it could be deduced that the application of those terms used in these appendices have the same meaning and function. But I do agree that it might be a good idea to make those definitions explicit in all appendices, or perhaps define them more broadly in the base document, thus eliminating the necessity of having to replicate identical definitions in every appendix. Indeed, better geometric/draw rule intelligence will help to improve the implementation and rendering of the symbols.

Thus is the SSMC chair's opinion. But the definitive answer will be determined by the SSMC members, as I have no vote (except in a tie) :-)

Regards,

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

-----Original Message----- From: Andy Bouffard [mailto:notifications@github.com] Sent: Friday, February 27, 2015 12:43 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Good question @kjellmf https://github.com/kjellmf . I'd like to see what @mepler https://github.com/mepler and @wmcgrane https://github.com/wmcgrane have to say regarding the definition of static vs. dynamic in the control measure documentation. We have plans to add more geometric/draw rule intelligence to the XML, so this information will probably be better captured that way.

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

Reply to this email directly or view it on GitHubhttps://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78128992.

Classification: UNCLASSIFIED Caveats: NONE

— Reply to this email directly or view it on GitHub https://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78142556 . https://github.com/notifications/beacon/AI5TbX-wlP-CRdQMlrWi_1ki2y64NKT6ks5nz01EgaJpZM4DnHGQ.gif

ottenw commented 9 years ago

Classification: UNCLASSIFIED Caveats: NONE Good Morning Bill McGrane,

Thanks - feel free to use the language in my post - it is for public consumption.

Have a great day.

V/R,

Bill Otten

Senior Professional Systems Engineer PM Mission Command TMD / PD FSC2 SETA contractor support (CSC)

PM Mission Command Field Office 106 Wynn Drive 2D300-B2 Huntsville, AL 35805-1957 256-842-1948 BB: 443-243-9777 william.r.otten.ctr@mail.mil Please consider the environment before printing this email

From: wmcgrane [mailto:notifications@github.com] Sent: Wednesday, March 11, 2015 5:57 AM To: Esri/joint-military-symbology-xml Cc: Otten, William R CTR (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Bill Otten: Thank you for your input. I could make the time to discuss by turning this into a CP and adding it to the list for discussion. That thought had crossed my mind, so if I get the opportunity this week, I will draft a CP sponsored by DISA, and with your permission, I will use the language you've stated below as part of the CP.

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

-----Original Message----- From: ottenw [mailto:notifications@github.com] Sent: Tuesday, March 10, 2015 4:36 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Classification: UNCLASSIFIED Caveats: NONE Good Afternoon Everyone,

My two cents worth - as I believe that control measure symbols are a bit challenging due to their complexity and variety. As the original words in this thread stated "...the definition of static vs. dynamic in the control measure documentation", I thought I would first research the older versions of MIL-STD-2525 to see the origin and whether or not the usage has changed over time. I found that the term "Static/Dynamic" appears first in MIL-STD-2525B (January 1999), in section B.5.4. Interesting in that while it specifically states "The Static/Dynamic column indicates whether the tactical graphic's size is fixed or changes in proportion with the background projection", the actual column in Table B-IV is titled "Fixed/Dynamic".

For the purpose of clarifying static vs. dynamic in the draw rules for MIL-STD-2525D Control Measure Symbols, I would offer the following.

The words Static/Dynamic need to be removed from the draw rules for individual symbols. If these words are needed, then they should be defined up front one time rather than being repeated over and over in the 255 pages of Appendix H.
With regards to lines and areas, I would offer that any symbol containing two or more points is dynamic, as it will change depending on the point location, distance between points, and the number of points.
That leaves only single point symbols. A single point symbol could be considered static if the single point control measure's "... size is fixed ... in proportion with the background projection". But is this something that should be defined within the standard, or left up to an implementer of the standard? If a system operator changes the map/image background for example from a 1:50,000 topographic line map (TLM) to a 1:250,000 scale Joint Operational Graphic (JOG) map, should the size of the single point control measures be unchanged / fixed / static, should they scale proportionally in relation to the updated map or image background and become 5X smaller and perhaps unrecognizable, or should that be left to the system implementer as a user defined display preference?
If the definition of the words Static/Dynamic are changed/added, I would suggest not including the word "projection" in the definition. Projection has a very specific meaning in the geospatial world, and its inclusion in MIL-STD-2525 could cause more confusion than clarification.

Bill McGrane, time permitting, next week's SSMC meeting could be a good forum/time to discuss this topic / issue.

Have a great day.

V/R,

Bill Otten

Senior Professional Systems Engineer PM Mission Command TMD / PD FSC2 SETA contractor support (CSC)

PM Mission Command Field Office 106 Wynn Drive 2D300-B2 Huntsville, AL 35805-1957 256-842-1948 BB: 443-243-9777 william.r.otten.ctr@mail.milmailto:william.r.otten.ctr@mail.mil Please consider the environment before printing this email

From: wmcgrane [mailto:notifications@github.com] Sent: Tuesday, March 10, 2015 2:27 PM To: Esri/joint-military-symbology-xml Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

All:

Yes, these terms should be more accurately defined in order to avoid any misinterpretation and incorrect usage. The definitions currently in the standard are as follows: Paragraph 3.2.14. Dynamic amplifier. An amplifier whose size and placement are based on the attributes of an object and can change as these attributes and the scale of the background change. Paragraph 3.2.41. Static amplifier. An amplifier whose size and placement are fixed and remain constant.

When 2525 was first developed, its focus was primarily focused on surface (land and sea) and non-surface (sub and air) objects and their movements/direction of movements. For example: Paragraph 5.3.6.12.3 states that "...the static direction of movement amplifier is a fixed length and identifies only the direction of movement of the object."

In every appendix is this definition of a text amplifier: "The purpose of the static text amplifiers described in the appendix is to standardize the display of additional alphanumerical information on identity, movement and location and capabilities." Likewise, there is a definition of a graphic amplifier: "Graphic amplifiers can be static, located in a fixed position in relation to a track's symbol, or dynamic and move about the symbol based on the track's characteristics."

However, when we get into the Command and Control, METOC, and Cyber appendices, we do not see these definitions spelled out as clearly. Theoretically, it could be deduced that the application of those terms used in these appendices have the same meaning and function. But I do agree that it might be a good idea to make those definitions explicit in all appendices, or perhaps define them more broadly in the base document, thus eliminating the necessity of having to replicate identical definitions in every appendix. Indeed, better geometric/draw rule intelligence will help to improve the implementation and rendering of the symbols.

Thus is the SSMC chair's opinion. But the definitive answer will be determined by the SSMC members, as I have no vote (except in a tie) :-)

Regards,

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

-----Original Message----- From: Andy Bouffard [mailto:notifications@github.com] Sent: Friday, February 27, 2015 12:43 PM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)

Good question @kjellmf https://github.com/kjellmf . I'd like to see what @mepler https://github.com/mepler and @wmcgrane https://github.com/wmcgrane have to say regarding the definition of static vs. dynamic in the control measure documentation. We have plans to add more geometric/draw rule intelligence to the XML, so this information will probably be better captured that way.

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

Reply to this email directly or view it on GitHubhttps://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78128992.

Classification: UNCLASSIFIED Caveats: NONE

Reply to this email directly or view it on GitHub https://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78142556 . https://github.com/notifications/beacon/AI5TbX-wlP-CRdQMlrWi_1ki2y64NKT6ks5nz01EgaJpZM4DnHGQ.gif

Reply to this email directly or view it on GitHubhttps://github.com/Esri/joint-military-symbology-xml/issues/174#issuecomment-78242478.

Classification: UNCLASSIFIED Caveats: NONE

wmcgrane commented 9 years ago

Thanks.

-----Original Message----- From: ottenw [mailto:notifications@github.com] Sent: Wednesday, March 11, 2015 9:15 AM To: Esri/joint-military-symbology-xml Cc: McGrane, William M CIV DISA EE (US) Subject: Re: [joint-military-symbology-xml] Static/Dynamic control measures question (#174)