Latest Contributions by MervynLotter

You should also consider Circuitscape (http://www.circuitscape.org/) for modelling multiple paths (this does work well but be careful of cell size as it takes an inordinate amount of time to run and requires LOTS of RAM). Then if you are using Pro 1.3 and above, or ArcMap 10.5 (possibly 10.4), consider using the new "Cost Connectivity" tool that can connect up multiple patches using corridors and a cost surface. Not sure of the limits. See https://pro.arcgis.com/en/pro-app/tool-reference/spatial-analyst/cost-connectivity.htm ... View more

I would start by making a copy of your input feature layer and work with the copy. The tool I propose in your first step, Integrate, changes the geometry of your input file. So be careful. So open Integrate, and set the distance at which you would like to summarise your points i.e. your input distance will be 100 m. After running this tool, all your accident incidents within 100 m of one another will have the same geometery. Next run a Spatial Join on your input layer, using the same layer for both your Target Features and Join Features inputs. The join operation should be one to one. The resulting output will contain a field called Join_Count. This field will contain the number of points (accidents) occurring at each point on the map. ... View more

For me this error is frequently resolved when if I select to save to a geodatabase, but as Dan points out, there could be many reasons. ... View more

Thanks Dan, I agree. I took a look at this site before writing through GeoNet but I did not find any similar add-ins or scripts. ... View more

Hi Dan There was a street view add-in for Pro 1.1 that I used for a while, but this add-in is no longer compatible with the newer versions of Pro. For the life of me I cannot recall where I got this add-in from!  If I now try and run the add-in, the resulting error message seems to be written in Italian (based on Google Translate). The add-in was called PAMStreetView and there are no contact details with the associated files.  The ReadMe.txt file contains the following text: Double click on PAMStreetView.esriAddInX file for install. Note: Street View requires WGS84 so add-in projects from your coordinate system current of Map to wgs84 (for now only coordinate system based on a datum wgs84) Tested with ArcGIS Pro 1.1.1 For a bug of ArcGIS Pro 1.1.1 I use a rest service for projection in wgs84. In arcgis pro 1.2 I will use arcgis pro api Version 1.0: initial version So not to worry about this any further. I am hoping that there may be other Pro users out there that are aware of this add-in, or other similar 3rd party add-ins, that may be of assistance.  ... View more

In 2012 (I cant recall which version of ArcMap, probably 10.1), I ran a Viewshed analysis on about 300 000 buildings and the process took 33 days to complete (805 hours)!  So it is possible, it just computationally intensive. Last year I ran a Visibility analysis on 17 716 points (as Input Points) and the process took just under a week to complete. Both of these analysis used the 90m DEM as input.  So I would think you need to reduce your number of inputs so best to subsample as Darren suggested. There is a geoprocessing tool called Generate points along line that you can use to create points every 100 m or so. It may be a good idea to use topography to inform the distance values for certain areas (more hilly, more points) but the trade-off would be that it then complicates the number of times a cell is visible (if that is of importance). ... View more

You can search using the *Locate *tool, and just add the list of layers (shapefiles or features) to search under Settings. Not quite as simple as ArcMap but I really like the search output. ... View more

If the source data is in point format, you could use the Extract Values to Points  tool to add the elevation value from your raster to your point dataset. Then simply add a column and use the calculator to subtract the two values. This would introduce less 'noise' through interpolation, particularly relevant if it may trigger an investigation. ... View more

Thanks George  ... View more

Have you tried the Feature Compare tool? Under Compare Type, you can select to compare geometry, attributes, etc., or just select all. I have used it to compare two large wetland datasets but admittedly I was not concerned about the attributes at the time.   ... View more

Have you seen this workflow for identifying highest (and lowest) points within a polygon using a DEM? Do see How To: Create points representing the highest or lowest elevations within polygon features  In step 1E, for "Statistics type", select "All", then you can choose which values you want to use in the workflow (min, max).  Summary "Using a Digital Elevation Model (DEM) raster and the Spatial Analyst extension, the location of the highest or lowest elevation can be identified for polygon features of interest. This procedure describes a basic workflow that generates a point feature class of the highest point within each polygon feature. In this example, highest elevations are used, but method this also works for lowest elevations." ... View more

I am sure there are other approaches that would work but the one I would try would be to create a new polygon feature class and then summarize your elevation values from your 3D polygon into this new polygon feature class. So you could start by creating a new polygon feature like a grid using the Create Fishnet tool, using your 3D polygon file as the Template Extent.  You will have to play around with size or number of columns to get the desired grid of approximately 10k polygons.   Then use the Summarize Within tool to summarize your elevation values into the new polygon file that you had created. Under Summary Fields, select your elevation field under Field and then Mean under Statistic.  I am not sure how long it woudl take to run on such a large polygon of yours, or whether it is even possible. I have never attempted something as large as this before.  ... View more