In an update to OsmAnd about a year ago, they introduced for the first time Naismith's rule to factor elevation into the calculation of WALKING times. Back then, I tested it and it worked. Numerous refinements to Naismith's rule have been proposed, but a fundamental uncertainty is one's personal physical capabilities. I don't know anything about the bicycle case, but I suspect that the variability from person to person (even for a typical user) would be even greater?
In the long term, it ought to be possible for apps like OsmAnd to automatically calibrate to our recorded behaviour! On Saturday, May 25, 2019 at 11:12:00 PM UTC+1, Bart Eisenberg wrote: > > Ah, right. And agreed. The time calculation on OsmAnd does not take > elevation gain or loss into account. > > On Saturday, May 25, 2019 at 2:56:34 PM UTC-7, jot ess wrote: >> >> Obviously I have not made my problem clear. I have not systematically >> tried whether routing is different with different options. My point is, >> that elevation is not taken into account for calculation of time. I tried >> different options for a hill nearby (where there are no different >> possibilities for the route) and I let Osmand calculate those 1.7km with >> ~100m difference in elevation and it always takes 4 minutes. No matter >> whether on or of, no matter even whether up or down! This means I should >> cycle an incline of ~6% with 25km/h in both directions. >> > -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/50412646-c924-47a6-a9b7-67a120097dde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
