← Search

Table · dataset · 2015

Modeling Airlines Decisions On Route Selection Using Discrete Choice Models - Data and Supplementary Materials

Listed in DataCite

Description

<p>The supplementary results are documented in Appendix.pdf</p> <p>The following are the data files included in this set;</p> <p>1. finalData****&nbsp;&nbsp; &nbsp;- Has the data processed by applying filters to raw BTS data<br /> 2. airportsList&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;- Identifies the airports included in our network topology<br /> 3. unionSet&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;- Matrix that indicates the set of routes that existed in given years</p> <p>Details of the data files.</p> <p>1. finalData****<br /> This data file includes the filtered data from BTS that we used for our analysis.

The &#39;****&#39; indicator in the&nbsp;name indicates the year for which this data file is created. The included matrix has the following columns:<br /> possRoutes: &nbsp;&nbsp;This is the set of 8646 possible routes, which, if all of them exist, would make for a fully&nbsp;connected network. They are identified by a ten digit code, the first five digits of which are&nbsp;&nbsp;the Airport ID of the origin airport as assigned in the BTS dataset, and the last five digits&nbsp;are the same for the destination airport.<br /> DISTANCE:&nbsp;&nbsp; &nbsp;This is the distance between the airport pairs.<br /> ROUTES: &nbsp; &nbsp; &nbsp; A column that identifies the routes that exist in the given year. &#39;1&#39; indicates the route exists&nbsp;while &#39;0&#39; indicates that it does not.<br /> ADD: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;These are the routes that were added in the current year; they are identified by &#39;1&#39;.<br /> DEL: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;These are the routes that were deleted in the current year; they are identified by &#39;1&#39;.<br /> HUBS: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; These identify the &#39;hub-level&#39; of the route. &#39;0&#39; indicates both the terminal airports on this&nbsp;route are non-hubs, &#39;1&#39; indicates that one of the two airports is a hub, and &#39;2&#39; indicates that&nbsp;both airports are hubs.<br /> DIRECT_COST:&nbsp;&nbsp; &nbsp;This is the direct operating cost on the route.

Read the rest (2 more)

It is calculated as a weighted by number of&nbsp;operations sum using data in the BTS Schedule P-5.2.<br /> SEG_PAX:&nbsp;&nbsp; &nbsp;This is the segment demand the the route as reported in the BTS T-100 dataset.<br /> MKT_PAX:&nbsp;&nbsp; &nbsp;This is the market demand the the route as reported in the BTS T-100 dataset.</p> <p>2. airportsList<br /> This file has three columns. The first column is the airport code, the second column is the five digit airport ID&nbsp;given in the BTS dataset, and the third column identifies (using indicator &#39;1&#39;) if the airport is a hub.</p> <p>3. unionSet<br /> This file identifies the set of routes that existed in the years under consideration.

Each of the columns are&nbsp;for a year and correspond to the &#39;ROUTES&#39; column in the finalData file as described above.</p>

Links

Where it is published

Documentation and papers

Catalogue records · 2

Topics

Stated by source
Mechanical engineering
Provenance · 1 source records, 8 field assertions
SourceKeyLast seenRaw
DataCite10.4231/r74747tg15 d agoJSON v1
FieldAssertionExtractorEvidence
access_levelsource · DataCiteconnector:datacite@1.0.0/data/attributes/rightsList
byte_sizesource · DataCiteconnector:datacite@1.0.0
concepts[field].fos:mechanical-engineeringsource · DataCiteconnector:datacite@1.0.0
descriptionsource · DataCiteconnector:datacite@1.0.0/data/attributes/descriptions
licensesource · DataCiteconnector:datacite@1.0.0/data/attributes/rightsList
publication_datesource · DataCiteconnector:datacite@1.0.0/data/attributes/dates
titlesource · DataCiteconnector:datacite@1.0.0/data/attributes/titles/0/title
version_labelsource · DataCiteconnector:datacite@1.0.0