Current Situation / Problem
ADS-B Exchange reports "static" transponders, which are displayed in ADSBEx's radar view as type TWR. At the time of writing, EGCC had 4 of them around the airport perimeter.
As it is impossible to derive a type, LiveTraffic displays those object with default type, often "A320". So we end up having static A320 sitting around the airport, not rarely even within buildings, which looks ugly.
Looking at the ADSBEx raw data there is nothing that suggest these object to be of static nature. There are very few fields filled with reasonable data at all, basically only position:
However, unlike any plane (even taxiing planes) ADSBEx in this case of static objects delivers no altitude data ("alt":"","galt":"") plus a positive ground flag ("gnd":"1"). I'd love getting such accurate data for taxiing planes...but...well...
Suggested Solution
Try to derive a way of identifying static senders. Assuming the above pattern of unused fields and fields set to 0 plus a positive gnd flag might be a start.
Offer an option to hide static ADS-B senders, default: on, as there is no reasonable representation otherwise.
If this option is off, then those objects should be classified as cars, not planes, though.
Benefits
Allows to remove object from the scenery that don't belong there.
Current Situation / Problem ADS-B Exchange reports "static" transponders, which are displayed in ADSBEx's radar view as type TWR. At the time of writing, EGCC had 4 of them around the airport perimeter.
As it is impossible to derive a type, LiveTraffic displays those object with default type, often "A320". So we end up having static A320 sitting around the airport, not rarely even within buildings, which looks ugly.
Looking at the ADSBEx raw data there is nothing that suggest these object to be of static nature. There are very few fields filled with reasonable data at all, basically only position:
However, unlike any plane (even taxiing planes) ADSBEx in this case of static objects delivers no altitude data (
"alt":"","galt":""
) plus a positive ground flag ("gnd":"1"
). I'd love getting such accurate data for taxiing planes...but...well...Suggested Solution Try to derive a way of identifying static senders. Assuming the above pattern of unused fields and fields set to
0
plus a positivegnd
flag might be a start.Offer an option to hide static ADS-B senders, default: on, as there is no reasonable representation otherwise. If this option is off, then those objects should be classified as cars, not planes, though.
Benefits Allows to remove object from the scenery that don't belong there.
Additional context Forum post