Warning about private roads incorrectly displayed for Bicycle (motor_vehicle=private) about osmand

[vshcherb]

Don't see problems on web version https://osmand.net/map?start=49.309610%2C18.117356&end=49.310883%2C18.099890&mode=bicycle#16/49.3090/18.1075

[mdykierek]

It is easily reproducible in the area as a few of these roads are restricted for motor vehicles. Here are my results in the App. Maybe web version is a different piece of routing software:

As a bonus I got several crashes when trying to setup the route with GPS off and switching from car profile (the default) to bicycle when trying to select starting point on map.

exception.log

[DmitryAlexei]

OsmAnd~ 4.5.0#367m, released: 2023-07-10
The same result as in the web version. Private access disabled.

Please check, you may have specified vehicle routing in the navigation settings for the bicycle profile.
https://osmand.net/docs/user/navigation/guidance/navigation-settings#navigation-type

[mdykierek]

I had to change my phone and now it seemed harder to reproduce, so the theory with wrong navigation profile is plausible unlikely - I actually managed to generate exact same result as in my previous comment.

But I nailed it. The routing is "worse" because of elevation data being enabled rather than the private access.

There is definitely is something wrong with the interpretation of "private" access and the dialog notifying about it.

1. Navigation from this way: https://www.openstreetmap.org/way/375793921 to the adjacent way: https://www.openstreetmap.org/way/109177284 causes the "private" access dialog. It is marked private but for motor_vehicle only. The same is true for next segment of cycle route: https://www.openstreetmap.org/way/674286868.

2. The dialog reads "Allow using private roads for this trip?" but it does not seem to care a lot if I answer Yes or No for bicycle.

3. For Android Auto the dialog appears on the phone and waits for input so that the route does not start. Is it possible to display the choices on AA also?

Bottom line is - routing is most probably affected by elevation data not the private access. The "private" road dialog is definitely broken and needs both fixing and improvement (2 and 3).

[DmitryAlexei]

Bicycle routing: OsmAnd reads tag motor_vehicle=private (taginfo) and proposes to grant permission to use such a road.

It is important to note, that
1.destination point should be located on the route tagged with motor_vehicle=private. If the destination point is after the segment with this tag, the routing is built without warnings.
2. When using replace destinationa point there is no warning.
3. When destination point near the road tagged motor_vehicle=private, may be no warning.

1.	2.	1. ok	2. ok

1. OSM, OsmAnd Map
2. OSM, OsmAnd Map

Also tested on https://www.openstreetmap.org/way/51784728 and https://www.openstreetmap.org/way/255036528. Same result, warning appears.