Closed BobBooth closed 5 years ago
@kgonzago @dfoll @lfunkhouser @csmoore - coordinate conversion crash found, also affects visibility The 10/16/18 build of Distance and Direction (in December2018) is not affected.
Opened issue https://github.com/Esri/coordinate-conversion-addin-dotnet/issues/547 Closing this one.
I was not able to reproduce a crash in coordinate-conversion-addin-dotnet - but I was able to identify a possible source of the crash in Visibility.
Reopening issue and addressed in PR #310
Tested using Visibility build 32 build from this feature branch
This looks to be fixed with ArcGIS Pro 2.3.0.15723 the add-in displays that coordinates you entered in the input box are invalid. If you press Enter to try to use those coordinates, you get a message that the coordinates are out of bounds.
This still needs to be fixed with ArcMap 10.3.1 the add-in displays that coordinates you entered in the input box are invalid. If you press Enter to try to use those coordinates, ArcMap crashes.
Tested in ArcMap 10.3.1 (4959) - this workflow still crashes in ArcMap. @csmoore
10S FF 22750 4320
as your observer location
_note that it displays an "Invalid coordinate" warning.10S FF 22750 4320
as your observer location
_note that it displays an "Invalid coordinate" warning.@dfoll @BobBooth - I can reproduce and see the issue, I will add to the PR #310 in a few mins
@dfoll @BobBooth - PR #310 has been updated for ArcMap - please retest - sorry, not sure how I missed that
Retested these repro steps
This works with latest test build in ArcMap.
Rebuilt MT (176) with the recent changes and this looks good
Testing the latest build of the Visibility and Coordinate Conversion stand alone add-ins, on Pro (2.3.0_15735) and ArcMap (10.3.1) I have found a crash when certain values are pasted into the input box (the addins work fine for adding points by clicking on the map).
If I set the coordinate system for the map by adding the "ElevationUTM_Zone10" from solutions test catalog data, in MilitaryToolsTestData.gdb and click on the map with the identify tool, I get values in our AOI such as: (in ArcMap) 647,071.585 4,037,740.468 Meters 647,771.497 4,035,832.642 Meters or (in Pro) 624,927.73E 4,045,489.61N m 627,776.94E 4,043,909.37N m
DD and UTM values do not crash.
If I use these values as inputs for the LLOS, RLOS, and Coordinate Conversion input boxes, ArcGIS Pro (daily 2.3.0_15735), and ArcMap (10.3.1) both crash. I installed the previous versions of the addins [server]\Commercial\Solutions\DefenseSolutions and tested the September, August, and June 2018 builds. September and August had the crash, but the latest June build does not.