>
> On Thursday, January 16, 2020 at 11:07:30 PM UTC-8, Danilo Baggini wrote:
>
>> For your information the OsmAnd time of about 4 hours is for very very
>> fast hikers the normal time is 5-6 hours.
>>
>
On Fri, Jan 17, 2020 at 10:34 AM Bart Eisenberg
wrote:
> I'm not surprised your
I'm not surprised your estimate is longer: that's a steep trail.
Thanks for your OSM contributions. On the map, at least, it looks like a
nice part of the world.
On Thursday, January 16, 2020 at 11:07:30 PM UTC-8, Danilo Baggini wrote:
>
> Thanks to all for the clear considerations.
>
> I
Thanks to all for the clear considerations.
I reach with OsmAnd the same yours time resul for the A34 very step path.
For your information the OsmAnd time of about 4 hours is for very very
fast hikers the normal time is 5-6 hours. I am an Alpinist and
Climber from long long time and I
@A Thompson--I didn't know that: thanks! I got the similar results to
yours when having OsmAnd plan the route. 4:25 up, 1:45 down. (I had to set
an intermediate waypoint for the downhill route to keep it on the GPX)
@ danilo.baggini: this video might help. https://youtu.be/UXpvjE1vmbI . In
Actually, for walking OsmAnd does now use Naismith's rule to factor ascent
into the time estimate. But it seems that it doesn't do this is you are
following your own .gpx track. If I take the start and end of the .gpx
track and allow OsmAnd to plan its own walking route, then the estimated
OsmAnd doesn't take elevation gain into account for time estimates. From
App profiles/Walking/Vehicle paramaters/Default speed, you can set a
minimum, default and maximum speed. That might help for some situations,
but for a hike that steep, I would guess your own personal estimate would
come
