'Minimum disance' filter gets confused when the phone is moved

[nathanncohen]

Let me start by saying: GREAT APP. I use it to log my position constantly.

Unfortunately, 90% of the points that I log are useless: despite the 'min distance' filter, the app logs consecutive points even below the filter value.

Try for yourself:

• set only a 'minimum distance' filter of 20 meters, and look at your phone on the table.
• It logs one point, nothing more
• Now take your phone, and shake it
• It will log more points, despite not having moved by much

It seems that the 'minimum distance' filter gets confused when the phone moves (or when it is in your pocket). Could this maybe have an easy fix?

Thank you again for your work :-)

[GrazianoCapelli]

Thanks, really glad you like the app, and thanks a lot for the clear report and steps to reproduce.

Currently the app intentionally records points at the moments when the user stops or starts moving, regardless of the configured filters. We do this because we need some samples that mark the transitions between moving and stopped, so the average speed statistics (which could be based on time in movement) make sense. The downside, as you noticed, is that this causes extra points to be logged (including points that are formally below the "min distance" threshold) also when the phone is shaken or jostled.

We’re thinking about ways to fix this so the app respects the minimum-distance filter more strictly while still keeping correct in-movement statistics. I’d like to keep this issue open so we can track changes and updates here linked to your report.

Thanks again for the feedback, really helpful.
Cheers!