Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outlier filtering #34

Open
linusg opened this issue May 10, 2020 · 3 comments
Open

Outlier filtering #34

linusg opened this issue May 10, 2020 · 3 comments
Labels
Status: Needs investigation Needs further investigation Type: Feature New feature

Comments

@linusg
Copy link
Member

linusg commented May 10, 2020

I did, in fact, not take a trip into the River Thames.

image

We could do this by calculating the average speed between points for example, a sudden spike is an outlier. (great idea from @growse)

Not sure if this should be part of the recorder's API or just a frontend thing.

@linusg linusg added Status: Needs investigation Needs further investigation Type: Feature New feature labels May 10, 2020
@0xspade
Copy link

0xspade commented Mar 20, 2022

This also happens to me, but we all know that this is a false positive, this also occurs in Traccar.

@rrkarman
Copy link

rrkarman commented Aug 4, 2023

Would love to come up with a way to filter these outliers or possibly manually delete these from the dataset through the frontend interface. (I recently had one with a longitude of 0 (prime meridian) and an accuracy of 9 and I am in the US)

@linusg
Copy link
Member Author

linusg commented Aug 4, 2023

The recorder provides no API to delete locations, you'll have to do that manually or run a script on the .rec files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs investigation Needs further investigation Type: Feature New feature
Projects
None yet
Development

No branches or pull requests

3 participants