Make navigation_average_speed_<X> a value in menu for better "time to target" values
Gathering feedback
Helllo All,
I would suggest to make the navigation_average_speed_<X> from config-file a value in the track recordings menu profils.
First, then we could make a profile for biking mtb and biking race - with varies widely in the parameters I would like to use in the track recordings menu. This will result in a much better "time to target" values.
Second, it would be much easier to find for everybody like me, wondering how locus calculates time to target. Because for me this value was useless until I find out how to lower the standard values - normaly biking MTB single tracks also uphill with an average of 11 km/h and not 18km/h as set in config-file....
Greetings, thanks
Wille
I like this idea 
Hello Wille,
mainly based on this discussion : http://help.locusmap.eu/topic/why-was-time-to-target-so-wrong , these parameters are since version 3.9.3 not used!!! Current time estimates are computed by different method based on current movement.
After some testing in the field, we will see if new method gives better results or if previous solution with easier configuration should be more useful.
Hello Wille,
mainly based on this discussion : http://help.locusmap.eu/topic/why-was-time-to-target-so-wrong , these parameters are since version 3.9.3 not used!!! Current time estimates are computed by different method based on current movement.
After some testing in the field, we will see if new method gives better results or if previous solution with easier configuration should be more useful.
Sorry Menion, I missed that these parameters are not used any more.
Can I (or you) close or delete this idea...?
Greetins
Wille
Sorry Menion, I missed that these parameters are not used any more.
Can I (or you) close or delete this idea...?
Greetins
Wille
You cannot miss it, because I never wrote about it :).
I've leaved them in config, because I'm still not sure that new system will work. Only field tests next week will show. Till then, we should consider this idea as "paused". After some tests we all will see if there is a way to use new "automatic" system, or we will need this idea to make it work.
Oki?
You cannot miss it, because I never wrote about it :).
I've leaved them in config, because I'm still not sure that new system will work. Only field tests next week will show. Till then, we should consider this idea as "paused". After some tests we all will see if there is a way to use new "automatic" system, or we will need this idea to make it work.
Oki?
In my 2 hour ride yesterday the estimate was the same as if I had used 0.3 (m/s) for navigation_average_speed_<X> in the config.cfg. In other words, the new system was working nicely for me (no change), but only one test so far. And I didn't stop, so no check yet on what gets displayed while stopped.
In my 2 hour ride yesterday the estimate was the same as if I had used 0.3 (m/s) for navigation_average_speed_<X> in the config.cfg. In other words, the new system was working nicely for me (no change), but only one test so far. And I didn't stop, so no check yet on what gets displayed while stopped.
Perfect, glad to hear it. No hurry ... I'll also do some more field testing and we will see ...
Perfect, glad to hear it. No hurry ... I'll also do some more field testing and we will see ...
Replies have been locked on this page!