-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #44 from terminal2/fix-bds40-decoding-high-alt-fli…
…ghts Improves high altitude flight detection of BDS40 data
- Loading branch information
Showing
2 changed files
with
33 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
df9c40d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surveillance is done until FL600 - I would put the filter at FL610 to allow for private jets and military traffic above FL500
df9c40d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It first was checking up to FL650 as is allowed by the data packet.
When trying to determine which BDS is used you want to filter on the 99% of traffic. The likelihood of a FL600 being a normal flight are low compared to it not being BDS44.
currently removing errors through real recorded data, this value may go bit higher if I find more examples.
I'll try run the dataset through my test script using FL610 see if I get the same amount of multiple matches / invalid data as I get now.