osmandapp/OsmAnd

Triangular adjustment of bike routing parameters

Opened this issue ยท 1 comments

xeruf commented

๐Ÿž routing report

Routing engine

OsmAnd's in-app offline routing

Routing Profile

bike

Problem

As outlined in #12018 and surely quite a few other issues, it is sometimes hard to adjust routing parameters so the result is pleasurable. I myself recently used the "Use elevation data" setting, and was happy with neither route, as the routing tends to be quite extreme if it is enabled.

Solution

Generally, routing should prefer official bike routes if they fit the route as they are more likely to be appropriate.

What I envision is a routing parameter triangle, where one can select a preference dynamically according to three parameters:

  • Comfort (prefer bike routes and even paths)
  • Trail (prefer unpaved)
  • Speed (prefer shorter, paved ways)

Comfort โ€”โ€”โ€”โ€” Trail
โ€‡โ€‡โ€‡โ€‡โ€‡\โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡/
โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡\โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡/
โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡\โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡/
โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡โ€‡Speed

In that triangle, one can place a dot at any point to adjust the parameters of the route calculation algorithm.

The default should err on the side of Comfort and a bit of Speed, resulting in an order of preference similar to this:
Official bike routes > Bike lanes/trails > Paved non-roads > Roads > Unpaved trails

I agree that bicycle routing in OsmAnd is still very suboptimal.

I also suggested to have a stronger preference on cycleways and cycle routes in #12023 (comment) and #12018 (comment). I guess this would also fix #10191.