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
thanks for your work. We have been using on many GPS tracks your Anomaly Detection to sort and filter all bad position reported by incorrect GPS fix.
It works well still I'm trying to figure how I should handle such case. So far we are checking speed to detect anomaly but we would have the same issue by checking distance or straight GPS latitude/longitude. I attached a graph to provide a sample of data where I got some anomaly detection found while it's a normal behavior and expected data.
How should we resolve this?
The text was updated successfully, but these errors were encountered:
Hey @Toucouleur66, you'll probably want to use a different approach / library for this (one possible approach). If you find something that works well, I'd be curious to hear the details.
Hi there,
thanks for your work. We have been using on many GPS tracks your Anomaly Detection to sort and filter all bad position reported by incorrect GPS fix.
It works well still I'm trying to figure how I should handle such case. So far we are checking speed to detect anomaly but we would have the same issue by checking distance or straight GPS latitude/longitude. I attached a graph to provide a sample of data where I got some anomaly detection found while it's a normal behavior and expected data.
How should we resolve this?
The text was updated successfully, but these errors were encountered: