MTB profile links

232 views
Skip to first unread message

Poutnik

unread,
Feb 24, 2016, 12:50:28 AM2/24/16
to OSM Android bikerouting
This may be targeted to Volker, Zossebart and other MTB profile authors.

Are there available links to true MTB profiles,
that I could refer and recommend to friends ?

As not being a MTBiker,
my profiles offer just some profile bending and extrapolation toward MTB,
so true MTB profiles can be better.

Poutnik ( The Pilgrim, der Wanderer )

Zossebart

unread,
Feb 24, 2016, 9:27:02 AM2/24/16
to OSM Android bikerouting
Hi,

My attempt to a MTB-profile can be found here: https://groups.google.com/d/msg/osm-android-bikerouting/ACQWNUsEsEM/A3H-6UAxWW4J
I thought this would be the official place to post profiles, but now I think nobody is looking there...

I'm not shure if it's recommendable, but maybe it's worth a try.

I extended and refined it since I posted it there more than a year ago and plan to release the new version soon (maybe even on github).
There are also some guys from IBC forum who have tried it recently, but I don't have got much feedback yet.

Poutnik

unread,
Feb 24, 2016, 10:13:05 AM2/24/16
to OSM Android bikerouting
Ahh, I see. I forgot about this thread  and Google search did not remind it to me for some reason.
I will offer it for the try.

My profiles are here :  https://github.com/poutnikl/Brouter-profiles
with wiki https://github.com/poutnikl/Brouter-profiles/wiki
respectively development version of my profile template here : https://github.com/poutnikl/Trekking-Poutnik


Dne středa 24. února 2016 15:27:02 UTC+1 Zossebart napsal(a):

Poutnik

unread,
Feb 26, 2016, 2:34:53 AM2/26/16
to OSM Android bikerouting
Dne 24/02/2016 v 15:27 'Zossebart' via OSM Android bikerouting napsal(a):


My attempt to a MTB-profile can be found here: https://groups.google.com/d/msg/osm-android-bikerouting/ACQWNUsEsEM/A3H-6UAxWW4J
I thought this would be the official place to post profiles, but now I think nobody is looking there...

I'm not shure if it's recommendable, but maybe it's worth a try.

I extended and refined it since I posted it there more than a year ago and plan to release the new version soon (maybe even on github).
There are also some guys from IBC forum who have tried it recently, but I don't have got much feedback yet.
--
You received this message because you are subscribed to the Google Groups "OSM Android bikerouting" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osm-android-biker...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I got feedback it is quite good in Beskydy mountains ( tops at 13xx m ),
probably by comparing suggested routes with the user experience.
http://brouter.de/brouter-web/#zoom=11&lat=49.5412&lon=18.1985&layer=OpenCycleMap%20(Thunderf.)

For non mountain just hilly areas
the user would appreciate some Highlands version,
without up/downhill limitations of track grade5 or path,
rather lightly preferring them.


Poutnik

unread,
Feb 26, 2016, 8:39:07 AM2/26/16
to OSM Android bikerouting
The user recently stated
he is for now the most satisfied with my development version of Trekking-Poutnik profile template

https://raw.githubusercontent.com/poutnikl/Trekking-Poutnik/psmallpaved_factor/Trekking-Poutnik.brf

He uses its parameters tuned to
MTB_factor  2.0 and smallpaved_factor -0.5 for MTB profile
MTB_factor  1.0 and smallpaved_factor -0.3 for MTB profile light , good for a tired biker, aiming home

assign   MTB_factor           0.0 # default 0.0, see ****), see also https://github.com/poutnikl/Brouter-profiles/wiki/Trekking-MTB-Profiles---legend
assign   smallpaved_factor    0.0 # default 0.0, if <> 0.0 then it penalizes/promotes mainroads and unpaved roads for positive/negative values.

Dne pátek 26. února 2016 8:34:53 UTC+1 Poutnik napsal(a):

Zossebart

unread,
Mar 1, 2016, 10:40:01 AM3/1/16
to OSM Android bikerouting
Thanks for the feedback!

I must admit, I haven't found the time yet to test your profiles, but I hope to find time to do it soon...

Poutnik

unread,
Mar 3, 2016, 2:46:25 AM3/3/16
to OSM Android bikerouting, Zossebart
In such a case, you may want to separate hillcosts from MTB factor,  keeping them independent,
as  current implementation  progressively turns  them down with raising up MTB_Factor.

The original idea of pushing a trekking profile toward MTB was
to prefer MTB-like ways more  and to avoid hills less at the same time.

-- 
Poutnik ( the Pilgrim, Der Wanderer )

My Brouter profiles 
https://github.com/poutnikl/Brouter-profiles/wiki

Dne 01/03/2016 v 16:40 'Zossebart' via OSM Android bikerouting napsal(a):

Norbert Kress

unread,
Jul 10, 2017, 12:17:28 PM7/10/17
to OSM Android bikerouting
Hi,
I've found your profiles for MTB - which were recommended bei Putnik. But both profiles - Puntniks and yours (Zossebart Hard) - do a routing in the valley and not over the hill, which I don't understand.
The same behavior was on GPSies, while using GraphHopper.
I was MTB'ing over the weekend in Sauerland and one of our trips had been from Brilon to Willingen over the hills. One of our guys had used a Garmin and that founds a track over the hill.

Any idea about that?

Thanks in advance and regards,
Norbert

Poutnik

unread,
Jul 10, 2017, 12:56:30 PM7/10/17
to osm-android...@googlegroups.com
If you want to "release the dragons", you can. On user demands, I have
created few months ago 2 profiles with all the evil unleashed. Usual MTB
profiles are rather like profiles for a grandmothers. :-)

Trekking-No-Flat.brf, Trekking in No-Flat mode, giving penalty to flat
roads, with zero hillcost.
Trekking-hilly-paths.brf, Trekking in Hilly paths mode, Very strong
preference of unpaved hilly paths

Each of them was taylored from different point of view, but they are
about comparable. They can find for you the total hill ascend several
times higher than usually. If they kill you, I do not accept any
responsibility. :-)

See the discussion about them in the gitHub issue Profile
Hiking/Trekking near nature
<https://github.com/poutnikl/Brouter-profiles/issues/12> . Some links
there may be outdated, as profiles could be moved to the released
profiles - see the link below.

https://github.com/poutnikl/Brouter-profiles/tree/master/BikeProfiles

BTW, the proper nick is Poutnik, it means ein Wanderer, or a Pilgrim.

Dne 10.7.2017 v 18:17 Norbert Kress napsal(a):
> --
> You received this message because you are subscribed to the Google
> Groups "OSM Android bikerouting" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to osm-android-biker...@googlegroups.com
> <mailto:osm-android-biker...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

--
Poutnik ( The Pilgrim, Der Wanderer )

https://github.com/poutnikl/Brouter-profiles/wiki

Poutnik

unread,
Jul 13, 2017, 9:06:42 AM7/13/17
to osm-android...@googlegroups.com
Just an addition to the previous post...

The below mentioned profiles focus themselves rather on the MTB-like
road quality than on riding up and down. They still use elevation
penalty, even if lowered to road/trekking profiles. OTOH, if some other
routing system ignores elevation, it is more probable it suggests hilly
roads.

2 special profiles that search for such a hilly roads were mentined in
the other post.


Dne 10.7.2017 v 18:17 Norbert Kress napsal(a):
> Hi,
> I've found your profiles for MTB - which were recommended bei Putnik.
> But both profiles - Puntniks and yours (Zossebart Hard) - do a routing
> in the valley and not over the hill, which I don't understand.
> The same behavior was on GPSies, while using GraphHopper.
> I was MTB'ing over the weekend in Sauerland and one of our trips had
> been from Brilon to Willingen over the hills. One of our guys had used
> a Garmin and that founds a track over the hill.
>
> Any idea about that?
>
> Thanks in advance and regards,
> Norbert
>
>

Zossebart

unread,
Jul 26, 2017, 8:44:56 AM7/26/17
to OSM Android bikerouting
Hi Norbert,


On Monday, July 10, 2017 at 6:17:28 PM UTC+2, Norbert Kress wrote:
Hi,
I've found your profiles for MTB - which were recommended bei Putnik. But both profiles - Puntniks and yours (Zossebart Hard) - do a routing in the valley and not over the hill, which I don't understand.
The same behavior was on GPSies, while using GraphHopper.
I was MTB'ing over the weekend in Sauerland and one of our trips had been from Brilon to Willingen over the hills. One of our guys had used a Garmin and that founds a track over the hill.

Any idea about that?

Thanks in advance and regards,
Norbert

You are right, my profiles somewhat still penalize uphills. That's mainly because of my own preference.
The profiles are intended to be used with via-points rather than only for A-B routing. I normally do a routing with via points set on hills/mountains I want to decent from, letting the profile find uphills to / downhills from those hills and avoiding uphills otherwise.

I already thought of creating a profile variant which only penalizes the steepest uphills...if I only had time to do it ;-)

Regards,
Zossebart


 
Reply all
Reply to author
Forward
0 new messages