Latest Contributions by SheldonBrown

‎07-31-2014

Thanks, Jay. As I mentioned above, in my actual network dataset I don't include the origins and destinations as junctions per se. It just happened the be the case that in the analysis I was conducting, they were coincident.

‎07-28-2014

Thanks, Tim. Setting the scratch workspace to the temporary directory didn't help. I additionally had to set the other two windows environment variables "TEMP" and "TMP" to the location of the temporary directory. The files go where expected now, and space will no longer be a constraint. Geoprocessing bliss!

‎07-28-2014

Hi all, I'm having some relatively large temporary files created on my primary hard drive during python scripting with arcpy. Their location appears to default to C:\%appdata%\Local\Temp. I need them to be stored in a different location. I came across a couple postings suggesting to set the ARCTMPDIR environment variable to a different directory, and I've done that, but it doesn't seem to help. The temp files are still created on the C drive. Are there any other things I can try? Thanks.

‎07-25-2014

No, I suppose there isn't. I'll try that on the next full run. But still, the origins ‌should ‌snap to the street features. I'll be curious to learn if it's a bona fide bug.

‎07-25-2014

Thanks for looking. Ultimately I'm using your Add GTFS to a Network Dataset tool to calculate travel times between transit stops. So, the "origins" in my case are doing double duty - they get created as, and are part of, the network dataset, and I use them again as origins. I have about 7,500 transit stops in my network. Only about 70 - randomly peppered throughout the network - don't locate when I run the OD Cost Matrix. The rest seem fine.

‎07-25-2014

OK - I've uploaded a FGDB to Dropbox containing a small network dataset with two origins. Here are the steps to reproduce the error: Add network_debug_ND to ArcMap. Create a new OD Cost Matrix layer. In 'Network Locations' uncheck "origins" and make sure "roads_small" is set to shape. Check "Exclude restricted portions of the network." Set search tolerance to 15 meters. Add the "origins" feature class to the Origins network layer. The origin on the right will not locate. Expanding the search tolerance or allowing location on restricted elements will fix the problem. Thanks for any help.

‎07-25-2014

Sure. Let me try to put together something small and reproducible.

‎07-25-2014

Thanks, Melinda. Using the Network Identify tool, there's nothing obvious that pops up that would indicate a restriction on the two network elements that are close by. I see their length, travel time, source feature, and their connectivity to other elements. Everything seems normal. The properties are similar for the links proximate to the unlocated origin and the located origin. I didn't define any restriction attributes for this network dataset. The output of a Route analysis shows that the origin is snapping to junction immediately to the right along the network. The properties of those links are also similar.

‎07-25-2014

Thanks, I've moved it. I'm pretty sure this isn't a connectivity problem. If I use the same pair of origins with the same parameters on a route layer, network analyst successfully locates the stops and finds a route between them.

‎07-25-2014

I'm not sure what you mean by "go the other way." At this point I'm not actually solving the analysis layer, just trying to add origins and destinations. For the same reason, breaks in the network shouldn't be an issue here - I can see that both origins are directly on top of the features I want them to snap to, yet one does and the other doesn't.

‎07-25-2014

Hi all, I noticed some strange behavior when solving a series of OD cost matrices in Network Analyst. The crux of the problem is that some origins and destinations are not being included in the solve. The strange part is that they are already set to be coincident with the network features I'm snapping to, so the search tolerance parameter shouldn't be an issue (I've verified this by running the Near tool, and confirming that NEAR_DISTANCE equals zero). Here's an image of a simplified example with two origin points: After adding the origins to the network with a search tolerance of 15 meters, I get this: The origin on the right is unlocated, despite being (seemingly) identically positioned relative to the relevant network features as the origin on the left. The two ways I've found that I can get the origin on the right to locate are to: Increase the search tolerance arbitrarily. At a tolerance of 500 meters, the origin will locate in the correct spot. Maintain the shorter search tolerance but uncheck "Exclude restriction portions of the network" from the Network Locations tab in the OD Cost Matrix Properties window. (To be clear, the origin will always locate at a search tolerance of 500 meters with our without excluding restricted portions of the network.) Neither of these two things should have any effect. As I've already mentioned, the origin is located on the feature. Additionally, there are no relevant network restrictions (that I'm aware of ... and I built the network). Besides, when it does locate, the origin gets placed in the correct spot, so that particular link can't be restricted. Any ideas for getting to the bottom of this? I'd rather not just take one of the "solutions" above without fully understanding what's going on. Thanks for any help.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by SheldonBrown

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Specifying location of temporary files created during python scripting

Specifying location of temporary files created during python scripting

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Re: Inconsistent behavior in Network Analyst when adding origins

Inconsistent behavior in Network Analyst when adding origins