Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTM Coordinate Entry need enhancement #526

Open
pjdohertygis opened this issue Jan 30, 2017 · 3 comments
Open

UTM Coordinate Entry need enhancement #526

pjdohertygis opened this issue Jan 30, 2017 · 3 comments

Comments

@pjdohertygis
Copy link

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

image

Or try the Esri Campus - this puts me in the South Pacific
34.0562, -117.1955
11S 0481954E 3768406N

image

But lat / long appears to work

image

@driskull
Copy link
Member

@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?

@pjdohertygis
Copy link
Author

pjdohertygis commented Jan 30, 2017 via email

@pjdohertygis
Copy link
Author

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.

image

@pjdohertygis pjdohertygis changed the title UTM Coordinate Entry not working UTM Coordinate Entry need enhancement Feb 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants