Python error on **line 809**, **179** and **335*

[Hussain Ali]

Dear Gallo,

I am trying to run a pinchpoint  and centerality analysis. I have a core file as (Shapefile) in "WGS_1984_UTM_Zone_43N" and resistance layer with 0 to 108 values and the layer is in "GCS_WGS_1984".

I am using "Linkage Mapper 2.0.0, toolbox in Arc GIS 10.7.1" on windows 10 (64bits). 

I am getting the following errors, the details of run are:

....................................................................................................................................................

Executing: MapLinkages C:\Linkage\Out C:\Linkage\MD_Distribution.shp Code C:\Linkage\nathfi.asc true true "Cost-Weighted & Euclidean" C:\Linkage\MD_Distribution.shp_dists.txt true true false 4 Cost-Weighted true true true 200000 # # # # #

Start Time: Sun Aug 22 09:46:16 2021

Running script MapLinkages...

---------------------------------

A record of run settings and messages can be found in your log directory:

C:\Linkage\Out\run_history\log

---------------------------------

********************************************************

NOTE: Linkage Mapper tools often work best when run  from ArcCatalog instead of ArcMap.

Linkage Mapper Version 2.0.0

on ArcGIS Desktop 10.7.1 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:\Linkage\Out\datapass\adj

Calculating cost-weighted distance adjacency

Starting cost-weighted distance allocation...

Processing cell size: 846.132455118555

Building output statistics and pyramids for CWD raster.

Cost-weighted distance allocation done.

That took 4 seconds.

Calculating adjacencies crossing allocation boundaries...

That took 4 seconds.

---------------------------------

Calculating Euclidean adjacency

Starting Euclidean adjacency processing...

Euclidean distance allocation done.

That took 1 seconds.

Calculating adjacencies crossing allocation boundaries...

That took 4 seconds.

---------------------------------

Running script s2_buildNetwork.py

Core area distance list loaded.

number of pairwise distances = 64

---------------------------------

Removed 0 duplicate core pairs in Euclidean distance table.

After removing duplicates and distances that exceed maximum,

there are 64 pairwise distances.  Max core ID number is 24.

Cost-weighted adjacency file loaded.

Creating link table

 

Keeping all adjacent links

 

Checking for corridors that are too long to map.

Writing C:\Linkage\Out\datapass\linkTable_s2.csv

There are 64 links in the table.

This includes 64 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:\Linkage\Out\datapass\linkTable_s2.csv

There are 64 links in the table.

This includes 64 potential corridor links.

Number of core areas to connect: 24

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 6 7]

---------------------------------

Geoprocessing error on **line 809** of lm_util.py in Linkage Mapper Version 2.0.0:

---------------------------------

ERROR 999999: Error executing function.

Failed to execute (RasterToPolyline).

---------------------------------

********************************************************

NOTE: Linkage Mapper tools often work best when run  from ArcCatalog instead of ArcMap.

---------------------------------

---------------------------------

Python error on **line 809** of s3_calcCwds.py in Linkage Mapper Version 2.0.0:

SystemExit: 1

---------------------------------

****Failed in step 3. Details follow.****

---------------------------------

Python error on **line 335** of s3_calcCwds.py in Linkage Mapper Version 2.0.0:

SystemExit: 1

---------------------------------

Python error on **line 179** of lm_master.py in Linkage Mapper Version 2.0.0:

SystemExit: 1

---------------------------------

A record of run settings and messages can be found in your log directory:

C:\Linkage\Out\run_history\log

---------------------------------

Completed script MapLinkages...

Failed to execute (MapLinkages).

Failed at Sun Aug 22 09:46:40 2021 (Elapsed Time: 23.63 seconds)

 

[Venkanna Babu Guthula]

Dear Hussain Ali,

I think the error occurring due to the coordinate system of core shapefile and resistance files are not the same. Both the files should have the same projection or at least the same extent. So change your resistance file coordinate system to "WGS_1984_UTM_Zone_43N" projection and try again. Also, check the extent of both files after projecting the resistance file.

This error occurred previously due to the extent issue. https://groups.google.com/g/linkage-mapper/c/qyi9fAard70/m/jgVbeevzAgAJ

Regards,

Venkanna.

--
You received this message because you are subscribed to the Google Groups "Linkage Mapper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linkage-mappe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/81b78f25-f56f-4350-9069-6af4fd7c04aen%40googlegroups.com.