Open pjdohertygis opened 7 years ago
@pjdohertygis shouldn't the esri one be "11N" instead of "11S"?
and for wellington "60S" instead of "60G"? If I do those then it works. Maybe the letter is just messed up?
Ok looks like myself and the user I am supporting are using this framework which follows the MGRS Zones https://goo.gl/images/2SiY4Q
Perhaps the UTM entry should use the same standard or at least provide an autocorrect / suggestion?
Sent from my iPhone
On 31/01/2017, at 10:49, Matt Driscoll notifications@github.com wrote:
@pjdohertygis shouldn't the esri one be "11N" instead of "11S"?
and for wellington "60S" instead of "60G"? If I do those then it works. Maybe the letter is just messed up?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Ok - working with support (Esri Case #01881792) - the simple answer was to not use any letter in the zone (most GPS receiver give you a letter designation so the end user will likely add this in unless they receive an error telling them otherwise). Once we switched his northing and easting and took the letter out of the zone - it worked perfectly.
I highly suggest an enhancement request that makes this workflow more intuitive and has a more informative error message.
I have tried two examples from Google Chrome. @driskull can you replicate?
For example - I am currently located at -41.2952, 174.7776 60G 0313921E 5426085N WGS84
This puts me in the Bering Sea - not Wellington, NZ
Or try the Esri Campus - this puts me in the South Pacific 34.0562, -117.1955 11S 0481954E 3768406N
But lat / long appears to work