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

[elinz]

DDM example:

If a enter a decimal minute component for latitude, the addin expects the longitude to also have a decimal minute component.

• Type in the following coordinate: 45 0.0N 100 0.0W The input is interpreted and output coordinates are displayed:

• Now edit 100 0.0W in the input textbox to be 100 0W by backspacing. The input is still interpreted and output coordinates are displayed:

• Now edit 100 0W in the input textbox to be 100W by backspacing. The input is no longer interpreted even through the values 45 0.0N 100 0.0W and 45 0.0N 100W are equivalent:

DMS example:

If a enter a seconds component for latitude, the addin expects the longitude to also have a seconds component.

• Type in the following coordinate: 45 0 0.0N 100 0 0.0W The input is interpreted and output coordinates are displayed:

• Now edit 100 0 0.0W in the input textbox to be 100 0W by backspacing. The input is not longer interpreted even through the values 45 0 0.0N 100 0 0.0W and 45 0 0.0N 100 0W are equivalent:

ArcGIS Pro and ArcMap issue

[elinz]

@nfeuerstein We will add a note to the doc about this limitation.

[dfoll]

@NatalieCampos can you please look at the documentation for this, (in the supported formats section) and see if you think this is sufficiently documented. if you feel it is, please remove the "affects documentation" tag, if not, we need to discuss what additionally needs written

[dfoll]

the four of us @NatalieCampos @topowright @lfunkhouser have reviewed what exists in the documentation, we believe that what is there satisfies the "affects documentation" tag, removing the "affects documentation" tag

[dfoll]

I do not believe this is an issue in Pro any longer with MT 3.0 build 48

[BobBooth]

The DDM case of this is still an issue: These cases work: 45 0.0N 100 0.0W 45 0.0N 100 0W This one does not work: 45 0.0N 100W