error on line 763

[amykeis...@gmail.com]

I just upgraded to ArcPro 3.1.2 and so I also upgraded to Linkage mapper 3.1.0

I've tried 5 different runs in different areas of the Build Network and Map Linkages and they all keep stalling out at the same spot. I rebooted and I'm still getting the same error. For a while I thought it was because some of the centroids of my core extend beyond the resistance raster, but I just tried a run where all of the cores are completely covered by the resistance raster and it is still stalling out at the same point:

Starting cost distance calculations. ---------------------------------Target core areas for core area #1600 = [1636 1675]------------------------------------------------------------------Geoprocessing error on **line 763** of s3_calcCwds.py in Linkage Mapper Version 3.1.0:---------------------------------ERROR 010236: Error in building VAT: MtVatBldNew: All cells in grid c:\lma2\scratch\core1600\addras have NODATA value. VAT will not be built.. ERROR 010067: Error in executing grid expression. Failed to execute (GetRasterProperties).

Any ideas on what I'm doing wrong?

[amykeis...@gmail.com]

oh, wait, I think I have one running. I looked through other posts and was reminded the importance of using short names for the inputs. Fingers crossed, I just got one core processed and am hoping the file name for my hubs was just a bit too long.

[amykeis...@gmail.com]

dang, I spoke too soon, I got it to get past line 763 on a small test area, and I thought maybe it was the very short hub name that helped get me over the hump, but when I put in one of the smaller sized areas that I was able to run last year, it stopped at 763 again. 

Starting cost distance calculations. ---------------------------------Target core areas for core area #704 = [722 761 769 807 808 821 844 848 864]------------------------------------------------------------------Geoprocessing error on **line 763** of s3_calcCwds.py in Linkage Mapper Version 3.1.0:---------------------------------ERROR 010236: Error in building VAT: MtVatBldNew: All cells in grid c:\lma1\scratch\core704\addras have NODATA value. VAT will not be built.. ERROR 010067: Error in executing grid expression. Failed to execute (GetRasterProperties).

[amykeis...@gmail.com]

I have 11 different subregions that I normally run my analysis in, and I keep getting stuck o line 763, but sometimes the error is different

Starting cost distance calculations. ---------------------------------Target core areas for core area #1588 = [1634 1661 1666]------------------------------------------------------------------Geoprocessing error on **line 763** of s3_calcCwds.py in Linkage Mapper Version 3.1.0:---------------------------------ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds. Failed to execute (GetRasterProperties).

I'm keeping on trying different things, but so far I've only got past this step once and it was on a very small subset of my smallest subregion. I have a new computer this year and new versions of ArcPro and Linkage Mapper. 

[John Gallo]

Hi Amy,

Congrats on the new computer and great to hear you are doing an analysis update.

I'm heads down right now but should have some time next week to look at lne 763 in the code and get better recommendations.  Or you can in an standard python reader or on the github page.

In the meantime, my initial thoughts:

1) 700 links and 1.3 billion cells will be tough, but you have a souped up machine so that should be fine, and this is the same or similar numbers as last time I think... so that doe snot seem to be it.  especially since it is crashing on the first try at this step...

2) Often times new Esri releases break some aspect of the code. It could be something in the new ArcPro version.  It came out in late May it looks like, and it is possible that you are the first person coming across a configuration that triggers the new bug.  But.. you said it worked with a small test region, so maybe it is only particular size or overlay characteristics that trigger the bug.  Unlikely but possible.  You could roll back to a previous version, or even last year's version to be on the safe side there...

3) given the above, and that it is having a hard time building the attribute table, on some of the error messages but not all, with all cells, c:\lma2\scratch\core1600\addras have NODATA value , maybe there is something with the way your resistance surface and cores (hubs right?) are configured...When you reply, please clarify if you tried it for multiple subregions and it gets stuck in the same spot. And if different errors, please include those log files too.

Thanks,

JOhn

--
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/01cb4d43-8cb8-4259-b9b5-e96a2f0b6e3bn%40googlegroups.com.

--

John A. Gallo, Ph.D.

Project Director

LinkageMapper.org

and

Senior Conservation Scientist

Conservation Biology Institute

[amykeis...@gmail.com]

Thanks John. So far it is is happening on all my subregions. The cores/hubs and resistance rasters seem roughly similar to last year. Same max/min (1/500) value of the resistance raster. I do run this over huge areas, but I've been testing on my smaller subregions to start with and haven't gotten any of my real subregions to get past this point. 

Sometimes I get the generic 99999 error, sometimes the NODATA error.

I'm going to go back to exploring over much smaller areas in my current set up. I may also follow your idea to roll back to ArcPro 2.x and Linkage Mapper 3.0.

[amykeis...@gmail.com]

I have made it past this point in a very small test area. I'm going to let this run finish to see if it does. I hate to have to make even more subregions, but maybe I'll have to. Before I go there, I'm going to test changing the resistance raster. Instead of going from 1-500, I'm going to make it 1-150. That way I can stay in 8 bit instead of going to 16 bit. Maybe that will help me run in my original subregions.

It is just so confusing because I successfully did even larger subregions last year.

[amykeis...@gmail.com]

Oh! Wait a minute! Something went wrong with my code and my resistance raster didn't successfully resample from 30 to 90. I feel like an idiot, this is definitely the problem (at least it is a very obvious problem). 

Sorry, I'm moving way to fast over here this year. We ended up a month behind schedule and I was trying to go to fast.

[John Gallo]

Great!  Nice find. Lets hope that is what it is.  And if you roll back, best to stick with LM 3.1 is my instinct. 

To view this discussion on the web visit https://groups.google.com/d/msgid/linkage-mapper/1bbd1d50-fda4-4b68-befd-0579f7155fbfn%40googlegroups.com.

[Erica Anderson]

Hey everyone! Did this thread ever get solved? I could really use an assist. I am running into the same error but have only 27 features I'm trying to run this analysis between. Below is my log. I don't even know where to begin :( 

Build Network and Map Linkages

=====================
Tool Path

C:\Users\erica\Downloads\linkage_mapper_3_1_0\linkage_mapper_3_1_0\toolbox\Linkage Mapper.tbx\MapLinkages
=====================
Parameters

Project Directory     C:\LinkMap
Core Area Feature Class     Habitat_Hubs
Core Area Field Name     AreaNumber
Resistance Raster     Overlay5
Step 1 - Identify Adjacent Core Areas     true
Step 2 - Construct a Network of Core Areas     true
Network Adjacency Method     Cost-Weighted & Euclidean
Core Area Distances File    
Step 3 - Calculate Cost-Weighted Distances and Least Cost Paths     true
Drop Corridors that Intersect Core Areas     true
Step 4 - Prune Network Using Options Below     false
Option A - Maxium Number of Connected Nearest Neighbors     4
Option B - Nearest Neighbor Measurement Unit     Cost-Weighted
Option C - Connect Neighboring Constellations     true
Step 5 - Calculate, Normalize and Mosaic Corridors     true
Truncate Corridors     true
Truncate Cost-Weighted Distance Threshold     200000
Bounding Circles Buffer Distance    
Maximum Cost-Weighted Corridor Distance    
Maximum Euclidean Corridor Distance    
Output for ModelBuilder Precondition    
Custom Settings File    
=====================
Messages

Start Time: Saturday, April 12, 2025 9:21:14 PM
A record of run settings and messages can be found in your log directory:
C:\LinkMap\run_history\log

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

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:\LinkMap\datapass\adj

Calculating cost-weighted distance adjacency
Starting cost-weighted distance allocation...
Processing cell size: 25

Building output statistics and pyramids for CWD raster.
Cost-weighted distance allocation done.
Task took: 22 minutes and 58 seconds.

Calculating adjacencies crossing allocation boundaries...
Task took: 17 minutes and 28 seconds.

---------------------------------
Calculating Euclidean adjacency
Starting Euclidean adjacency processing...

Euclidean distance allocation done.
Task took: 14 minutes and 22 seconds.

Calculating adjacencies crossing allocation boundaries...
Task took: 21 minutes and 11 seconds.


---------------------------------
Running script s2_buildNetwork.py
Simplifying polygons for core pair distance calculations

Finding distances between cores using Generate Near Table.
There are 67 adjacent core pairs to process.
10 percent done
20 percent done
30 percent done
40 percent done
50 percent done
60 percent done
70 percent done
80 percent done
90 percent done
Task took: 1 minutes and 25 seconds.

Distance file C:\LinkMap\Habitat_Hubs_dists.txt generated.

Core area distance list loaded.
number of pairwise distances = 67

---------------------------------
Removed 0 duplicate core pairs in Euclidean distance table.

After removing duplicates and distances that exceed maximum,
there are 67 pairwise distances.  Max core ID number is 26.
Cost-weighted adjacency file loaded.
Creating link table

Keeping all adjacent links


Checking for corridors that are too long to map.
Writing C:\LinkMap\datapass\linkTable_s2.csv
There are 67 links in the table.
This includes 67 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:\LinkMap\datapass\linkTable_s2.csv
There are 67 links in the table.
This includes 67 potential corridor links.

Number of core areas to connect: 26

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

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

Geoprocessing error on **line 763** of s3_calcCwds.py in Linkage Mapper Version 3.1.0:

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

ERROR 010236: Error in building VAT: MtVatBldNew: All cells in grid c:\linkmap\scratch\core1\addras  have NODATA value. VAT will not be built..

ERROR 010067: Error in executing grid expression.
Failed to execute (GetRasterProperties).

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

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

---------------------------------
A record of run settings and messages can be found in your log directory:
C:\LinkMap\run_history\log
---------------------------------

Failed script Build Network and Map Linkages...
Failed to execute (MapLinkages).
Failed at Saturday, April 12, 2025 11:15:32 PM (Elapsed Time: 1 hours 54 minutes 17 seconds)

[John Gallo]

Hi Erica,

Yes, the problem in that thread was resolved. It was not a bug with linkage mapper but rather a problem with her data inputs.  It looks like that is probably the case here too.

your log says " All cells in grid c:\linkmap\scratch\core1\addras  have NODATA value"

So, something seems off with regards to your core areas surface most likely.  Please run the exercise with the sample data and the end of the user guide.  This will show you how it all should work.  and Look.  And then go from there.

If you reply with another error, please also include the log file.

Good luck!

John

To view this discussion visit https://groups.google.com/d/msgid/linkage-mapper/015f739a-4c57-4459-95bb-e28dbfce1aeen%40googlegroups.com.

[Erica Anderson]

Hey John,

I have to be honest, I am really struggling! I've been trying for a week straight making changes and I still can't figure out what is wrong with my data even based on the demo materials, like you suggested. Is it something we might be able to look over together or I could send it your way to check out? I'm wondering if you might be able to spot what's wrong here faster than I will ever be able. I've attached the most recent log file. Same error code and took nearly double the amount of time to get to.  

All the best,

Erica 

You received this message because you are subscribed to a topic in the Google Groups "Linkage Mapper" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/linkage-mapper/sPAQaDjUU_s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to linkage-mappe...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/linkage-mapper/CAEUWjEsa47-oP31t8p9JJcS%2BtKFum%3Dj4KBjSTcEQZGDFSOuPsQ%40mail.gmail.com.

[John Gallo]

Hi Erica,

I'm inferring that the software was working fine for you with the demo data.  OK, lets move this to a private conversation, and lets try to report out to the community if it seems helpful/

Thanks,

John

To view this discussion visit https://groups.google.com/d/msgid/linkage-mapper/CAMdBeZBmAXxU--G2Xy_eEGBrPg44GHV3%2BsRSkCQ4OigJw4jS4g%40mail.gmail.com.