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

Coordinate Conversion MGRS, UTM, USNG columns written by addin to CSV only import if you set input format to match #541

Open BobBooth opened 5 years ago

BobBooth commented 5 years ago

Current behavior

When you export to CSV, the addin writes out the coordinates in the list view, with a column for each format that you've added for your output. So, if you add DD, DDM, MGRS, UTM outputs, you get a column in your csv file with values for each. This is good. When you import that table again, the DDD,DDM,DMS coordinates seem to import well. The MGRS, USNG, UTM coordinate columns give a "Please enter a valid coordinate" message, unless you set the input format to MGRS (etc) first. Then it seems to import that column/coordinate type fine. Ex_11_9.zip

Expected behavior

The addin should recognize and import UTM, USNG, MGRS coordinates in a column of a CSV without the user having to specify the input coordinate format.

To Repro,

extract the Ex_11_9.csv from the attached zip file. With the Input format at "default" In the CC addin, click Import. Choose DD or Coordinate for the input field. The coordinates should be added to the map and the list. Clear All With the Input format at "default" In the CC addin, click Import. Choose MGRS or UTM for the input field. Get a "Please enter a valid coordinate" message. Click OK a dozen times. No coordinates added. Clear all. Set the Input format to MGRS. In the CC addin, click Import. Choose MGRS for the input field. The coordinates should be added to the map and the list.

ArcGIS Pro 2.3.0. beta.1 build 14508 Military Tools Coordinate Conversion latest build (3.2.0.126) Tested on ArcMap 10.6.0 8184 and the CC 2.3.1.19, where it works as expected (no need to set input format before MGRS imports correctly).

dfoll commented 5 years ago

would like to look at this one again before we give this one to CT

dfoll commented 5 years ago

verified this is still an issue with current dev build