zossebart / brouter-mtb

Brouter Mountainbike Profile

brouter-mtb

a Brouter Mountainbike Profile

This profile tries to find routes suitable for mountainbikes. It tries to avoid major roads and focuses on tracks for uphills and paths/tracks for downhills where possible.

There are two major switches to modify the behaviour:

• is_wet
• false: normal behaviour (default)
• true: try to avoid ways which are potentially unpleasant to ride when they are wet (for example ways with grass/earth surface)
• avoid_unpaved (available only prior to v1.1.0)
• true: normal behaviour (default), generate routes for XC/AM
• false: generate harder routes (for example Enduro)

These parameters are configurable from within the Locus UI when used with Locus version 3.19 and up.

CAUTION: Locus ignores the default settings of the parameters when the profile is first configured! This means the avoid_unpaved parameter is set to false, which leads to the creation of harder routes in profile versions prior to v1.1.0! Please enable avoid_unpaved at the first setup if you want the default behaviour! This setting is global for all profiles configured in Locus. This is not a problem with other apps or brouter-web, as they are not aware of these parameters and thus use the default settings. Beginning from v1.1.0, the profile is split into two separate variants (normal/hard), so this is not a problem any more.

Changelog

v1.0.0

• initial version

v1.0.1

• refactor to syntax alternatives (should improve the readability)

v1.0.2

• correction to make Locus parameter switches work again

v1.1.0

• split into normal/hard versions of the profile, removed avoid_unpaved parameter

v1.1.1

• fix for wrong turninstructions bug

v1.1.2

• add profile parameter comments, fix ferry route avoidance

v1.1.3

• add missing turninstructionmode parameters

v1.1.4

• add oruxmaps turninstructionmode parameter

v1.2.0

• avoid oneways on cycleways
• kinematic model parameters for more precise ETA

v1.2.1

• add parameter to switch access on uncertain gates (without access-tags)

brouter-mtb's Issues

LCN support

It would be nice if this profile was able to stick to LCNs. Where I live there is a strong preference for following marked routes.

relation:

network=lcn
route=mtb
type=route

No access at all for vehicle=no. Is it the expected behaviour?

Hello,
consider a sample way tagged like this:

highway=track
tracktype=grade4
vehicle=no

This way is rendered as totally inaccessible due to the access_penalty expression (line 330).
Is this the intended behavior? I think no, as access=private is still allowed (even though penalized).
I have changed this behavior in this commit:
asamm/brouter@82d3cb7
Feedback welcome.
Thanks for your attention. Radim