Sorry if it sounded like that and i i was not questioning the explanation nor the tar1090 interface which i really appreciate
What data do you need in the screenshot? I was only interested in what this data show. I never said that i question it or see it incorrect.
I just wanted to get some more details about the data shown.
For me the question is answered and we can close this particular topic in this thread.
It’s always nice to have the ICAO hex included that’s at the top of the details.
That way one could check if it’s always sending that spurious selected altitude.
Cheers!
Now i get the misunderstanding.
I wanted to know about that data field in general, not the particular plane/helicopter i was taking the screenshot from.
Anyhow, if you want to know more about that field:
view1090-fa --show-only 3C674F | grep -i selected -B4 -A4
view1090-fa will show very detailed packet information for a specific ICAO address (shown in tar1090 below the callsign in the selected tab)
The | means the output is redirected to another program to not show every message.
grep options:
-i: ignore upper/lower case
selected: search term
-A4: show 4 lines after the search term is found
-B4: show 4 lines before the search term is found
This way you could find out rather quickly if the aircraft in question is repeatedly sending the wrong information.
As obj explained, sometimes there is misinterpretation of Comm-B going on, so it’s not impossible that the wrong value would repeat.
Loving the recent openAIP integration! 
It’s nice but oh, so crowded though.
Does anyone have an explanation for the red Danger/Restricted zones? Such as the reasons those zones exist where they do.
They are usually military sites of some sort - rifle ranges, tank live fire ranges, air-ground bombing ranges or weapons testing of some sort.
For the US users, the following link is an amazing resource from the FAA allowing you to see all kinds of detailed airspace information, including the restricted zones mentioned above: https://faa.maps.arcgis.com/apps/webappviewer/index.html?id=9c2e4406710048e19806ebf6a06754ad
For UK users, check out Al Kissack’s OL3 mods, a drop-in replacement for /usr/share/dump1090-fa/html. It provides similar info here.
I’m using combine1090 and tar1090 running on a VPS to aggregate 1090 and 978 feeds from a single remote RasPi - but I’m seeing ‘ghost’ aircraft on the plots where the ‘real’ aircraft was reported from its 978MHZ UAT signal and the ‘ghost’ is an MLAT plot showing up on the 1090 MHz feed.
Example here:
Is there a way to filter MLAT out ?
By default MLAT shouldn’t even be forwarded. (so you must be forwarding it)
You can press Shift-N, but be aware that the shortcut is undocumented and not supported.
So if you forget you have it enabled, don’t blame me 
No need for the shortcut and nobody to blame except myself for a bad config of combine1090
Thanks for pointing me in the right direction - ghosts are gone…
Oh well, actually you’re right, combine1090 by default forwards both ports, the one for MLAT and the one for normal messages.
Anyhow glad you could resolve that.
On the other hand having MLAT results is nice.
If the results are those anonymized results, that could lead to ghosts i assume.
Or do they have a different hex for their 1090 and 978 transponders?
There was an option to disable anonymized FA MLAT results, but i recently removed it as it was very FA specific.
I’ll think about it.
There is also an option at the piaware level to not generate anonymized results in the first place (“piaware-config mlat-results-anon no”), if that works better for this case.
A minor thing I recently noticed is the NEXRAD toggle in the settings window (gear icon) doesn’t appear to be functional. The NEXRAD toggle in the layers window works fine however. I’m on the latest version 200405, but this has been the case for a while now.
Well, easy solution: i’ll remove the button!
Menu is getting crowded anyhow.
Not sure when this started. Perhaps with a recent update, not sure. Even though I have the FA links flag enabled in config.js, the FA links are not appearing in the sidebar when an aircraft is selected. I’m running the most recent version update 3 hours ago (200414).
Delete your config.js, run the install script, reconfigure.
The feature is working fine for me, not sure what the issue would be.
Most likely is using the wrong syntax in the configuration.
@timothydykstra82
It works for me too on the latest version.
The only change I had to make was to change line 173 in config.js to read:
flightawareLinks = true;
