This object is in archive! 

Force to navigate over cycle routes

Alex Müller shared this question 7 years ago
Answered

Hello,

is it possible to tell Locus + Brouter to navigate preferably over (made) bicycle routes?


With best regards,

Alex

Replies (2)

photo
1

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.

photo
2

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

photo
1

Libor, you are blessing for every developer. Thank you for exhausting answer. I'll have to once order Michal to create some summary for all users and place it into our manual :).

photo
2

It was pleasure. I will gradually refine my Github BRouter wiki pages, so feel free to refer them in the Manual pages. You can copy content as well, but links would grant uptodate info.

I guess I am better in writing profoles than documenting them. I need an assistent :-)


BTW, Be nice to the employees and just kindly ask... :-)

photo
1

@Alex: Just addition> You may found very handy to plan your routes and experiment with the profiles on Web BRouter front-end

http://brouter.de/brouter-web/

where you can upload the profile text content to the bottom left text input field of the page.

photo
1

Hi Libor,


thank you so much! It was quite easy to upload your .brf-Data to http://brouter.de/brouter-web/

I opened one of the files with nodepad and copied the text to the left of BRouter and clicked on upload.

I think it worked. Was this the correct procedure?


Now, I would like to activate your trekking profiles to my phone.

Therefore, I copy the files to the directories of brouter into the folder "profiles2".

I click on BRouter, then on "BRouter App" and choose your profile.

Now, Brouter asks me to select "Select form" or "Server-Mode".

If I click on "Server-Mode", there are two out of six boxes checked.

With clicking on "Ok", BRouter tells me, that the import of the new profile has been successful.

Did I import your profile correctly or did I miss something?

photo
1

For the BBRouter-web, yes, the procedure is correct.


For profile acrtivation - nothing special is needed, jost copying them to Brouter/profiles2 folder. Then you can work with them exactly as with standard BRouter profiles.


You can use the profiles directly in Brouter, generating GPX track with using of Locus waypoint.

Or, you can map them.


Try this unfinished, but already useful wikipage :

https://github.com/poutnikl/Brouter-profiles/wiki/Using-Brouter-profiles-for-Locus-navigation

photo
1

Your profile to mode assigning procedure is fine. But be aware if you left both trasportation modes in BRouter checked in, the profile will be mapped to both of them, what you may do not want.

photo
1

Hi Libor,


now, I am able to work with your profiles! ;-D


Which profile would you take for a cycling tour in foreign countries?


With best regards,

Alex

photo
1

For general usage, Trekking-dry or standard Trekking,

for stronger marked route preference Trekking-FCR, or Trekking with

  1. assign stick_to_cycleroute 1

For more, see https://github.com/poutnikl/Brouter-profiles/wiki/Choosing-bicycle-profile

Replies have been locked on this page!