solutions-geoprocessing-toolbox: Issues after testing #500 in ArcMap

@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

• Original sample data is in RED.
• Matt’s modified tool output is in PURPLE
• Bob’s modified tool output is in BLACK

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.

I’ve verified that the various components of this issue have been resolved. Closing out.

@joebayles - I think the “Incident Density - Raster output does not display” issue is dependent on whether or not you have the Spatial Analyst extension checked on. I tried it and saw the same, but the output included the message:

• Could not create output raster layer; make sure that your Spatial Analyst extension has been checked out. Checked SA on (it was not enabled), re-ran the tool, got the raster layer added.