Hook wrote:
So here's a suggestion for the AP folks: put an extra field in the aircraft profile and let the user optionally supply the ICAO hex code. If the code is there, the software would have a foolproof way to eliminate ghosts for that aircraft (like the capability apparently available in the Stratux code). Otherwise, it can continue to use the logic it does now.
Tail number is already included in ADSB data, and iFly uses the tail number in the Aircraft Profile as part of the ghost detection logic, so the intent of your suggestion is already implemented.
If the ghost detection logic is at fault here, it's the part of the logic that is intended to eliminate your ownship ghost from appearing due to other reasons. Example: ADSB-Rebroadcast traffic targets with no tail number identification associated with them that iFly incorrectly guesses is you.