Cobra wrote:
Robert Laird wrote:
I sure wish someone (maybe an iFlyGPS person?) would explain to me/us why this is an issue.
But.... there is data within the target information, including but not limited to your unique tail number and your unique Broadcast ICAO number. From a programming perspective, it should be easy enough to extract that data from your own ADS-B unit's configuration file, and compare it with target information that is inbound. If two targets have the same tail number, or if they have the same ICAO number, or both, then that target should be discarded.
But since this doesn't seem to be so easy to solve, there must be more to it than I can imagine. But it'd be nice if someone could explain it to me/us!
I am neither an iFly employee (though I do consider myself an "iFlyGPS person" :-) ) nor a retired programmer. Nor am I an expert in ADSB data structures. I haven't even slept in a Holiday Inn Express lately.
....................
I'm not saying that's the actual reason this problem is hard to completely solve. I'm just saying it's easy to imagine some possible reasons why this problem might be hard to completely solve.
Cobra -
Thanks for chiming in! As I said, it's more than I could imagine. It's sounding like the system is half-baked and that companies like AP have to do their best with an inconsistent system. So, yeah, I can well imagine, now, why ghosts have become a problem! And they may continue to be a problem until something else within the ADS-B system improves. I'm still glad we have what we have, but improvements from the FAA are definitely called for.