Esri / coordinate-conversion-addin-dotnet

Addin for ArcMap and Pro for convenient coordinate conversion in Desktop.
Apache License 2.0
45 stars 20 forks source link

UTM using incorrect zone identifier #410

Closed adgiles closed 6 years ago

adgiles commented 7 years ago

If you expand the coordinate parts for a UTM coordinate the Zone is using the UTM Hemisphere Band (N or S) not the UTM Band:

capture

capture

topowright-zz commented 6 years ago

This needs to be verified.

topowright-zz commented 6 years ago

@kgonzago @jmccausland I do not see anything showing the user to pick utm zone band or hemi based on output. Can someone help me with this? I just do not understand this issue and how we fixed it.

topowright-zz commented 6 years ago

We need to provide clarity on this issue.

topowright-zz commented 6 years ago

Tested this on build 4 ArcGIS Pro 2.1 and it is no longer an issue.

lfunkhouser commented 6 years ago

This needs to be removed from the known issues, http://solutions.arcgis.com/defense/help/coordinate-conversion/resources/release-notes.htm before the closing label can be applied. Removing the E-verified label until this is addressed in the documentation.

BobBooth commented 6 years ago

NGA has a caution: "... CAUTION: IN MANY SYSTEMS, THE LETTER AFTER THE ZONE NUMBER DESIGNATES A LATITUDINAL BAND, NOT A HEMISPHERE. ..." http://earth-info.nga.mil/GandG/coordsys/grids/utm.html That indicates to me that NGA has a preference for Hemisphere Zone, not a Latitudinal Band method.

topowright-zz commented 6 years ago

At first I was thinking that we should go off of what NGA states, but their documentation shows that they support both, but with a warning from one. Checking how ArcGIS Pro does it I found that they use bands and we are using bands in our addin. I feel like this issue should be closed and we can readdresss this if a customer comes back to share this same issue.

image

topowright-zz commented 6 years ago

There are no documentation tasks that I feel like need to be done on this issue.

dfoll commented 6 years ago

To follow on with @topowright comment, the reason we are not going to list this as an issue addressed is that it should never have been listed as a known issue in the first place