For my usecase I use the hike and mountainbike profiles but the included ones don't consider steepness.
So now I was having a look at the bike2 profile and try to adopt it for the hiking profile. Now I made good progress, so that steep section require more time (by decreasing the speed).
So what I now don't understand is the following:
I made speed go down it there is a lot of ascent and made it slightly go up if descending. But still, when I reverse a route, the duration is the same.
So what I figured out is that the bike profile has part of the code that asks
isBackward. Can anybody tell my how that works? What is it?
I assume the following:
I have an edge with a starting point A at 100m altitude and an endpoint B at let's say 200m altitude.
isForward is true I would have an ascent of 100m but if
isBackward is true than I'd have a descent of 100m?!? right?
So A is still index 0 in the point-list and B is at the last index, but the system want's to know... how fast would i be if I went the opposite direction?!?
At least when I do so, I get wrong results... So I guess that my assumption is wrong?
EDIT: ok... a little playing revealed that
isForward is not the opposite of
isBackward... So i guess my assumption is wrong?!?