Brouter routing profiles not distinctive enough

Dirk H shared this problem 3 years ago
Not a Problem

it appears that BRouter routing profiles are not distinctive enough. Routes created with "short bicycle" profile make not use of all bicycle capable roads. This only happens when using the "pedestrian"profile. I checked that in my living area and also in comparison to another offline routing app.

Comments (4)

photo
1

Good day Dirk,


from what I understand, you complain on results of track compute over BRouter application. Unfortunately in this case, it is needed to report any problems related to BRouter also to BRouter developers as it has nothing to do with Locus Map application. Thanks for understanding.

photo
1

BRouter uses OSM data, and it's possible the bicycle-capable roads you mention aren't properly marked as such in OSM, eg bicycle=designated, or aren't properly connected to other paths and roads.


I found this problem in my own city, and spent some time fixing it up in OSM. It works better here now. :)

photo
1

Hi, thanks for your answers. I'll try to report the problem to the BRouter development team. To me it looks like the profiles in Brouter are not associated properly to the corresponding range of possible roads.

photo
1

It is not like that. Standard Brouter profiles consider ALL OSM ways,since trunks to hard to see paths in the forests. The only exceptions are ways prohibited for bicycles/pedestrians, like motorways or private ways.

Brouter script-like profiles use penalizing system of costfactors, that cause a way segment to pretend it is longer than it is. The optimal route given by the profile criteria is transformed via costfactors to searching for the shortest way.

If Brouter evaluates a way it is not allowed to ride bicycle there ( or that direction for oneways), it is allowed anyway, but with a pedestrian penalty. A biker pushing the bike 500 m on such a way is counted as if he was riding the way 2.5 km long. One time delays for mounting / dismounting the bicycles are counted with as well.

As mentioned, OSM maps sometimes contains incorrectness, obvious only if high zoomed and/or way attributes are examined e.g. by OSM editors. As result, Brouter can incorrectly think the pass is not allowed, or is disadvantageous, even if it is not if surveyed.

Note that you can easily check standard and custom profiles at Brouter web,

when you can choose the profile from the offer , or to upload custom profile in the form.