search

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

No feedback why coordinate in common format is invalid #423

Closed BobBooth closed 7 years ago

BobBooth commented 7 years ago

I added a coordinate of Pyonyang, NK (39.0392° N, 125.7625° E) pasted from Google search. Got "Please Enter Valid Coordinate" error.
This should probably be an expected input format... image No feedback in message about what is wrong with the coordinate. By trial and error, determined that these are also invalid: 125.7625° E, 39.0392° N 39.0392 N, 125.7625 E Is the problem the spaces? This one is valid: 39.0392N, 125.7625E

(ArcGIS Pro 2.0, add-in downloaded from Solutions page, version for Pro 2.0 - add-in installer 6/28/2017)

NatalieCampos commented 7 years ago

The coordinates ( 39.0392° N, 125.7625° E) are not valid because there is a space between the fraction of degree mark and the Lat/Long. Removal of the space makes these valid coordinates. See the Supported format guide.

http://solutionsdev.arcgis.com/defense/help/coordinate-conversion/arcgis-pro/supported-notation-formats.htm

Closing issue.

NatalieCampos commented 7 years ago

Though upon further testing, the same format (39.0392° N, 125.7625° E) seems to be a valid format for Distance and Direction.

@nfeuerstein @lfunkhouser should both DD and CC accept the same coordinate variation? As is written for CC this issue is based on user error based on the supported format documentation. Maybe this is an enhancement request.

BobBooth commented 7 years ago

It would make sense to accept this format if Google is handing it out by default... image

Also, it would be nice if the CC tool could provide feedback on why the coordinate isn't being parsed.

BobBooth commented 7 years ago

image If we can parse space-delimited DMS, it seems strange not to be able to parse this case.