Inaccurate current speed at low speed
At low speeds, typically when hiking, current speed is inaccurate. I think it comes from a too short time/distance intervall the speed is calculated over. So, for example, if location precision is +/- 10m, the current (real) speed 1m/s, and current speed calculated over a 5 second intervall, the distance could vary from -15m to +25m, resulting in an absolute calculated speed of 0 to 5 m/s ! The same apply to vertical speed.
To avoid that, the time/distance interval should be ajustable, and at least calculated over a distance interval where imprecision becomes negligible. Anyway, in real world, it is often desirable is to choose the way the speed is calculated. For example, when hiking, you don`t need to know your speed over the last second (even if it was acurate), but rather over the last 1mn, or the last 100m, or vertically over the last 10mn.
The same problem 
Hello Ludovic,
I`m not sure if this error is something I may simply fix. Locus generally do not modify speed values that comes from your GPS unit. So values you see, aren`t computed by some internal algorithm, but directly by Android system. Locus just display them ...
So this is more task to create some filtering of speed, that may reduce speed noises, then to fix some existing problem in Locus. I suggest to check these values in different app. If this app will also just display these values, you`ll see, they`re same ...
Hello Ludovic,
I`m not sure if this error is something I may simply fix. Locus generally do not modify speed values that comes from your GPS unit. So values you see, aren`t computed by some internal algorithm, but directly by Android system. Locus just display them ...
So this is more task to create some filtering of speed, that may reduce speed noises, then to fix some existing problem in Locus. I suggest to check these values in different app. If this app will also just display these values, you`ll see, they`re same ...
Hi Menion,
if you have a look at the track display in Locus, you can see that the speed recording is very noisy whereas the altitude recording is pretty good now since some time (mainly due to some filtering).
I think it would be helpful to think about filtering speed values as well and offer it as a separate parameter like "moving average speed" for dashboard, track display etc.
Hi Menion,
if you have a look at the track display in Locus, you can see that the speed recording is very noisy whereas the altitude recording is pretty good now since some time (mainly due to some filtering).
I think it would be helpful to think about filtering speed values as well and offer it as a separate parameter like "moving average speed" for dashboard, track display etc.
Hello guys, hope you don't mind if I close this topic. Speed is partially filtered and should be a lot better then two years before. It's probably still not the best during slow speeds, but I'm sure it will get improved over time (also together with improved precision of GPS in devices). Thanks for understanding.
Hello guys, hope you don't mind if I close this topic. Speed is partially filtered and should be a lot better then two years before. It's probably still not the best during slow speeds, but I'm sure it will get improved over time (also together with improved precision of GPS in devices). Thanks for understanding.
Replies have been locked on this page!