Understanding 'trace' data parameters and units in more detail

[MrAirspace]

Hi :)

I would like to ask where I can find more detailed information regarding the 'trace' element contained in the 'tracefull*.json' files in the traces folder of the raw adsb data.

For example the trace entry of an aircraft like the one below: _[42831.19, 47.46252, 8.47222, 4650, 174.9, 264.1, 0, 2624, None, 'adsbicao', 4600, 2496, 173, 14.4]

Element 0 of the list seems to be the time of the transmission, measured in seconds from midnight UTC, then the lat/lon (element 1 and 2 of the list), followed by the alt/flight level/height (element 3 of the list). But thereafter, I can not figure out what it is. And maybe even my interpretations of elements 0-3 are incorrect ;) I assume the next parameters concern aspects like track or heading, etc, but I do not know it for sure. Sometimes there is also a data dictionary in the list, which is more explanatory as it has key:attribute values. Like this trace of an aircraft in the adsb data:

_[42828.77, 47.462814, 8.475197, 4550, 175.1, 267.7, 0, 2496, {'type': 'adsb_icao', 'flight': 'SXS111 ', 'alt_geom': 4525, 'ias': 173, 'tas': 178, 'mach': 0.28400000000000003, 'wd': 275, 'ws': 4, 'track': 267.71, 'track_rate': -0.44, 'roll': -3.34, 'mag_heading': 262.44, 'true_heading': 265.69, 'baro_rate': 2496, 'geom_rate': 2496, 'squawk': '3035', 'emergency': 'none', 'category': 'A3', 'nav_qnh': 1010.4, 'nav_altitude_mcp': 6016, 'nav_heading': 272.11, 'nic': 8, 'rc': 186, 'version': 2, 'nic_baro': 1, 'nac_p': 8, 'nac_v': 1, 'sil': 3, 'sil_type': 'perhour', 'gva': 1, 'sda': 2, 'alert': 0, 'spi': 0}, 'adsbicao', 4525, 2496, 173, -3.3]

But the majority of cases, a 'simple' transmission occurs, as per the first example. Does anybody know where I can find information of which exact parameters as well as the pertaining units are included in those transmissions?

Thank you so much in advance! :) Sebastiaan.

[wiedehopf]

https://github.com/wiedehopf/readsb/blob/dev/README-json.md#trace-jsons

[MrAirspace]

Super, that was what I was looking for, thanks a lot @wiedehopf :)