Closed clementzach closed 1 year ago
Previously, compute_future_flight_positions was using the incorrect indices to create start_x and start_y. This caused invalid latitude measurements to be introduced, and later introduced errors down the line. This fixes that issue.
@clementzach looks good feel free to merge
Thank you @GeorgeEfstathiadis !
Previously, compute_future_flight_positions was using the incorrect indices to create start_x and start_y. This caused invalid latitude measurements to be introduced, and later introduced errors down the line. This fixes that issue.