Source: Wikipedia
QNH and QFE are arbitrary Q codes rather than abbreviations, but the mnemonics “Nautical Height” (for QNH) and “Field Elevation” (for QFE) are often used by pilots to distinguish between them.
The Q-code is a standardised collection of three-letter codes that each start with the letter “Q”. It is an operating signal initially developed for commercial radiotelegraphy communication and later adopted by other radio services, especially amature radio.
To distinguish the use of a Q-code transmitted as a question from the same Q-code transmitted as a statement, operators either prefixed it with the military network question marker “INT” ( . . _ . _ ) or suffixed it with the standard Morse question mark UD ( . . _ _ . . ).
QNH: is the barometric altimeter setting that causes an altimeter to read zero when at the reference datum of a particular airfield (in practice, the reference datum is either an airfield center or a runway threshold). In ISA temperature conditions the altimeter will read the height above the airfield/runway in the vicinity of the airfield.
QFE - is the barometric altimeter setting that causes an altimeter to read zero when at the reference datum of a particular airfield (in practice, the reference datum is either an airfield center or a runway threshold). In ISA temperature conditions the altimeter will read the height above the airfield/runway in the vicinity of the airfield.
QNE - refers to the altimeter being set to the standard pressure of 1013.25 hPa. It is the setting that causes an altimeter to read the aircraft’s flight level (FL). Flight levels are given in hundreds of feet (for example: FL100 = 10 000 ft). Atmospheric pressure changes over time and position. Thus, the flight level is not “straight”, because it has a different altitude (elevation above the mean sea level).
Image courtesy: norbertflyer
2 Likes
Yep - the same Q-code may be used as a question, statement or an answer. I’ve never heard anyone qualify which it is. It’s just left to context and usually self evident.
QRP - question
QRP 5W - statement or answer
3 Likes
Yes, qualifying is not used in Voice communications, but in telegraphic communications using morse-code, the Q-codes were qualified.
Well, it was a bit bugged and sometimes it wouldn’t properly load the missing data, but now it always works. (until it doesn’t)
2 Likes
Just updated Tar1090 and noticed that the listing of flights on the right panel has a black background.
Where can I change this setting to white again?
Thanks
Hi,
I have searched about the addition of the airline to the map interface but without any success. I was able to add the route via adsb.lol API and would like to ask if there is any way to add the airline/operator via config.js file?
I know there is an API from adsb.lol and asdbdb.com that gives that information via callsign.
If not possible, there is any interest in adding that? Maybe I could try to implement that.
I don’t really want to no.
It can be misleading.
The database used by tar1090 actually has data on operators so i’d just have to load that file and do the lookups.
Not even if not on default but available to add it via configuration file? The data could be consumed via an API and not use the tar1090 db.
Also, is that possible to save the route with the snapshots shown on pTrack? Found that the field is empty when looking into the snapshots.
no that’s not possible.
no i don’t want to use an API for that.
it’s already available as data … i’ll see about at least adding something you can enable i guess.
maybe i just turn it on by default, it is kinda useful if you don’t know the callsing tags i suppose.
1 Like
Thanks for considering this feature. Some people using my radar don’t know the relation between callsigns and airlines, so this would be helpful. I appreciate it!
Months later after problem viewing on Samsung TV browser ran
sudo apt update
sudo apt upgrade
and am able to view the problem tar1090 version on Samsung Tizen browser. Updated to the latest tar1090 and it still works, so thanks to the unknown providers. Thanks for the tar1090 version included in adsb.im.
Maybe the Tizen browser got updated? 
@wiedehopf Just in case it saves you time wasted, early today I updated to the latest Chrome browser production version on Windows and immediately planes failed to show on Tar1090 map until I disabled WebGL in Tar1090 Settings.
Then just now I updated to latest Chrome browser version (134.0.6998.45 (Official Build) (arm64)) on Macbook and the same thing happened. Today’s Chrome browser relase may have broken WebGL or some other compatibiliy issue with Tar1090. Likely not a Tar1090 issue. Disabling WebGL in Tar1090 Settings resolves the issue. I have not seen any other problems with this version of Chrome yet.
1 Like
It seems random but yes i’m already aware.
I’ve checked openLayers versions / tar1090 versions back 2 years and there is no difference.
So it’s not a tar1090 change.
On my linux laptop with chrome beta, the webGL icons usually appear after a bit.
The more icons the quicker they appear it would seem.
Very weird.
For displaying less than 500 planes, disabling webGL is fine but a global map works much better with webGL.
Just updated chrome on this machine … same bug now.
Oh this is gonna be annoying.
Icons showing up after a bit though.
Disable webGL or use Firefox for the time being.
Workaround found, tar1090 updated!
It’s not actually a webGL bug but rather js variables having NaN value in some scopes.
This is gonna be a hard bug to report, very random.
Edit: Bug reported and made a little page to check if a browser is affected: https://wiedehopf.github.io/
Truely weird browser bug.
That was fast. I updated Tar1090 and re-enabled WebGL. No issues found with the workaround release.
I’ll follow the Google bug too.
There might be other bugs because this pattern of global variables being set in one file and then being read from another is quite common in tar1090.
1 Like
Unfortunately that fix still does not fix the issue with Safari on my iPad. Have to disable WebGL to show the map and aicraft. Such is life, lol
