Altitude Reported in dump1090


#1

Quick question, is the altitude displayed by dump1090 pressure altitude or something else?


#2

It is going to be whatever the Mode C altitude squawk is, which is pressure altitude (29.92), or so I would think. ADSB could be reporting GPS altitude though, not sure. Interesting question though, as I do see a lot of tracks reporting exactly 34000 feet (or whatever), which is no surprise given most airliners are going to be on autopilot with altitude hold during the encounter phase of flight.


#3

All the references I’ve seen say pressure altitude. I am very new to this, though, so it’s possible I’m not looking at the right references. As to the exactly 34000, it’s likely there’s some rounding going on. I haven’t seen anything more precise than 25 feet. And I think the format allows for less precision.


#4

I would think it would be pressure altitude as well; however, altitudes do change for me when the planes are closer to the ground. I also took a plane on approach into KORD who was told to maintain 7000 for the approach. He indicated 7275. I took the KMDW altimeter setting (the closest to the A/C) and did the math: 29.92-29.64=.28. That means the A/C’s altimeter should be indicating 280’ above what it is actually at. So in other words, it measures the aircraft at 29.92. So to figure out what the A/C is actually at in MSL (ASL), you need to do the math every time. I think my math checks out, but if anyone else knows better, let me know! Thanks!


#5

Are you missing something? Where did the 29.64 come from?


#6

The local altimeter setting. Transponders squawk pressure altitude though, uncorrected for local baro, and ATC computers apply the appropriate offset to the track to display “MSL” on their scopes.


#7

It would be cool if we had the same technology.


#8

My weather station console is literally inches away from my Raspberry Pi. Seems like something should be possible. If I had the time and inclination, I might come up with something. Really, it should be done in PiAware, though, I think. It could periodically poll nearby airports for current pressure…


#9

Wouldn’t be hard to get the local altimeter setting from a METAR.



root@piaware:/home/pi# curl -s -S http://w1.weather.gov/xml/current_obs/KVDF.xml | grep pressure | awk -F'<' 'FNR>1{print $1}' RS='>'
30.24


Just change the line to put your nearest METAR reporting station code.

You can get plenty of info off of that XML file.


        <location>Vandenberg Airport, FL</location>
        <station_id>KVDF</station_id>
        <latitude>28.01</latitude>
        <longitude>-82.35</longitude>
        <observation_time>Last Updated on Dec 1 2014, 1:55 pm EST</observation_time>
        <observation_time_rfc822>Mon, 01 Dec 2014 13:55:00 -0500</observation_time_rfc822>
        <weather>Fair</weather>
        <temperature_string>81.0 F (27.0 C)</temperature_string>
        <temp_f>81.0</temp_f>
        <temp_c>27.0</temp_c>
        <relative_humidity>54</relative_humidity>
        <wind_string>East at 12.7 MPH (11 KT)</wind_string>
        <wind_dir>East</wind_dir>
        <wind_degrees>70</wind_degrees>
        <wind_mph>12.7</wind_mph>
        <wind_kt>11</wind_kt>
        <pressure_in>30.24</pressure_in>
        <dewpoint_string>62.6 F (17.0 C)</dewpoint_string>
        <dewpoint_f>62.6</dewpoint_f>
        <dewpoint_c>17.0</dewpoint_c>
        <heat_index_string>82 F (28 C)</heat_index_string>
        <heat_index_f>82</heat_index_f>
        <heat_index_c>28</heat_index_c>
        <visibility_mi>10.00</visibility_mi>


So you could really go crazy here, for instance if you want the wind in mph:



root@piaware:/home/pi# curl -s -S http://w1.weather.gov/xml/current_obs/KVDF.xml | grep wind_mph | awk -F'<' 'FNR>1{print $1}' RS='>'
12.7


There’s probably a better way to dump the XML info but for one or two variables, it’s not worth the time required to code a script to extract them all. If I had to do more than 3 or so, I would write a script for it.


#10

OK - quick explanation of the technology involved (in small aircraft):
Transponder - this is the box in the plane sending data to the ground
Blind Encoder - this is the box in the plane which converts the pressure sensed by the static ports on the plane to an altitude referenced to 29.92"Hg (standard pressure)

The transponder can’t work out the altitude itself and doesn’t take GPS altitude. It needs the altitude to be fed from the “blind encoder”.

Below 18,000ft a local pressure adjustment is issued that is used by aircraft in that local area. Above 18,000ft all aircraft in the USA set their altimeters to 29.92"Hg so when planes are high in cruise you are very likely to see exact altitudes which are dead on XX,000ft.

Blind encoders vary in the resolution they provide. Good encoders provide resolution down to 10ft. With better avionics, you can get down to 1ft resolution. It looks to me that there is rounding to the nearest 25’.

As I said at the start, that is a little explanation of the system in a light aircraft - the principles apply to the larger aircraft although the avionics are more complicated.

John.


#11

RTM, Appendix A section A.1.4.2.4 Altitude:

A.1.4.2.4 Altitude
This 12-bit field (ME bits 9 – 20, Message bits 41 – 52) will provide the aircraft altitude.
Depending on the TYPE Code, this field will contain either:

  1. Barometric altitude encoded in 25 or 100 foot increments (as indicated by the Q Bit)
    or,
  2. GNSS height above ellipsoid (HAE).

Note: GNSS altitude MSL is not accurate enough for use in the position report.

I’m not sure if dump1090 even looks at the different reporting types, but I don’t know of any reason an airplane would be reporting GNSS HAE and not baro… maybe supersonic? I’m still not clear on if this section is referencing the Mode-S data or if it’s part of the Extended Squitter block. Dump1090 reports the Mode-S portion.


#12

I think it’s referring to the ES stuff.

I too can’t see why GPS altitude would be broadcast. We’re all flying using air pressure via the static ports for altitude.

John.