Some bicycle routes can have portions which are not accessible.
Potential reasons for this:
- temporary construction work on the ways (sometimes for months),
- local access change without simultaneous update of bicycle route relation
(lack of mapper's knowledge or lack of time to redefine an updated route),
- ...
This commit changes the fastbike profile so that being on a cycle route does
not automatically mean "access granted" for bicycles. The normal access
checkings are used instead.
However, the accesspenalty is set to 15 if the no-access way belongs to such a
route, so that the way is not completely forbidden if there is no other
alternative unavailable.
Some bicycle routes can have portions which are not accessible.
Potential reasons for this:
- temporary construction work on the ways (sometimes for months),
- local access change without simultaneous update of bicycle route relation
(lack of mapper's knowledge or lack of time to redefine an updated route),
- ...
This commit changes the trekking profile so that being on a cycle route does
not automatically mean "access granted" for bicycles. The normal access
checkings are used instead.
However, the accesspenalty is set to 15 if the no-access way belongs to such a
route, so that the way is not completely forbidden if there is no other
alternative unavailable.
Add support for routing over fairways which are used for navigable routes in a body of water
(where waterway=river or waterway=canal are not appropriate).
add "sett" as a paved surface (often nicer for bikes than cobblestone)
otherwise, sett surfaces tend to be avoided in routing, while it is usually smooth
even for thin wheels
If BRouter calculates a route with a cycling or hiking profile,
the `smoothness` tag is included in the response. That enables
a statistical analysis for the calculated route (distribution of
smoothness tags by distance).
See the analysis sidebar at https://brouter.m11n.de/ for an example.
