Coordinate Conversion input coordinate -- formatting lost in Northern Hemisphere

[BobBooth]

I added -- as a separator between the Lat Long values in a DD output. This output displayed in the List when I clicked in the Southern Hemisphere, but no dashes were returned when I clicked in the Northern Hemisphere.

The problem affects + and - symbols used as separators, as they also have significance in indicating hemisphere.
The problem does not affect other special characters, such as !,@,#,$,%,^,&,*,(,),=,<,>,?,/,,|,,.,

ArcGIS Pro 2.3.0 beta 1 build 14476
Coordinate Conversion 4.1.1.19 (latest October build)

[dfoll]

I would like to have this one worked on, but I think our team needs to research a little more first. Just thinking out loud without verifying the issue myself, I'm wondering if the example we give is confusing because - has a special meaning when it comes to coordinates.

• Do we get the same behavior using $$ or is this unique to --?

Definitely need to fix this, just think we could clean up this issue a little bit first

[BobBooth]

@dfoll - good point. I will look at this again.

[dfoll]

CT-Awaiting Response because we should do the research to find out if this bug is occurring because "minus" is a meaningful character. See comment

[BobBooth]

@dfoll - it is because the minus sign is meaningful. I did check on that, added it to the original issue description.
"...
The problem affects + and - symbols used as separators, as they also have significance in indicating hemisphere.
The problem does not affect other special characters, such as !,@,#,$,%,^,&,*,(,),=,<,>,?,/,,|,,.,
..."

[dfoll]

@saip in the comment above, @BobBooth believes this problem is occuring because the minus sign is a special character. Knowing that, are we able to move ahead with fixing this issue?

[dfoll]

spoke with @saip about this. I think we need to understand exactly how we need the parser to work to fix this issue. How do we get the code to understand - used as a delimiter, versus being used as a hemisphere designation?

For example, if the coordinate 54.72--48.37 is provided, how do we parse out if that is 54.72N-48.37W or 54.72N--48.37E from just what is provided textually.

[BobBooth]

So, we should detect+ and - symbols used as delimeters and warn the users that they are interpreted as hemisphere indicators only, cannot be also used as delimiters. Then not allow that input.

[dfoll]

@saip please check out @BobBooth comment on how we want the interaction to be.

• if the user tries to enter a + or - when creating custom formatting for DD/DDM/DMS, the input box should highlight red, with a tooltip style message that tells the user "+ and - are significant characters for latitude/longitude and cannot be used in custom formatting"

[dfoll]

#600 was created to wrap up this workflow. Without #600 the user will be unable to "mark" something as being in the Southern or Western hemisphere

[dfoll]

The logic that was used to issue this was to disallow "+/-" characters when entering custom formatting. This broke the fix that was put in for #468 in the PR #518. To resolve this regression issue we need to improve the logic that was used.

• Instead of absolutely disallowing "+/-", those characters should only be allowed within a latitude or longitude coordinate.
• "+/-" are still allowed when embedded in a latitude or longitude coordinate.
  • Example: "DD-MM-SS.SS DD-MM-SS.SS" is a valid coordinate formatting "-" is within the coordinate
  • Example: "DD-MM-SS.SS**-DD-MM-SS.SS**" is not a valid coordinate pair "-" is in front of/not within the coordinate
  • Example: "-DD-MM-SS.SS DD-MM-SS.SS" is not a valid coordinate pair "-" is in front of/not within the coordinate
  • Example: "DD-MM-SS.SS**+DD-MM-SS.SS**" is not a valid coordinate pair "-" is in front of/not within the coordinate

@saip this comment is instead of a design doc I mentioned about how we want to proceed with #468/#527 let me know if you need any further clarification to proceed with implementing this fix

[saip]

@dfoll Please confirm if below mentioned are valid/invalid coordinate formatting

• *-*DD-MM-SS.SS DD-MM-SS.SS
• DD-MM-SS.SS*+*DD-MM-SS.SS **

[dfoll]

@saip

*-*DD-MM-SS.SS DD-MM-SS.SS is not a valid coordinate pair because there is a "-" in front of the latitude [assuming this is a lat/lon pair, but lon/lat would not change anything, i only used the word to refer to the position]

DD-MM-SS.SS*+*DD-MM-SS.SS ** is not a valid coordinate pair because there is a "+" in front of the longitude [assuming this is a lat/lon pair, but lon/lat would not change anything, i only used the word to refer to the position]

`

[dfoll]

When creating custom formatting "+/-" are treated a special characters and cannot be placed by the user in front of either latitude or longitude. This prevents confusion in a case where a "-" has been inserted in front of a "-" that indicates S or W hemisphere.

If a user wants a "-" to display to indicate S or W hemisphere, they will use the "Show - for S/W hemisphere" checkbox

[dfoll]

• https://solutionsdev.arcgis.com/defense/help/coordinate-conversion/resources/june-2019-coordinate-conversion.htm
• \...\CoordinateConversion\Dev\148\
• https://solutionsdev.arcgis.com/defense/help/military-tools/resources/june-2019-military-tools-for-arcgis.htm
  -\...\DefenseSolutions\MilitaryToolsforArcGIS\Dev\314\

[lfunkhouser]

Verified in MT 314 and CC 148 and solutionsdev - not on STG yet.