-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brouter-profile for touring cyclists with luggage -> long-distance travel #22
Comments
I would take rather the develop branch of the template. Here is the link to generated package of profiles derived from template from develop branch. Use hills=2, that sets a velomobile-like baseline hillcost settings ( 1.0/80 up, 0.5/80 down. This avoids hills a lot. Avoiding of incline above a threshold is problematic, as it may lead to unwanted side effects. You may play with profile internal intermediate parameter uphillcostvalue to set it to 3.0, what kind of prefer milder slopes. To have incline threshold, there would be needed some dirty tricks. For downhill, the 0.5/80 cutoff)cost of hills=2 would stay. For uphill, a trick would be to have stepwise cost system with high uphillcutoff(value), probably low uphilcost(value) and very high uphillcostfactor and elevationbuffer reduce factor ( see Glossary ), but such profile is not ready yet. develop version uses cycleroute_pref even above 1.0 LCR is reasonable preferring international and national cycle routes, while the 2 profiles below becomes extreme to rather avoid other roads and in ICN case any road but international routes, giving them quite high cost. later added I use a Linux (Android+termux) script sedbatch generating profiles locally on the device from local or GitHub templates. ( The link leadss to not the latest version ) The parameter substitution easily read bfron the script text even if you are not familiar with coding ) Additionally you can tweak road preferences with MTB factor, smallpaved_factor ( see wiki Glossary ) For long distance Eurovelo routing, I would use Trekking-ICN-hills2 profile, |
See also Determining-optimal-bicycle-profile where is a link to highle experimental development branch, implementing hill=6 as Not Too Steep attempt, highly configurable by about 6 parameters, must be played with. |
Such a profile would/should also prioritize main roads when possible (possibly avoiding traffic constraints). It's especially important when map data is not (yet?) precise with regards to paving, access constraints, etc. Current case in mind: routing in Mexico & Colombia, where the main grid is on OSM, but too often imprecise. We're resorting to use |
@OdyX There would be then need for separate profiles, as in the West/Central Europe theatre of bicycle travelling, one usually avoids main roads ( at least from secondaries up, often even from tertiaries) as devil the cross. Probably topic for implementing a new flag: |
Let me just suggest a wording a little less condescending such as |
Well, For Brouter and it's profiles, there is no reality but the one that is mapped in Openstreetmaps. And only just part of that. Any profile may be forced to use just main roads as they may be the only ones mapped. True, Brouter web frontend or some Brouter aware apps like LocusMap offer to use offroad routing. But that is based on linear point2point route segment creation and has nothing to do with profile based routing. |
It seems in the region I'm in currently, I can get more or less what I want with these patches to
|
Hi poutnikl.
your BRouter profile are great! I use e.g. the MTB profile for my MTB tours.
However, I miss a profile for touring cyclists (with luggage) -> long-distance travel:
if possible on bike paths (all variants)
if possible without car traffic, or little car traffic,, e.g. at least on track type grade3 (grade4?),
avoiding strong gradients (for example > 13%) ...
Does this already exist?
I found your instructions to create it myself - but I'm not sure if I can do it optimally.
-> Release version - or Development/Beta version
The text was updated successfully, but these errors were encountered: