Hello all
We are using Visibility gp tool. Our DSM is 1 meter resolution and we try to calculate visibility for about 25 KM.
We do set the extent.
After about 10 minutes Pro crash. It gets to about 92% of the process.
The Pro.exe takes about 11Gb of memory but the machine have a lot of free memory.
I found this: https://support.esri.com/en-us/bug/when-working-with-large-raster-files-in-arcgis-pro-the-bug-000131...
Does anybody is doing such large Visibility calculations?
Thanks
the help for visibility recommends having a look at
Geodesic Viewshed (Spatial Analyst)—ArcGIS Pro | Documentation
for enhanced performance and control of the inputs and outputs. You could compare approaches and if there is no improvement, reporting on the version of Pro and the options that you specified in the tool might help
What's your input arguments to the tool and what format is the DSM in?
Possibly projection? Something like trying to calculate for 25 decimal degrees if the raster is in WGS84.
Or try Geodesic Viewshed.
I'd be tempted to export a subset 30km square as a tiff and use that as a test to rule out anything.
Hi all
My DSM is in UTM and tiff format.
The observer point is in UTM too.
Since this should run as a gp service on a server with no graphic card I do not think Geodesic Viewshed will do better.
I am thinking about splitting to big tiles, do separate visibility on each tile and then merge the results but did not have the time to test it yet.
Thanks
Is the location of the data a possible issue? i.e. Network Drive registered in the data store that has a slow I/O
There is a lot of data and two servers so the DSM's are on network drive.
I will test it on a local drive two (The servers are virtual). It is not going to be easy to manage it if it helps.