-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Possible position mis-decode #21
Comments
I just noticed that |
I bet it's just the time between messages. I use the "Globally unambiguous position decoding" decoding which if I remember correctly uses both an Odd and Even 'Frame` for calculating the new lat/long. It could also be a problem with my buffer in/out system. I'd have to checkup on that logic. |
Oh yeah, time between messages has definitely caused this issue for me before, in other decoders. |
Add --filter_time for removing airplanes after the the specified time. This is down to 2 seconds in the ICAO document, but I see 10 seconds as being pretty good for reducing the amount of mis-decodes greatly. This was previosuly 60 seconds, which was giving very bad lat/long if a long period of time was between both messages odd/even. See #21
I have something similar to this, fairly often I decode a lat/long of -300 ish by -170 ish, with a receiver location of roughly 50, -5. There's a possibility this is down to interference but I find it odd that it would always be in the ballpark of -300 -170. |
Interesting. I'd like to get rid of this issue. This would require having more lat/long cpr values for all the bad lat/long values after calling I'd also like to see if this is a problem in the C libraries, or if they do more pre/post processing. Which dump1090 did you use? |
I used this version of |
But that aircraft was closer to longitude -117 (screenshot may have been a few minutes after the decode above):

The text was updated successfully, but these errors were encountered: