The gps sometimes captures an imprecise location which will then result in a flight trace that jumps around
solution
The implemented solution to alleviate this problem consiste of first trying to detect such "anomalies" in the flight trace and then to just delete them in order to create a more continues trace.
The main strategy is to compare the distance of a point A and its predecessor A-1 with some distances of its predecessors i.e. dist(A-1, A-2), dist(A-2, A-3) in order to detect distances that incremented too rapidly. This method works fine in the case of hot-air ballons since they do not have fast accelerations.
anomaly detection and removal
Problem
The gps sometimes captures an imprecise location which will then result in a flight trace that jumps around
solution
The implemented solution to alleviate this problem consiste of first trying to detect such "anomalies" in the flight trace and then to just delete them in order to create a more continues trace. The main strategy is to compare the distance of a point A and its predecessor A-1 with some distances of its predecessors i.e. dist(A-1, A-2), dist(A-2, A-3) in order to detect distances that incremented too rapidly. This method works fine in the case of hot-air ballons since they do not have fast accelerations.
As a distance metric we've used the haversin metric to perform distance computations based on the longitude and latitude ( * https://www.geeksforgeeks.org/haversine-formula-to-find-distance-between-two-points-on-a-sphere/ )