Opensky api response - states array

Hi,
when i call opensky-network.org/api/states/all
i get 18 elements in each element in state array.

["4240ec","UTA394 ","United Kingdom",1499105360,1499105360,21.9943,54.9052,8404.86,false,225.19,84.89,9.1,null,8397.24,"7674",false,false,0]

The documentation describes 13 only.
Can someone describe the other elements right after sensors element which is null in my case?

And thanks for great API with flight data.

Hey nlavri,

we just released new API features a few days ago and did not yet get to update the API documentation. Sry for the confusion! In fact the features are so new not even out web frontend shows the data yet!

The following list describes the updated state vectors:

* [
* 0 icao24: string,
* 1 callsign: string (nullable),
* 2 originCountry: string,
* 3 lastPositionUpdate: int (nullable),
* 4 lastContact: int,
* 5 longitude: float #.#### (nullable),
* 6 latitude: float #.#### (nullable),
* 7 baroAltitude: float #.## (nullable),
* 8 isOnGround: bool,
* 9 velocityOverGround: float #.## (nullable),
* 10 heading: float #.## (nullable),
* 11 verticalRate: float #.## (nullable),
* 12 sensorSerials: Array[int] (nullable),
* 13 geoAltitude: float #.## (nullable),
* 14 squawk: string (nullable),
* 15 isAlert: bool,
* 16 isSpi: bool,
* 17 positionSource: int 0 for ADS-B, 1 for Asterix, 2 for MLAT
* ]

Detailed documentation will follow as soon as possible!

Cheers,
Marco

This looks very promising. It will close the gaps of unknown squawks in my script for merging OpenSky data with my local dump1090 web interface.
combining OpenSky data with dump1090 webinterface

Thanks for answer

Hey,

just wanted to let you know that the isAlert flag was removed from the state vectors. So now this is the current scheme:

* [
* 0 icao24: string,
* 1 callsign: string (nullable),
* 2 originCountry: string,
* 3 lastPositionUpdate: int (nullable),
* 4 lastContact: int,
* 5 longitude: float #.#### (nullable),
* 6 latitude: float #.#### (nullable),
* 7 baroAltitude: float #.## (nullable),
* 8 isOnGround: bool,
* 9 velocityOverGround: float #.## (nullable),
* 10 heading: float #.## (nullable),
* 11 verticalRate: float #.## (nullable),
* 12 sensorSerials: Array[int] (nullable),
* 13 geoAltitude: float #.## (nullable),
* 14 squawk: string (nullable),
* 15 isSpi: bool,
* 16 positionSource: int 0 for ADS-B, 1 for Asterix, 2 for MLAT
* ]

Sometimes, the squawk seems to be None, although adsb-exchange or flightradar24 provide a squawk value for the given hex ID. It may reappear after a few seconds or minutes.

I can only speculate, but since the squawk is usually way less interrogated than other information, it may take a while for aircraft that just entered our coverage to show a squawk.

Too bad we cannot interrogate aircraft ourselves

That may fit to my observations that this behavior occurs mainly in regions with bad coverage in asia.