This object is in archive! 
Force to navigate over cycle routes
Answered
Hello,
is it possible to tell Locus + Brouter to navigate preferably over (made) bicycle routes?
With best regards,
Alex
Hello,
is it possible to tell Locus + Brouter to navigate preferably over (made) bicycle routes?
With best regards,
Alex
Good day Alex,
as I know, in BRouter is possible almost everything. I highly depend on how deep you wants dig.
Good starting point is to check very nice repository of custom BRouter profiles made by one very active user Libor, repository is here: https://github.com/poutnikl/Brouter-profiles/wiki/Brouter-profiles-collection .
Feel free to ask if something won't be clear.
Good day Alex,
as I know, in BRouter is possible almost everything. I highly depend on how deep you wants dig.
Good starting point is to check very nice repository of custom BRouter profiles made by one very active user Libor, repository is here: https://github.com/poutnikl/Brouter-profiles/wiki/Brouter-profiles-collection .
Feel free to ask if something won't be clear.
Hi Alex,
There are basically 2 major options:
OPTION 1 - BRouter standard profile Trekking
you may want tostay with the BRouter standard profile Trekking. It already has a mild cycleroute preference.If you want to have the preference stronger,change in the the profile ( it is a plain text file )
"assign stick_to_cycleroutes = false"
to
"assign stick_to_cycleroutes = true"
But both the default and the tweaked behaviour of the Trekking profile has a drawback : It evaluates all cycleroutes as perfect ways, with no distinguishing between cycleroutes of great and horrible surface quality. And, even horrible cycleroute is considered beter than the best way that is not a cycleroute.
OPTION 2 - My custom trekking profile
https://github.com/poutnikl/Brouter-profiles
My trekking profiles, while able to tune the strength of cycleroute preference, still maintain distinguishing good and bad ones,and good non-cycleroutes can taken as better than bad cycleroute ( depends on preference value ). Aside of that, default settings uses extra preference for long distance cycleroute, as those from international or national cycleroute networks ( ICN, NCN ).
The standard Poutnik-dry.brf uses mild preference of cycleroute, with the FCR suffix (Follow-CycleRoute) strong preference. The suffix SameCR gives the extra preference of long distance cycleroutes to the local and regional cycleroutes as well.
If sorted by the stregth of these 2 combined efects, it is probably like
Poutnik-dry < Trekking-CRsame < Trekking-FCR-dry < Trekking-FCR-CRsame.brf
Aside of that, you can, if you want, manually tune the preference stregth by parameter "assign cycleroutes_pref".
Default value in the Trekking-dry profile is 0.2,
FCR uses 0.6,
ignoring cycleroutes ( ICR) uses 0.0,
you can go up to 1.0.
You may want to download the profiles archived as the ZIP archive https://github.com/poutnikl/Brouter-profiles/raw/master/BR-Bike-Profiles.zip With a short generated description https://raw.githubusercontent.com/poutnikl/Brouter-profiles/master/Bike-Profiles-List-Legend.txt
( I have listed below just the relevant profiles - all have also their wet variants )
Unzip the archive and place the chosen profiles into Android folder
<device dependent path to Brouter data>/Brouter/profiles2/
Profile name, Profile description ( generated )
Poutnik-dry.brf, Standard Trekking profile by Poutnik, for dry weather
Trekking-FCR-dry.brf, Trekking profile sticking to cycleroutes
Trekking-CRsame.brf, Trekking profile increasing preference of local routes, evaluating them as long distance routes
Trekking-FCR-CRsame.brf, Trekking profile sticking to cycleroutes, increasing preference of local routes, evaluating them as long distance routes
Hi Alex,
There are basically 2 major options:
OPTION 1 - BRouter standard profile Trekking
you may want tostay with the BRouter standard profile Trekking. It already has a mild cycleroute preference.If you want to have the preference stronger,change in the the profile ( it is a plain text file )
"assign stick_to_cycleroutes = false"
to
"assign stick_to_cycleroutes = true"
But both the default and the tweaked behaviour of the Trekking profile has a drawback : It evaluates all cycleroutes as perfect ways, with no distinguishing between cycleroutes of great and horrible surface quality. And, even horrible cycleroute is considered beter than the best way that is not a cycleroute.
OPTION 2 - My custom trekking profile
https://github.com/poutnikl/Brouter-profiles
My trekking profiles, while able to tune the strength of cycleroute preference, still maintain distinguishing good and bad ones,and good non-cycleroutes can taken as better than bad cycleroute ( depends on preference value ). Aside of that, default settings uses extra preference for long distance cycleroute, as those from international or national cycleroute networks ( ICN, NCN ).
The standard Poutnik-dry.brf uses mild preference of cycleroute, with the FCR suffix (Follow-CycleRoute) strong preference. The suffix SameCR gives the extra preference of long distance cycleroutes to the local and regional cycleroutes as well.
If sorted by the stregth of these 2 combined efects, it is probably like
Poutnik-dry < Trekking-CRsame < Trekking-FCR-dry < Trekking-FCR-CRsame.brf
Aside of that, you can, if you want, manually tune the preference stregth by parameter "assign cycleroutes_pref".
Default value in the Trekking-dry profile is 0.2,
FCR uses 0.6,
ignoring cycleroutes ( ICR) uses 0.0,
you can go up to 1.0.
You may want to download the profiles archived as the ZIP archive https://github.com/poutnikl/Brouter-profiles/raw/master/BR-Bike-Profiles.zip With a short generated description https://raw.githubusercontent.com/poutnikl/Brouter-profiles/master/Bike-Profiles-List-Legend.txt
( I have listed below just the relevant profiles - all have also their wet variants )
Unzip the archive and place the chosen profiles into Android folder
<device dependent path to Brouter data>/Brouter/profiles2/
Profile name, Profile description ( generated )
Poutnik-dry.brf, Standard Trekking profile by Poutnik, for dry weather
Trekking-FCR-dry.brf, Trekking profile sticking to cycleroutes
Trekking-CRsame.brf, Trekking profile increasing preference of local routes, evaluating them as long distance routes
Trekking-FCR-CRsame.brf, Trekking profile sticking to cycleroutes, increasing preference of local routes, evaluating them as long distance routes
Replies have been locked on this page!