nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD Cost Matrix not finding destinations for multiple origins, despite being within range

Mike_RPC

I'm running a cost analysis for pedestrian accessibility, but I've run into an issue. After running Solve on my OD Cost Matrix Analysis layer, I realized that multiple points could not find a destination, despite being well within my 3960 ft range. As an example below, the two origins (round icons) are only a little over 1000ft away from the nearest destination (square), following the network. The two origins that did connect to that destination, also have a route length of about 900ft; so, it doesn't seem like something weird is going on with how the destination is pathing to the network. Quickly scanning through my data, it looks like there's over 50 origins with similar issues.

Find more posts tagged with

Accepted answers

Melinda Morang

Hello. Are you using a network dataset you created yourself or got from your organization (as opposed to Esri Streetmap Premium or ArcGIS Online service)? If so, the problem is probably with the network dataset. Here are some common problems:

Incorrect connectivity policy. The streets aren't connected at intersections because you're using End Point connectivity, but the street features don't end at intersections. You can fix this by switching to Any Vertex connectivity. Documentation for connectivity: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm
The cost attribute isn't configured correctly. It may not be calculating distance correctly, the units may be wrong, etc. Documentation for cost attributes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/cost-attributes.htm
You could have a restriction attribute preventing travel on that side street where the two disconnected points are located.
You could have some kind of turn restriction preventing travel around that corner

To help you debug the problem, try using the Explore Network tool to click on the street features near the problem area to see how they're connected (or disconnected), what restrictions are applied, and how the cost attributes are being calculated. Documentation for Explore Network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/explore-network.htm

All comments

Melinda Morang

For anyone looking at this issue in the future: The ArcGIS Pro documentation now includes a guide for troubleshooting unexpected network analysis results: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/troubleshoot-network-analysis-problems.htm.

Mike_RPC

The connectivity was the issue! The road in front of the destination had a little nub that extended past the end point for the road that the origins were on. So the network didn't view the roads as connecting. After splitting the road at the vertex and running it again, those are now connecting correctly. Thank you for your help!

Mike_RPC

Thank you for the response! I'm using a network my organization created.

1. I'll have to take a look into this one.

2. The cost attribute appears to be working, as I have several other origins that were able to connect to destinations close to the limit, and the cost total is roughly equal to what I measure by hand.

3. and 4. I have no restrictions set on the analysis layer, so everything should be allowed.

Melinda Morang

Incorrect connectivity policy. The streets aren't connected at intersections because you're using End Point connectivity, but the street features don't end at intersections. You can fix this by switching to Any Vertex connectivity. Documentation for connectivity: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/understanding-connectivity.htm
The cost attribute isn't configured correctly. It may not be calculating distance correctly, the units may be wrong, etc. Documentation for cost attributes: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/cost-attributes.htm
You could have a restriction attribute preventing travel on that side street where the two disconnected points are located.
You could have some kind of turn restriction preventing travel around that corner

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.