froodproton wrote:I do not understand the difficulty.
There are two datapoints - position and time - distance and time --> Speed
That's what we do and that's what you are not happy with. The difficulty is to explain everyone that there is no one truth and that things like Garmin has value X, you have something else --> You are wrong, please fix.
are not correct. (Most frequently on the subject of elevation)
froodproton wrote: ↑
Tue 8. Jan 2019, 13:20
Maybe with even some more smoothing algorithms - I don't know.
Yes, of course we can think about the smoothing algorithm and try to adjust. But it's not the right way to do this based on one single activity by assuming that Garmin's value of 72 km/h is the one truth.
As I already said, we have a configuration option for the plot precision which is one kind of a moving average - one that is easy to understand for everyone.