Is all data - e.g. accuracy confidence - sent to the server by the app, and can it be used for cleaning it up later?

[richardacre]

Dawarich Android App and Backend hosted on Debian

I've notice that e.g. when I'm riding a train that a few points will be quite accurate (on or near the train line), but a few will snap to nearby towns and villages (that the train doesn't go through directly) or just be obviously wrong. My guess is that, at these moments, the accuracy/confidence is low - i.e. a high radius of possibility.

So I'm thinking, that a server-side job could revisit a day's points and look at these points, and a few either side of it in time, and having noticed that there are some high-accuracy points, then a low-accuracy one, then another high-accuracy one, to move the low-accuracy points to be in a line between the other two but still within its original accuracy radius (and store the original reported centre so that later/different analysis could have another go, or you could re-set it).

Example of a couple of train journeys here (BTW this entire day is logged as a single trip, it seems that no matter what I set my "haven't moved X distance in Y time settings to, it rarely logs any visits, I'm guessing the jitter of my data is so extreme that it always regularly jumps around, even when I'm at home - something that could be solved by this #2724 )

possibly related to #3048