DOI: 10.5281/zenodo.4266938
title: Crowdsourced air traffic data from The OpenSky Network 2020

description: <strong>Motivation</strong> The data in this dataset is derived and cleaned from the full OpenSky dataset to illustrate the development of air traffic during the COVID-19 pandemic. It spans all flights seen by the network's more than 2500 members since 1 January 2019. More data will be periodically included in the dataset until the end of the COVID-19 pandemic. <strong>License</strong> See LICENSE.txt <strong>Disclaimer</strong> The data provided in the files is provided as is. Despite our best efforts at filtering out potential issues, some information could be erroneous. Origin and destination airports are computed online based on the ADS-B trajectories on approach/takeoff: no crosschecking with external sources of data has been conducted.<br> Fields <strong>origin</strong> or <strong>destination</strong> are empty when no airport could be found. Aircraft information come from the OpenSky aircraft database. Fields <strong>typecode</strong> and <strong>registration</strong> are empty when the aircraft is not present in the database. <strong>Description of the dataset</strong> One file per month is provided as a csv file with the following features: <strong>callsign</strong>: the identifier of the flight displayed on ATC screens (usually the first three letters are reserved for an airline: AFR for Air France, DLH for Lufthansa, etc.) <strong>number</strong>: the commercial number of the flight, when available (the matching with the callsign comes from public open API) <strong>icao24</strong>: the transponder unique identification number; <strong>registration</strong>: the aircraft tail number (when available); <strong>typecode</strong>: the aircraft model type (when available); <strong>origin</strong>: a four letter code for the origin airport of the flight (when available); <strong>destination</strong>: a four letter code for the destination airport of the flight (when available); <strong>firstseen</strong>: the UTC timestamp of the first message received by the OpenSky Network; <strong>lastseen</strong>: the UTC timestamp of the last message received by the OpenSky Network; <strong>day</strong>: the UTC day of the last message received by the OpenSky Network; <strong>latitude_1</strong>, <strong>longitude_1</strong>, <strong>altitude_1</strong>: the first detected position of the aircraft; <strong>latitude_2</strong>, <strong>longitude_2</strong>, <strong>altitude_2</strong>: the last detected position of the aircraft. <strong>Examples</strong> Possible visualisations and a more detailed description of the data are available at the following page:<br> &lt;https://traffic-viz.github.io/scenarios/covid19.html&gt; <strong>Credit</strong> If you use this dataset, please cite the original OpenSky paper: Matthias Schäfer, Martin Strohmeier, Vincent Lenders, Ivan Martinovic and Matthias Wilhelm.<br> "Bringing Up OpenSky: A Large-scale ADS-B Sensor Network for Research".<br> In<em> Proceedings of the 13th IEEE/ACM International Symposium on Information Processing in Sensor Networks (IPSN)</em>, pages 83-94, April 2014. and the traffic library used to derive the data: Xavier Olive.<br> "traffic, a toolbox for processing and analysing air traffic data."<br> <em>Journal of Open Source Software</em> 4(39), July 2019.<br>