Data for Airlines network analysis on an air-rail multimodal system. Journal of Open Aviation Science, 1(2)

<h2>About</h2> <p>This dataset contains all the input data required to generate the analysis and results of the article Delgado, L., Trapote-Barreira, C., Montlaur, A., Bolić, T., &amp; Gurtner, G. (2023).&nbsp;<em>Airlines&rsquo; network analysis on an air-rail multimodal system</em>. Journal of Open Aviation Science, 1(2).&nbsp;<a href="https://doi.org/10.59490/joas.2023.7223" rel="nofollow">https://doi.org/10.59490/joas.2023.7223</a></p> <p>The code used is available on GitHub:&nbsp;<a href="https://github.com/UoW-ATM/joas_air_rail_network_analysis">https://github.com/UoW-ATM/joas_air_rail_network_analysis</a></p> <p>The path to the input data can be modified in the scripts provided in the GitHub repository. With the default setting, the input is in a folder called data.</p> <h2>Dataset structure</h2> <ul> <li>data_computed <ul> <li><em>rail_used_emissions.csv</em></li> <li><em>rail_used_emissions_2.csv</em></li> <li><em>routes_emissinos_v2.csv</em></li> </ul> </li> <li>flights_data4 <ul> <li>year=2023 <ul> <li>month=05 <ul> <li><em>1st_week_0523.csv</em></li> </ul> </li> </ul> </li> </ul> </li> <li>renfe <ul> <li>renfe_mid_long <ul> <li><em>agency.txt</em></li> <li><em>calendar.txt</em></li> <li><em>calendar_dates.txt</em></li> <li><em>routes.txt</em></li> <li><em>stops.txt</em></li> <li><em>stop_times.txt</em></li> <li><em>trips.txt</em></li> </ul> </li> </ul> </li> <li><em>aircraftDatabase.csv</em></li> <li><em>airport_static.csv</em></li> <li><em>code_seats.csv</em></li> <li><em>manual_fixed_airports.csv</em></li> <li><em>mat_corrected.csv</em></li> <li><em>type_code_missing.csv</em></li> </ul> <h2>Data description</h2> <h3>data_computed</h3> <p>This folder contains pre-computed values by the authors on rail and air emissions. These are estimated:</p> <ul> <li>For rail using <a href="http://ecopassenger.hafas.de/" rel="nofollow">EcoPassenger</a>.</li> <li>For flights&nbsp; based on the emission model from Montlaur, A., Delgado, L., &amp; Trapote-Barreira, C. (2021). <a href="https://doi.org/10.3390/su131810401" rel="nofollow"><em>Analytical Models for CO₂&nbsp;Emissions and Travel Time for Short-to-Medium-Haul Flights Considering Available Seats</em></a>. Sustainability 13.18 (2021) and from some specific flights using EUROCONTROL's&nbsp;<a href="https://www.eurocontrol.int/platform/integrated-aircraft-noise-and-emissions-modelling-platform">IMPACT </a>model.</li> </ul> <h3>flights_data4</h3> <p>Information from flights_data4 table from <a href="https://opensky-network.org/data/impala">OpenSky</a>. Please refer to the <a href="https://opensky-network.org/about/terms-of-use">terms of use of OpenSky</a> for the restrictions on the further use of these data.</p> <p>The file <em>1st_week_0523.csv&nbsp;</em>contains the information of the table flights_data4 from OpenSky for the week of the 1st May 2023 (01/05/2023 to 07/05/2003). This was downloaded with the SQL query&nbsp;</p> <p>SELECT * FROM flights_data4 WHERE lastseen &gt;= 1682899200 AND firstseen &lt;= 1683504000;</p> <p>Note that the lastseen and firstseen are in UnixTime and correspond to 2023-05-01 00:00:00 UTC and 2023-05-08 00:00:00 UTC respectively. This ensures capturing all flights landing on 01/05/2023 even if they departed the day before and departing on 07/05/2023 even if landing the day after.</p> <h3>renfe</h3> <p>renfe folder contains the General Transit Feed Specification (GTFS) data from the&nbsp;<a href="https://data.renfe.com/dataset/horarios-de-alta-velocidad-larga-distancia-y-media-distancia">Renfe</a> rail operator with the high-speed, long and medium distances timetables. Note that Renfe provides the data under a <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" rel="noopener">Creative Commons Attribution 4.0</a> license.&nbsp;</p> <h3>Other datasets</h3> <ul> <li><em>aircraftDatabase.csv </em>: Database containing information on aircraft information (type, manufacturer, license, etc.) as a function of their transponder icao24 code. Obtained from <a href="https://opensky-network.org/aircraft-database">OpenSky</a>.</li> <li><em>airport_static.csv</em>: Airport ICAO code, latitude and longitude.</li> <li><em>code_seats.csv</em>: allows each aircraft model to be related to the seats in the cabin. It has been extracted from airline websites and other sources.</li> <li><em>manual_fixed_airports.csv</em>: List of manually modified airports for arrival/departure to fix wrong rotations from OpenSky data. For each airport ICAO code, it provides the one that should be used instead and some information on that airport (e.g., name)</li> <li><em>mat_corrected.csv</em>: identifies the rotation of each aircraft in the week of study. This is especially relevant for fleet analysis as it is necessary to know the start and end airport of each rotation for each day. It has been identified with an ad-hoc algorithm, and some data has been corrected with <a href="https://www.flightradar24.com/">FlightRadar24</a> data support.</li> <li><em>type_code_missing.csv</em>: relates the transponders' icao24 identifiers missing from OpenSky to the aircraft type (complement aircraftDatabase), compiled from <a href="https://www.flightradar24.com/" rel="nofollow">FlightRadar24</a>.</li> </ul>