vshcherb
commented
5 years ago Indeed OsmAnd doesn't forbid private roads but does put a high penalty. There is also a dialog which warns about private roads need to be accessed on the route. You can fully disable road from navigation by using "Avoid road" feature.
I'm using OsmAnd 3.3.5, on Android.
The issue I'm running into is that if I try to use the navigation and my current position is a private road, offline routing for any of the navigation profiles will get a bit confused and start trying to point me in straight lines off of the current private road. It seems to tend towards routing in a straight line regardless of the bounds of the private road, to take the fastest possible path towards a non-private road.
Allowing private access fixes this, but I would expect it to understand that I mean the current road is fine, just that future private roads other than the destination, or ones required for certain to get to it, aren't desired. Using OSRM does actually give a correct result, just exiting the current location's private road like normal, though I imagine that's due to OSRM's OsmAnd support not really letting you specify not to go on private roads.
I can reproduce it with any private road, but the first one I ran into the issue with is a private road near Grandfather Vista, Boone, NC, USA. The exact coordinates are (36.22731, -81.71786); an example of it failing is trying to ask it to navigate you to Greer Lane (36.22823, -81.72099), directly across the road from it. It should suggest taking a straight line off of the private road, onto the NC 105 Bypass, whereas it should suggest you just follow the private road until you're off of it. Permalink to the navigation, on osm.org