Closed elinz closed 7 years ago
This is what we will add to the known issues list in the documentation.
When entering integers without spaces the coordinates will be returned as inaccurate. As an example:
12 returns 1N 2E 1234 returns 4N 123E
Ready for testing
Assigning to MT PEs and @elinz who originally submitted the issue to verify
I'll take this one.
New results:
@elinz Mind giving this a quick once over to make sure it is now the desired output?
The expected behavior would be when a user puts in a coordinate that is not clear that the tool will prompt them to allow the tool to understand what they mean.
If a user puts in 11 or 1234 or 123456 as examples the feedback should be:
Currently this prompt happens correctly if there is a space in the inputs as an example 1 1, 12 34 , 123 456
@kgonzago 's PR merged - ready for retest in next build
Got this one again.
@csmoore @topowright I'm not sure the expected behavior now: I used the same values from above. 00, 45, and 457598 throw:
Build 1428
@ACueva 00, 45, and 457598 are invalid coordinates. The logic used to parse these coordinates assumes there will be a delimiter (comma, space, period, etc.) used to distinguish between x and y coordinates. 0 0 is valid but 00 (no spacing) is invalid.
@kgonzago Makes sense. Based off your reply I believe this issue is good to go. @topowright thoughts?
We need to look a the documentation.
@lfunkhouser at 2:25 pm, I tried to recheck out the "known issues for CC Addin for ArcGIS Pro" and it still says it is checked out by you.
@dfoll commented on Jan 14th about listing this as a known issue. This never made it into the known issue list; however, this no longer needs to be documented. When invalid coordinates are entered a user is now prompted that the coordinate is invalid.
The addin is generating output for input values that are ambiguous.
Some examples, below:
[ ] Input value: 00 This doesn't become a valid value until 00 is separated by a space, a comma or one of the other valid coord-pair-separators (http://desktop.arcgis.com/en/arcmap/10.3/tools/data-management-toolbox/supported-notation-formats.htm)
[ ] Input value: 45
[ ] Input value: 457898
@topowright FYI.