Issues after testing #500 in ArcMap
See original GitHub issueIssues after testing #500 in ArcMap:
Incident Hot Spot
- Change Parameter Name
Incidents_OptimizedHotSpotAn
toIncident Hot Spot
- Tool defaults back to ArcGIS/default.gdb
Hot Spot by Area
-
Keeps features selected after completed analysis (Clear Selection either in doc or tool)
-
Group result layers (Add a doc step)
Incident Density
- Raster output does not display
Incidents by LOC
- Not receiving expected results
Expected:
Received:
FYI
Issue Analytics
- State:
- Created 6 years ago
- Comments:22 (22 by maintainers)
Top Results From Across the Web
Error: ArcGIS Server Site is not configured. Code: 500
Code: 500. Error Message. When accessing a REST endpoint, the following error message may be returned: "Error: ArcGIS Server Site is not configured....
Read more >Common problems and solutions—Portal for ArcGIS
Questions or issues that you may encounter when working with ArcGIS Enterprise portals as well as possible solutions are listed below.
Read more >ArcGIS Online Reader/Writer Error: Code 503 - FME Community
We've been having issues with our organization's ArcGIS Online portal for the last couple of days (layers being randomly dropped from maps, apps...
Read more >upgrade from Entprise 10.8.1 to 10.9, ArcGIS Server failing to ...
lachlanwainwright opened this issue on May 11, 2021 · 2 comments ... The log for DataStoreUpgradeInstall has the following:.
Read more >Get 500 internal server error when calling an arcgis rest ...
This is a debugging and analysis problem and likely one of a number of possible problems. · Thanks for the replay. · Look...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@BobBooth I was just talking to @mfunk and it looks like the way we fix the symbology for Incidents by LOC is by changing the symbology classification in our sample layer file from manual to some other class breaks (preferably natural breaks)
@BobBooth So I modified the Count Incidents by LOC and also ran the tool you sent me. The output match each other, but still don’t match the original sample layer. So in this screenshot there are three coincident line features, so visually it will be hard to tell the difference so I labelled on FREQUENCY field where
On the road to the far left there is the greatest difference where the original counted 11 incidents and the modifications counted 35.
This is also showing another hidden bug that we haven’t found before. Notice that there are a bunch of floating 78’s in the middle but no road? Weird huh? The road does exist there, but our output symbology classification’s max break is at 76… effectively excluding anything that is a FREQUENCY of 77 or higher. While you can’t see it on this screenshot the actual FREQUENCY maximum is 85. So we are not displaying several roads that have VERY HIGH incident counts.
So I think we are back to removing the AOI from Count Incident By LOC.