Mil Stdr 2525C Graphics Render Improperly

[fteel]

The following graphics do not render properly:
Taks->Disrupt
MOBILITY/SURVIVABILITY -> OBSTACLES -> OBSTACLE EFFECT -> DISRUPT
Chemically Contaminated Area
Halted Convoy
Biologically Contaminated Area
Minimum Safe Distance Zones
Roadblock Complete (executed)
Dynamic Depiction
Dummy Minefield (dynamic)
Biologically Contaminated Area
Biologically Contaminated Area

Also, all graphics that indicate it as a rectangle render as a square.

See images in Attachments

[michael-spinelli]

Let me ask a few things before I look deeper into this.

-Going by the Disrupt example, it looks like you didn't change the symbology standard from 2525B to 2525C.
you can do this globally:
RendererSettings.getInstance().setSymbologyStandard(RendererSettings.Symbology_2525C);
or per graphic:
attributes.put(MilStdAttributes.SymbologyStandard, String.valueOf(RendererSettings.Symbology_2525Bch2_USAS_13_14));

-Without knowing what the point placement is, the Disrupt looks like it's rendering ok.

-Contaminated areas, I'm not clear on what the issue you're seeing is.

-Looking at the minefields, I think you need to make sure you're setting the map scale properly. Unfortunately, the "right" value varies depending on the map technology.

-For the area's, are you passing in the appropriate width values?

Multi Point Tactical Graphics:
//(comma delimited for modifiers with multiple values)
modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000");

[fteel]

Hey Michael, Thanks for the quick response. Let me dig a little deeper into what you’ve suggested and see what I can come up with. V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Tuesday, September 22, 2020 7:41 AM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. Let me ask a few things before I look deeper into this.

…

-Going by the Disrupt example, it looks like you didn't change the symbology standard from 2525B to 2525C. you can do this globally: RendererSettings.getInstance().setSymbologyStandard(RendererSettings.Symbology_2525C); <https://github.com/missioncommand/mil-sym-android/wiki#21configuring-the-renderer-for-your-needs> or per graphic: attributes.put(MilStdAttributes.SymbologyStandard, String.valueOf(RendererSettings.Symbology_2525Bch2_USAS_13_14)); <https://github.com/missioncommand/mil-sym-android/wiki#322setting-attributes>

-Without knowing what the point placement is, the Disrupt looks like it's rendering ok.

-Contaminated areas, is your issue with the label placement? This could be affected by the map scale value you're using.

-Looking at the minefields, I think you need to make sure you're setting the map scale<https://github.com/missioncommand/mil-sym-android/wiki#3316scale-for-3d> properly. Unfortunately, the "right" value varies depending on the map technology.

-For the area's, are you passing in the appropriate width values? Multi Point Tactical Graphics: <https://github.com/missioncommand/mil-sym-android/wiki#321setting-modifiers> //(comma delimited for modifiers with multiple values) modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000"); — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4FI5E7R3JXF4DC62VLSHCLOZANCNFSM4RVA2RAA>.

[fteel]

Hi Michael, 1. We have, RendererSettings.getInstance().setSymbologyStandard( RendererSettings.Symbology_2525C ); 2. Task->Disrupt The image on the right is from 2525C. It depicts the symbol with the longest arrow on the bottom and has the letter “D” on the middle arrow. The placement image on the right shows the longest arrow on the top side and there is no “D”. While this render could be rotated to be in proper position it is expected that it will render as depicted in 2525C with the longest arrow on the bottom and the “D” on the middle arrow. 3. Mobility/Survivability->Obstacles->Obstacles Effect-> Disrupt The image on the right is from 2525C. It depicts the symbol with the longest arrow on the top. There is no way even with rotating the image that the render on the right can be aligned with the image from 2525C on the left. 4. The issues with Dummy Minefield, Dynamic Depiction, Contaminated Areas are that they are being rendered as triangles. 5. I am looking into the Rectangular images to see if we are passing in the modifiers properly. V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Tuesday, September 22, 2020 7:41 AM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. Let me ask a few things before I look deeper into this.

…

-Going by the Disrupt example, it looks like you didn't change the symbology standard from 2525B to 2525C. you can do this globally: RendererSettings.getInstance().setSymbologyStandard(RendererSettings.Symbology_2525C); <https://github.com/missioncommand/mil-sym-android/wiki#21configuring-the-renderer-for-your-needs> or per graphic: attributes.put(MilStdAttributes.SymbologyStandard, String.valueOf(RendererSettings.Symbology_2525Bch2_USAS_13_14)); <https://github.com/missioncommand/mil-sym-android/wiki#322setting-attributes>

-Without knowing what the point placement is, the Disrupt looks like it's rendering ok.

-Contaminated areas, is your issue with the label placement? This could be affected by the map scale value you're using.

-Looking at the minefields, I think you need to make sure you're setting the map scale<https://github.com/missioncommand/mil-sym-android/wiki#3316scale-for-3d> properly. Unfortunately, the "right" value varies depending on the map technology.

-For the area's, are you passing in the appropriate width values? Multi Point Tactical Graphics: <https://github.com/missioncommand/mil-sym-android/wiki#321setting-modifiers> //(comma delimited for modifiers with multiple values) modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000"); — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4FI5E7R3JXF4DC62VLSHCLOZANCNFSM4RVA2RAA>.

[fteel]

Hi Michael, It appears that although we set the modifiers and the values actually represent a rectangle the values are not disparate enough to make the image appear as a rectangle to the user. V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Tuesday, September 22, 2020 7:41 AM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. Let me ask a few things before I look deeper into this.

…

-Going by the Disrupt example, it looks like you didn't change the symbology standard from 2525B to 2525C. you can do this globally: RendererSettings.getInstance().setSymbologyStandard(RendererSettings.Symbology_2525C); <https://github.com/missioncommand/mil-sym-android/wiki#21configuring-the-renderer-for-your-needs> or per graphic: attributes.put(MilStdAttributes.SymbologyStandard, String.valueOf(RendererSettings.Symbology_2525Bch2_USAS_13_14)); <https://github.com/missioncommand/mil-sym-android/wiki#322setting-attributes>

-Without knowing what the point placement is, the Disrupt looks like it's rendering ok.

-Contaminated areas, is your issue with the label placement? This could be affected by the map scale value you're using.

-Looking at the minefields, I think you need to make sure you're setting the map scale<https://github.com/missioncommand/mil-sym-android/wiki#3316scale-for-3d> properly. Unfortunately, the "right" value varies depending on the map technology.

-For the area's, are you passing in the appropriate width values? Multi Point Tactical Graphics: <https://github.com/missioncommand/mil-sym-android/wiki#321setting-modifiers> //(comma delimited for modifiers with multiple values) modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000"); — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4FI5E7R3JXF4DC62VLSHCLOZANCNFSM4RVA2RAA>.

[fteel]

Michael, I am having trouble making sense out of modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000"); The best I can do is get an elongated rectangle that is higher than wider. The numbers don’t seem to have the same effect on the areas NFA ….. as they do on a Rectangular Target. Can you help me out? Is there any documentation? V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Tuesday, September 22, 2020 7:41 AM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. Let me ask a few things before I look deeper into this.

…

-Going by the Disrupt example, it looks like you didn't change the symbology standard from 2525B to 2525C. you can do this globally: RendererSettings.getInstance().setSymbologyStandard(RendererSettings.Symbology_2525C); <https://github.com/missioncommand/mil-sym-android/wiki#21configuring-the-renderer-for-your-needs> or per graphic: attributes.put(MilStdAttributes.SymbologyStandard, String.valueOf(RendererSettings.Symbology_2525Bch2_USAS_13_14)); <https://github.com/missioncommand/mil-sym-android/wiki#322setting-attributes>

-Without knowing what the point placement is, the Disrupt looks like it's rendering ok.

-Contaminated areas, is your issue with the label placement? This could be affected by the map scale value you're using.

-Looking at the minefields, I think you need to make sure you're setting the map scale<https://github.com/missioncommand/mil-sym-android/wiki#3316scale-for-3d> properly. Unfortunately, the "right" value varies depending on the map technology.

-For the area's, are you passing in the appropriate width values? Multi Point Tactical Graphics: <https://github.com/missioncommand/mil-sym-android/wiki#321setting-modifiers> //(comma delimited for modifiers with multiple values) modifiers.put(ModifiersTG.AM_DISTANCE,"1000,2000,3000"); — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4FI5E7R3JXF4DC62VLSHCLOZANCNFSM4RVA2RAA>.

[michael-spinelli]

It's all in the MilStd 2525

No Fire Area has 2 points and the width is determined by 1 "AM" value
modifiers.put(ModifiersTG.AM_DISTANCE,"1000");

Rectangular Target has 1 point (center) with 1 "AN" value for attitude/angle and 2 "AM" values for length and width
modifiers.put(ModifiersTG.AN_AZIMUTH,"45");//If I remember correctly, it can be degrees or mils depending on the symbol. Check MilStd.
modifiers.put(ModifiersTG.AM_DISTANCE,"1000, 2000");//in meters, AM, AM1, AM2....

[michael-spinelli]

Also, for Tactical Graphics, getSymbolDef will help you figure out what modifiers each symbol has.

[michael-spinelli]

For your areas that are coming out as triangle, are you saying you're adding more than three set of coordinates and they're still rendering as a triangle?

[fteel]

So for instance the Dummy Minefield (dynamic) we are passing in

…

-87.6886362173281,30.381411101605323

-87.6886362173281,30.382169886229793

-87.68938992380288,30.381790493917556 And getting this V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Wednesday, September 23, 2020 1:13 PM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. For your areas that are coming out as triangle, are you saying you're adding more than three set of coordinates and they're still rendering as a triangle? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4D33G2RH7ZVDXDSZJ3SHI3A7ANCNFSM4RVA2RAA>.

[michael-spinelli]

The picture didn't show up.
Can you reply directly on the issue tracker in github rather than using email?

Also, I plotted those points and they make a triangle.

[fteel]

[michael-spinelli]

I plotted the points from your email. It looks fine to me. What am I missing?:

I flipped the lat and lon values and got this as well:

[fteel]

So I sent the coordinates as a reference along with the picture that’s attached. The issue is that the boundary of the area as depicted in 2525C is not a triangle. V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Thursday, September 24, 2020 7:23 AM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. I plotted the points from your email. It looks fine to me. What am I missing?: <https://user-images.githubusercontent.com/5972575/94144311-f9c3af00-fe3e-11ea-816b-7e1c17eb2f74.png> I flipped the lat and lon values and got this as well: <https://user-images.githubusercontent.com/5972575/94144453-237cd600-fe3f-11ea-91cd-0923acaed0c3.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4AI5GEDWUBWWIGAA4TSHM23XANCNFSM4RVA2RAA>. <https://github.com/notifications/beacon/AO3KI4EM55GY2KBUCRRU3UTSHM23XA5CNFSM4RVA2RAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFGPVW5Y.gif>

[michael-spinelli]

It's a polygon based area. It works similar to Fire Support Area (FSA) and it takes the shape of whatever points you give it.

[fteel]

Michael, If I wanted to have symbol say like a hexagon is there an order in which the points have to be entered in the method RenderSymbolAsMilStdSymbol? V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Wednesday, September 23, 2020 12:20 PM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. It's all in the MilStd 2525 No Fire Area has 2 points and the width is determined by 1 "AM" value modifiers.put(ModifiersTG.AM_DISTANCE,"1000"); <https://user-images.githubusercontent.com/5972575/94046876-4061cc80-fd9f-11ea-89ca-33ddf72d92d0.png> Rectangular Target has 1 point (center) with 1 "AN" value for attitude/angle and 2 "AM" values for length and width modifiers.put(ModifiersTG.AN_AZIMUTH,"45");//If I remember correctly, it can be degrees or mils depending on the symbol. Check MilStd. modifiers.put(ModifiersTG.AM_DISTANCE,"1000, 2000");//in meters, AM, AM1, AM2.... <https://user-images.githubusercontent.com/5972575/94046230-6fc40980-fd9e-11ea-8f98-3d8abaf7359a.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4DO47VIL7N442QB35DSHIU3VANCNFSM4RVA2RAA>.

[michael-spinelli]

So, using something like a general area?
For something simple like that, I don't believe order matters.

You could also use the code "BS_AREA--------" for basic shape area. It's not a milstd symbol so you can't pass it to another system but you can draw a simple area with it.

[fteel]

Yes like a general area. For some reason we use a triangle for every general area that does not have a specific shape. Which make is quite confusing if you learn the symbols from the F.M. and then see a triangle. I don’t think I’ll be the one to fix them all but I need to understand how it works and at least have a couple examples in code. Is there an example that you could show me for a general area and how to use “BS_AREA--------” …. Would that be the sidc? V/R, Forrest G Teel Jr Software Engineer IV Augustine Consulting Inc Cell: 339-236-1472 Office: 774-413-5388 [email protected]<mailto:[email protected]> Winning is in the preperation not in the game! You are hereby notified that I DO NOT have the authority to direct you in any way to alter your contractual obligation. Further, if the Government, as a result of the information obtained from this email discussion DOES desire to alter your requirements, changes will be issued in writing and signed by the contracting officer. You should take no action on any change unless you receive such a contract modification. From: Michael Spinelli <[email protected]> Sent: Wednesday, September 30, 2020 1:33 PM To: missioncommand/mil-sym-android <[email protected]> Cc: Forrest Teel <[email protected]>; Author <[email protected]> Subject: Re: [missioncommand/mil-sym-android] Mil Stdr 2525C Graphics Render Improperly (#96) CAUTION:This email originated outside of the organization by a potentially untrusted source. So, using something like a general area? For something simple like that, I don't believe order matters. You could also use the code "BS_AREA--------" for basic shape area. It's not a milstd symbol so you can't pass it to another system but you can draw a simple area with it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO3KI4HGPLYLSENXFN46OV3SIN2WZANCNFSM4RVA2RAA>.

[michael-spinelli]

Yes, "BS_AREA--------" is just an SIDC we made up for the purpose of drawing a basic shape area. Like the other areas, it requires a minimum of 3 points but can have as many as you want to make whatever shape you want. They're no different in usage from the other areas you've been drawing (minefields, NFA, etc...).