Reach not completing due to number of points?

[Patrick McGrath]

Hello,

I'm getting a strange error with the UNA tool. First...

 

UNA Toolbox: May 2013 Release

Desktop 10.0 Service Pack 3

Network dataset built with a restriction (non-traversable links)

 

I'm able to successfully execute Reach using subsets of point feature classes as the input, but not the full point feature classes. These are not big feature classes--one represents 1835 parcels within a neighborhood ("North Redmond"), another about 600 parcels ("Downtown"). So for example, when I run all 1835 parcels within North Redmond, the tool fails.

 

Messages

Executing: Centrality NRParcels false TFP_ND true false false false false FID # Length 200 "On the network" 1 # C:\temp\nrtest2 1835 #

Start Time: Tue Dec 31 13:36:11 2013

Running script Centrality...

[started] Copying input buildings

[finished]

[1 started] Computing adjacency list

Adjacency list already computed on previous run

[1 finished]

[2 started] Building graph from adjacency list

[2 finished]

[3 started] Retrieving necessary node attributes

57 out of 1835 input points not recorded in graph

[3 finished]

[4 started] Running centrality computation

[4 failed]

Not successful

Completed script Centrality...

Succeeded at Tue Dec 31 13:36:47 2013 (Elapsed Time: 36.00 seconds)

 

 

However if I select 1778 or fewer parcels out of the feature class and re-run the tool (into the same directory), Centrality completes. I arrived at the number 1778 through a lot of troubleshooting. 1778 or fewer works, 1779 does not, regardless of where that one additional point feature is spatially located (I tried many to control for problems in the network or the point features, so I don't think this is an issue with geometry). The same thing happens with my Downtown parcels. The full set of 600 or so will not complete, but when I selected 300 points at random, it did complete. Any idea what's going on here?

 

Thank you very much,

Patrick

 

 

[Patrick McGrath]

I've done some more investigation and think I've found the source of the problem. When I rebuild my network dataset without the restriction attribute, Centrality will complete for the full neighborhoods. This is a new problem, since I've had success in the past using a restriction in the network dataset. I'm very interested to hear how this problem might be solved.