You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When importing from a Google Records.json file, positions recorded from different devices are treated as if they were the same.
This results in "teleports" between both devices, inflating the distance travelled massively (see screenshot).
Version
0.15.3
To Reproduce
Steps to reproduce the behavior:
Import a Records.json containing points from multiple devices. e.g. :
Expected behavior
I expected implausible changes in position to be filtered out or data from unreliable devices to be filtered (automatically or manually).
Screenshots
The text was updated successfully, but these errors were encountered:
Shower thoughts: need option to detect active device (like moving more than 50m/150ft) and prioritize its info for next 5 mins. But looks a little bit process heavy
Describe the bug
When importing from a Google Records.json file, positions recorded from different devices are treated as if they were the same.
This results in "teleports" between both devices, inflating the distance travelled massively (see screenshot).
Version
0.15.3
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected implausible changes in position to be filtered out or data from unreliable devices to be filtered (automatically or manually).
Screenshots
The text was updated successfully, but these errors were encountered: