BRouter car-mode truly hates unpaved roads
Hi. I've been using BRouter with Locus for years, generally no problems. However...
The car-mode profiles, even the "Short' versions, both Locus- and BRouter versions, seem to assign a very high penalty to unpaved roads. In the first attached picture, the obvious "correct" route is the one shown in orange, which is highway=secondary, surface=unpaved in the OSM data as of today. (Here in rural Canada, many roads are unpaved.)
In the second screenshot, the routing is clearly wrong for "short", and might even be considered wrong for "fast". (Unclassfied unpaved vs secondary)
It behaves this way in the BRouter web client as well, all four alternatives, first example. Some of those alternatives go even farther afield, just to avoid that unpaved section.
I've learned to switch to cycle routing (even though I'm driving), which does work as expected (until I meet a trail).
Shouldn't a car-short profile put only a small penalty on "unpaved"? Asking for "short" would imply that I can accept unpaved.
Thank you. :)