Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future API mitigation #21

Open
E3V3A opened this issue Mar 13, 2018 · 0 comments
Open

Future API mitigation #21

E3V3A opened this issue Mar 13, 2018 · 0 comments
Labels
api The API data sources we use enhancement New feature or request ToDo Things that will be done, eventually. PR welcome!

Comments

@E3V3A
Copy link
Owner

E3V3A commented Mar 13, 2018

In case the FR24 would some day break the API provided by the flightradar24-client, we should consider using alternative sources for our data. One such source could be the OpenSky Network.

Open Air Traffic Tracking Data

The OpenSky Network is a community-based receiver network which continuously collects air traffic surveillance data. Unlike other networks, OpenSky keeps the collected data forever and makes it accessible to researchers. With over 5 trillion ADS-B and Mode S messages collected from more than 1000 sensors around the world, the OpenSky Network exhibits the largest air traffic surveillance dataset of its kind.

Indeed their API look very similar:

Index Property Type Description
0 icao24 string Unique ICAO 24-bit address of the transponder in hex string representation.
1 callsign string Callsign of the vehicle (8 chars). Can be null if no callsign has been received.
2 origin_country string Country name inferred from the ICAO 24-bit address.
3 time_position int Unix timestamp (seconds) for the last position update. Can be null if no position report was received by OpenSky within the past 15s.
4 last_contact int Unix timestamp (seconds) for the last update in general. This field is updated for any new, valid message received from the transponder.
5 longitude float WGS-84 longitude in decimal degrees. Can be null.
6 latitude float WGS-84 latitude in decimal degrees. Can be null.
7 geo_altitude float Geometric altitude in meters. Can be null.
8 on_ground boolean Boolean value which indicates if the position was retrieved from a surface position report.
9 velocity float Velocity over ground in m/s. Can be null.
10 heading float Heading in decimal degrees clockwise from north (i.e. north=0°). Can be null.
11 vertical_rate float Vertical rate in m/s. A positive value indicates that the airplane is climbing, a negative value indicates that it descends. Can be null.
12 sensors int[] IDs of the receivers which contributed to this state vector. Is null if no filtering for sensor was used in the request.
13 baro_altitude float Barometric altitude in meters. Can be null.
14 squawk string The transponder code aka Squawk. Can be null.
15 spi boolean Whether flight status indicates special purpose indicator.
16 position_source int Origin of this state’s position: 0 = ADS-B, 1 = ASTERIX, 2 = MLAT

Here is their github site, and they are mainatined! 🥇

@E3V3A E3V3A added enhancement New feature or request ToDo Things that will be done, eventually. PR welcome! api The API data sources we use labels Mar 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api The API data sources we use enhancement New feature or request ToDo Things that will be done, eventually. PR welcome!
Projects
None yet
Development

No branches or pull requests

1 participant