For bicycle, there is similar rule - the principle is the same, it just uses different values. Of course, the differences are here much bigger (easy ride x race). But as a rule of the thumb, I would suggest something around speed 20 km/h and 800 vertical meter / h for "faster" and 15 km/h and 600 Vm/h for "easier" or lighter off road (tracks, easy paths).
Ideally, allow the user to manually set the numbers as variables - better trained/experienced people usually know their current numbers. There is a marked difference between my numbers in February/March and in July/August for the same route, ridden with no extra effort :) The same - make use of user-set variables (or preset values) would work for walking as well. On Monday, 3 June 2019 03:01:04 UTC+2, A Thompson wrote: > > 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! > -- 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/d3e7ecab-8a8b-4604-af5b-e8f65355d9c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
