"Estimated travel time": Make values for cross country skiing more realistic
The "Estimated travel time" (see http://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning&s[]=route#estimated_travel_time) is very helpful for most movement types except for cross country skiing: Even in "fast" setting it estimates twice the real time despite we are doing classic style (not the faster skating), include the short breaks in the track time, and when we are at medium intensity without being well trained (neither technique nor fitness). I am aware that speeds strongly vary depending on style (classic vs skating) and track type (groomed or not) and piste elevation profile (flat or hilly) and weather conditions (e.g. icy pistes slow you down), hence I guess 3 speeds make more sense then 2.
My observations - feel free to refine by adding your observations :-)
- 5km/h horizontal speed is quite low, usually we're going 6,3km/h to 8,8km/h (without breaks), mostly around 7.2km/h - I assume this to be good value for "medium" speed, i.e. classic style on groomed piste
- roughly 1000m/h downhill is OK for "medium" speed (I can't tell more exactly because I have no idea how to find that value from Locus track statistics page)
- nearly 500m/h uphill is OK for "medium" speed
Cheers, Georg
I like this idea 
Instead of Locus using "hard coded" values for making the estimate of travel time, I suggest the values could be specified by the user (stored in track recording profile?), or maybe better yet, be self tuning based on past tracks where available, so no values need be entered at all.
Instead of Locus using "hard coded" values for making the estimate of travel time, I suggest the values could be specified by the user (stored in track recording profile?), or maybe better yet, be self tuning based on past tracks where available, so no values need be entered at all.
Thanks for useful information Georg,
so what about such improvement
Thanks for useful information Georg,
so what about such improvement
Hello,
I think that creating standard profiles can be usefull only for "standard" activities like bike or running on streets but into the wild the terrain makes the difference. Also the physical preparation of each one is a value that can change a lot the travel time.
There are a lot of activities without profile and I think it is not possible to cover all.
What about trail running?
The best solution for me is something where to put data of speed in plain km/h - positive gain m/h - negative gain m/h so each one can fill the data according to terrain and ability.
Hello,
I think that creating standard profiles can be usefull only for "standard" activities like bike or running on streets but into the wild the terrain makes the difference. Also the physical preparation of each one is a value that can change a lot the travel time.
There are a lot of activities without profile and I think it is not possible to cover all.
What about trail running?
The best solution for me is something where to put data of speed in plain km/h - positive gain m/h - negative gain m/h so each one can fill the data according to terrain and ability.
Good day Lorenzo,
I believe that current values are close to some "average value" of most of users, so I consider this idea as implemented. You may discover your own estimates compare to computed values by Locus. I expect that most of users will be able to find out that they are usually about 10% faster then Locus compute. It's a lot easier then estimate positive/negative speed parameters.
Anyway feel free to create a request if not already exists, for a user-based customization of this feature.
Good day Lorenzo,
I believe that current values are close to some "average value" of most of users, so I consider this idea as implemented. You may discover your own estimates compare to computed values by Locus. I expect that most of users will be able to find out that they are usually about 10% faster then Locus compute. It's a lot easier then estimate positive/negative speed parameters.
Anyway feel free to create a request if not already exists, for a user-based customization of this feature.
Hello,
I mam using app for skialp skitouring and I can not use profiles for estimare time in app. For skitouring is very diferent speed up and sking down. It is possible make some profile editable or make some profile for skitouring ;-)
Best regards
Lukas
Hello,
I mam using app for skialp skitouring and I can not use profiles for estimare time in app. For skitouring is very diferent speed up and sking down. It is possible make some profile editable or make some profile for skitouring ;-)
Best regards
Lukas
Replies have been locked on this page!