Wrongly car navigation routing over path, badly bicycle routing over grass

[SLMapper]

Description

highway=path is clearly not for car navigation, but still is wrongly chosen by Osmand.

highway=track, tracktype=grade5, surface=grass and highway=path, surface=grass is clearly not for bike, but still is wrongly chosen by Osmand, when there ways of better surface around it.

Steps to reproduce

Both appeared in longer route (~30 minute each). Only showing the relevant part here:

• car routing from 48.59359° N, 8.87231° E to 48.59435° N, 8.87470° E
  (routes over https://www.openstreetmap.org/way/551096127)
• bike routing from 48.55116° N, 8.94187° E to 48.55221° N, 8.92684° E
  (routes over https://www.openstreetmap.org/way/938199238)

Actual result

1. Invalid road is chosen
2. Road with poor surface was chosen

Expected result

1. Chosing a valid route
2. Chosing a route with conditions matching the vehicle
   (there is a connection via a tracktype=grade1 and tracktype=grade2, which is a bit longer but much more fitting for a bike)

Your Environment (required)

OsmAnd Version: OsmAnd~ 4.7.10
Android/iOS version: -
Device model: -
Crash-Logs: -

Latest map updates of "Baden-Württemberg". Happens with and without live updates enabled.

[yuriiurshuliak]

The bug was partially reproduced. Initially, I attempted to reproduce the issue by building navigation for a car, where the navigation is built exactly as specified by the user. Following that, I attempted to build navigation for a bicycle, but the method for bicycle navigation is currently different.

Additionally, car navigation on the Web version is constructed differently compared to the app, despite Live updates.

Here are the relevant links for car navigation on OSM and the Web version:
Car navigation on OSM
Car navigation on the Web version

Here are the links for bicycle navigation on OSM and the Web version:
Bicycle navigation on OSM
Bicycle navigation on the Web version

OsmAnd~ 4.8.0#2528m, released: 2024-06-18

[yuriiurshuliak]

The bug has been reproduced. In the app, when using the reset car profile, the navigation wrongly routes through bike paths, even with live updates. On the Web version, the navigation works correctly and takes a detour. However, if you enable the "Short way" option on the Web version, it also incorrectly routes through bike paths, just like the app.

Bicycle navigation is now working correctly.

Here is a link to the web version: Car navigation on the Web version

OsmAnd~ 4.8.0#2568m, released: 2024-06-24

[SLMapper]

Thank you very much for reproducing the issue with car navigation.
I was also able to reproduce the bicycle issue of routing over a highway=path, surface=grass using "short way" on the web version.

[SLMapper]

Another bike example I experience yesterday even without "Short way enabled"

where OsmAnd unexpectedly

• prefers tracks with surface=grass → surface=grass → hw=track without additional information
• over continuing on the good tracks that can be seen below surface=gravel, tracktype=grade2 → surface=gravel, tracktype=grade1

[SLMapper]

Another crazy bike example with "Short way" enabled, where

• OsmAnd routes over a foot=designated, highway=footway, lit=no, surface=asphalt, width=0.8
• instead of taking the roads appropriate for bikes (this is when disabling "Short way" on the website, but on my phone I had to manually put a way point for OsmAnd to go there, despite that I had "short way" disabled)