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

Dev #6

Merged
merged 15 commits into from
Dec 29, 2018
Merged

Dev #6

merged 15 commits into from
Dec 29, 2018

Conversation

corstian
Copy link
Member

No description provided.

With this commit the only thing we need to know in order to be able to
determine flight times:

- Latitude
- Longitude
- Timestamp

This will allow us to combine FLARM feeds with ADS-B feeds in order to
get a more accurate picture of what's going on.

But please note we need something to figure out timing issues when mid
flight. Those are a PITA.
In case a limited subset of data would be used data would not be
processed at all, and an unhandled exception would be thrown.

Currently there's still an issue related to processing of data in
limited amounts. If the update speed at which we get our data is higher
than the speed with which new GPS fixes are being retrieved, we see that
as an aircraft that's standing still.

We could fix that by:
- Calculating G load. If it's higher than 9G we could either ignore it
or mark the crash site.
- Just let it be, and only mark an arrival if there are multiple points
in a row (like 5 or something) that say the aircraft has a groundspeed
of 0.
@corstian corstian merged commit b4d6f7b into master Dec 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant