Comment by technothrasher
15 hours ago
OsmAnd has the annoying quark of suggesting that I drive off my retaining wall, through some woods, and then across some wetlands, in order to get to the road behind my house, rather than directing me down my long driveway to the road a little further away. This is because the driveway is marked as private in the OpenStreetMap data, because it is private. Obviously I know to just go down my driveway, but anybody trying to get directions to my house would be sent to the incorrect road behind it and then just abandoned. I contacted the OsmAnd folks and was told it was an OSM problem. But other apps using OSM data don't have this issue. I gave up with OsmAnd after that.
You might get better results tagging the driveway as `access=destination`.
https://wiki.openstreetmap.org/wiki/Tag:access%3Ddestination
Adding a few avoid road markers might help.
Settings > Driving > Navigation settings > Route parameters > Allow private access
Now you'll be routed through private roads anywhere. It should ignore the private flag if it's directly adjacent to the start or end of a route.
See ndriscoll's answer; but besides that there should at least be a feature to tell your local app that a road in question is not to be considered private for yourself; imagine it telling you to go around a long way instead of cutting through your private driveway road that accesses your parcel from both bottom and top road, when you don't technically have the destination on your parcel (say, going to the neighbors across the bottom street straight from work which has you come by the top street first).
Testing just now, it appears to not route through private roads unless it needs to (e.g. destination is on the private road) when you have that setting on, but it might just heavily down weight it so that if the public route is long enough out of the way, it will use it?