Previous releases

Releases

Previous releases of Coordinate Conversion are described in the following table:

DateDescription

September 2017

  • Issues addressed:
    • #412 Flash does not work on coordinates that were imported in ArcMap and ArcGIS Pro.

September 2017

  • Support for:
    • Web AppBuilder for ArcGIS 2.6 (Developer Edition)
  • The Coordinate Conversion widget is incorporated in Web AppBuilder for ArcGIS.

June 2017

  • Support for:
    • ArcGIS Pro 2.0
    • ArcMap 10.5.1
  • WGS84 support for the Web AppBuilder for ArcGIS widget.

May 2017

  • Support for:
    • ArcGIS Pro 1.4.1
    • Web AppBuilder for ArcGIS 2.3–2.4 (Developer Edition)

    Batch coordinate conversion

  • Issues addressed:
    • BUG-000099009—The Coordinate Conversion ArcMap 1.0.1 add-in fails to populate the DMS, DD, and DDM fields if the region is set to use a comma as the decimal separator.
    • BUG-000104918—ArcGIS Pro crashes when starting existing projects if the Coordinate Conversion pane is docked.
    • BUG-000102904—ArcMap crashes when changing display coordinates after using the Map Point Tool.

February 2017

  • Support for:
    • ArcGIS Pro 1.4
    • ArcMap 10.3.1–10.5
    • Web AppBuilder for ArcGIS 2.2 (Developer Edition)

Known issues

Known issues when using ArcGIS Pro include the following:

BugDescription
#243

Coordinate Conversion does not support diaeresis and double acute accent symbol for seconds mark.

#245

Coordinate Conversion expects components of latitude and longitude input values to be balanced.

#252

When converting coordinates in UTM, there are times the coordinates are rounded 1 meter.

#254

Coordinate Conversion autocorrects incorrect invalid coordinates.

#261

Coordinate Conversion does not provide an output MGRS or USNG coordinate in the polar regions.

#371

Dark Theme is not fully supported.

#403

The Ambiguous Coordinates dialog box appears for coordinates that are not ambiguous.

#404

Manual inputs are not added to the Batch Conversion list.

#406

A column heading error appears when exporting to CSV.

#407

Importing an open CSV file causes the application to crash.

#409

Exporting to KML causes export to KMZ.

#410

UTM uses incorrect zone identifier.

Known issues when using ArcMap include the following:

BugDescription
#244

Coordinate Conversion does not support diaeresis and double acute accent symbol for seconds mark.

#246

Coordinate Conversion expects components of latitude and longitude input values to be balanced.

#253

When converting coordinates in UTM, there are times the coordinates are rounded 1 meter.

#255

Coordinate Conversion autocorrects invalid input coordinates.

#262

Coordinate Conversion does not provide a valid output MGRS, USNG, or UTM coordinate in the polar regions.

#403

The Ambiguous Coordinates dialog box appears for coordinates that are not ambiguous.

#404

Manual inputs are not added to the Batch Conversion list.

#407

Importing an open CSV file causes the application to crash.

#408

Exporting to either CSV or KMZ locks the export file type until the ArcMap session is restarted.

#410

Incorrect zone is used for UTM coordinates when the output box is expanded.

#409

Exporting to KML causes export to KMZ.

Top