Route error when destination stop is approx. >60metres off network.

[KarinaVitiritti]

Hi all, I have successfully created routes using my network, so I know the network works. But when I place a stop approx. 60 metres off the network, I would still like it to create the route to the closest point on the route, but instead it gives me an error. (ERROR 030212: Solve did not find a solution). If I then move the stop closer to the network it finds a solution. Can someone please advise where it is that I setup the tolerance distance that a stop can be off the network, as it appears I need to increase this.

For my solution I'm happy if it stops at the closest point on the network to the stop, no matter what the distance.

Thanks, Karina

[MelindaMorang]

Hi Karina.

Here is some documentation explaining all about how points get located on the network: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/locating-analysis-inputs.htm.  In particular, the "Settings that affect how inputs are located" is relevant to your question.

However, I suspect that the locate settings aren't actually the cause of the solve failure.  If the point were unlocated, you would see different errors.  They would tell you that the point wasn't located and that at least two valid stops are required for a route.  Instead, your error indicates that no path could be found between the two stops.

The first thing to check is where the stop actually located.  It probably found some other, closer spot on the network to locate.  You can check the stop's SnapX and SnapY fields and use the XY Table to Point tool to map the snapped location and see where it falls on the network.

Assuming the stop located on some other network edge, the next thing to do is to figure out why no path could be found between the two stops.  That's likely an issue with the network dataset; the roads are disconnected somehow.  See this post for some ideas and diagnosis steps.

[KarinaVitiritti]

Thanks Melinda, I have worked it out finally, it has taken much of the day looking at the network data. Thanks for making me aware that it was most likely the network dataset due to the error I received, as this turned my attention to the right area to look.

The issue was that with my network build I had included a few landmarks, but I couldn't work out how to set them up in the properties, so I just left them. I worked out that the error occurs when the stop created by myself, has its closest point being a landmark and not on the path or roads which make up the line network. If the landmark is the closest then it errors, but when I move the point to be closer to a road or path which I have setup correctly it runs fine with no error. So I now need to either workout how to add the landmarks properly into the properties or just remove them for now.

Thanks for your assistance.

[MelindaMorang]

Oh, that makes sense.  So your "landmarks" must have been included in the network as a junction source, and some of them were just sitting there by themselves and not connected to anything.

I'm not sure what you mean by "landmarks," but if you mean landmarks that get used in your turn-by-turn directions, here's the documentation for how to set that up: https://pro.arcgis.com/en/pro-app/latest/help/analysis/networks/setting-directions.htm#GUID-7996C48B....  They should not be included as a junction source but instead as a Landmarks table.