My PlaneFinder feed is having errors connecting to the PF site.
Having emailed them, they suggest dump1090’s (i’m using Muatbility 1.14) error correction should be turned off, as a possible culprit.
They suggest turning off “-fix” and “-aggressive” (if they’re on - I’ll check when I get home).
Any thoughts - should I do this, what’s the impact?
I wonder if they have changed their data quality criteria recently. I had a similar problem a few weeks ago and they requested I turn off --fix. It does make a difference to the number of tracks recorded, but the reduction is primarily those with single messages which are far fewer than before. It doesn’t seem to make much difference to the number of aircraft seen or the message rate.
I am actually thinking of removing --aggressive from dump1090-mutability entirely - it feels a little wrong to do that, but it seems to be a magnet for people to turn on without understanding the consequences and then spewing bad data everywhere. Maybe I’ll make it a compile-time option to enable it.
maybe too much cost - but aren’t mlat positions marked as ‘mlat’ … what about setting a marker ‘probably wrong’ in the position data output from aggressive …
i guessed that this were not so trivial. since i shut down my --aggressive flag on your request some weeks ago - i saw nearly zero decrease in real detected aircrafts - and won’t miss it. maybe simply deleting the dedicated mutability reconfigure-page for --aggressive would do 90% of the trick …