Working on corridor modeling in Costa Rica and have been getting the same error.
Have tried about 2 dozen times with differing project directories, resistance raster types, etc. Tried in both ArcMap and ArcCatalog. Still no luck. Just rebooted my computer, still nothing.
See dialog below. Anything you see that I need to fix?
Executing: MapLinkages C:\Users\set78542\Desktop\Scratch C:\Users\set78542\Desktop\NASADevelop\TalamancaOsa\Data\CorridorModelingData\NationalParks.shp Core_ID C:\Users\set78542\Desktop\NASADevelop\TalamancaOsa\Data\CorridorModelingData\resist_1 true true "Cost-Weighted & Euclidean" # true true false 4 Cost-Weighted true true true 200000 # # # # #
Start Time: Wed Jul 17 14:42:28 2019
Running script MapLinkages...
---------------------------------
A record of run settings and messages can be found in your log directory:
C:\Users\set78542\Desktop\Scratch\run_history\log
---------------------------------
********************************************************
NOTE: ArcGIS errors are more likely when writing to remote drives or deep file structures. We recommend shallow project directories on local drives, like C:\puma. Errors may also result from conflicts with anti-virus software (known problems with AVG). We have also seen conflicts when writing to synchronized folders like DROPBOX.
Note also that Linkage Mapper tools often work best when run from ArcCatalog instead of ArcMap.
Linkage Mapper Version 2.0.0
on ArcGIS Desktop 10.6 Service Pack N/A
Setting data frame spatial reference to that of core area feature class.
---------------------------------
Starting at step 1.
Making temporary copy of resistance raster for this run.
Making temporary raster of core file for this run.
---------------------------------
Running script s1_getAdjacencies.py
Adjacency files will be written to C:\Users\set78542\Desktop\Scratch\datapass\adj
Calculating cost-weighted distance adjacency
Starting cost-weighted distance allocation...
Processing cell size: 0.003500055116
Building output statistics and pyramids for CWD raster.
Cost-weighted distance allocation done.
That took 15 seconds.
Calculating adjacencies crossing allocation boundaries...
That took 10 seconds.
---------------------------------
Calculating Euclidean adjacency
Starting Euclidean adjacency processing...
Euclidean distance allocation done.
That took 1 seconds.
Calculating adjacencies crossing allocation boundaries...
That took 8 seconds.
---------------------------------
Running script s2_buildNetwork.py
Simplifying polygons for core pair distance calculations
Finding distances between cores using Generate Near Table.
There are 2 adjacent core pairs to process.
50 percent done
That took 0 seconds.
Distance file C:\Users\set78542\Desktop\Scratch\NationalParks.shp_dists.txt generated.
Core area distance list loaded.
number of pairwise distances = 2
---------------------------------
Removed 0 duplicate core pairs in Euclidean distance table.
After removing duplicates and distances that exceed maximum,
there are 2 pairwise distances. Max core ID number is 3.
Cost-weighted adjacency file loaded.
Creating link table
Keeping all adjacent links
Checking for corridors that are too long to map.
Writing C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s2.csv
There are 2 links in the table.
This includes 2 potential corridor links.
Creating shapefiles with linework for links.
Linework shapefiles written.
---------------------------------
Running script s3_calcCwds.py
---------------------------------
NOT using bounding circles in cost distance calculations.
Looking for C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s2.csv
There are 2 links in the table.
This includes 2 potential corridor links.
Number of core areas to connect: 3
Creating cost-weighted distance output folders
...cw
Checking for corridors that are too long to map.
Creating core area raster.
Starting cost distance calculations.
---------------------------------
Target core areas for core area #1 = [2 3]
Done with all calculations for core ID #1. 1 of 3 cores have been processed.
That took 35 seconds.
---------------------------------
Target core areas for core area #2 = [1]
Done with all calculations for core ID #2. 2 of 3 cores have been processed.
That took 7 seconds.
---------------------------------
Target core areas for core area #3 = [1]
Done with all calculations for core ID #3. 3 of 3 cores have been processed.
That took 7 seconds.
Updating C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s3.csv
Creating shapefiles with linework for links...
That took 2 seconds.
Individual cost-weighted distance layers written to "cwd" directory.
C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s3.csv
updated with cost-weighted distances between core areas.
---------------------------------
Running script s5_calcLccs.py
Looking for C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s4.csv
Looking for C:\Users\set78542\Desktop\Scratch\datapass\linkTable_s3.csv
There are 2 links in the table.
This includes 2 potential corridor links.
Creating output folder: C:\Users\set78542\Desktop\Scratch\datapass\nlcc
Normalized least-cost corridors will be written to C:\Users\set78542\Desktop\Scratch\datapass\nlcc\nlc
Normalized and mosaicked corridor for link ID #1 connecting core areas 1 and 2 in 0.83 seconds. 1 out of 2 links have been processed.
Normalized and mosaicked corridor for link ID #2 connecting core areas 1 and 3 in 1.49 seconds. 2 out of 2 links have been processed.
-------------------------------------------------
Failed to execute gp.SingleOutputMapAlgebra_sa(expression, intRaster) on try #1.
The following ArcGIS error is being reported on line line 399 of "c:\program files (x86)\arcgis\desktop10.6\ArcToolbox\Toolboxes\scripts\s5_calcLccs.py":
ERROR 010240: Could not save raster dataset to C:\Users\set78542\Desktop\Scratch\output\corridors.gdb\Scratch_corridors with output format FGDBR.
Failed to execute (SingleOutputMapAlgebra).