Xavier Olive
Martin Strohmeier
Jannis Lübbe
2020-09-17
<p><strong>Motivation</strong></p>
<p>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.</p>
<p><strong>License</strong></p>
<p>See LICENSE.txt</p>
<p><strong>Disclaimer</strong></p>
<p>The data provided in the files is provided as is. Despite our best efforts at filtering out potential issues, some information could be erroneous.</p>
<ul>
<li>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.</li>
<li>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.</li>
</ul>
<p><strong>Description of the dataset</strong></p>
<p>One file per month is provided as a csv file with the following features:</p>
<ul>
<li><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.)</li>
<li><strong>number</strong>: the commercial number of the flight, when available (the matching with the callsign comes from public open API)</li>
<li><strong>icao24</strong>: the transponder unique identification number;</li>
<li><strong>registration</strong>: the aircraft tail number (when available);</li>
<li><strong>typecode</strong>: the aircraft model type (when available);</li>
<li><strong>origin</strong>: a four letter code for the origin airport of the flight (when available);</li>
<li><strong>destination</strong>: a four letter code for the destination airport of the flight (when available);</li>
<li><strong>firstseen</strong>: the UTC timestamp of the first message received by the OpenSky Network;</li>
<li><strong>lastseen</strong>: the UTC timestamp of the last message received by the OpenSky Network;</li>
<li><strong>day</strong>: the UTC day of the last message received by the OpenSky Network;</li>
<li><strong>latitude_1</strong>, <strong>longitude_1</strong>, <strong>altitude_1</strong>: the first detected position of the aircraft;</li>
<li><strong>latitude_2</strong>, <strong>longitude_2</strong>, <strong>altitude_2</strong>: the last detected position of the aircraft.</li>
</ul>
<p><strong>Examples</strong></p>
<p>Possible visualisations and a more detailed description of the data are available at the following page:<br>
<<a href="https://traffic-viz.github.io/scenarios/covid19.html">https://traffic-viz.github.io/scenarios/covid19.html</a>></p>
<p><strong>Credit</strong></p>
<p>If you use this dataset, please cite the original OpenSky paper:</p>
<p>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.</p>
<p>and the traffic library used to derive the data:</p>
<p>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>
</p>
https://doi.org/10.5281/zenodo.4088202
oai:zenodo.org:4088202
eng
Zenodo
https://traffic-viz.github.io/scenarios/covid19.html
https://doi.org/10.1109/IPSN.2014.6846743
https://zenodo.org/communities/covid-19
https://doi.org/10.5281/zenodo.3737101
info:eu-repo/semantics/openAccess
Other (Non-Commercial)
aviation
flightlist
ads-b
covid19
Crowdsourced air traffic data from The OpenSky Network 2020
info:eu-repo/semantics/other