Skip to main content

Currently Skimming:


Pages 28-42

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 28...
... 28 Companies and organizations in many industries use formal data specifications and data standards and commonly agreed upon data formats. This chapter presents five examples of data specifications and common data formats from the transportation industry.
From page 29...
... Examples of Transportation Industry Data Specifications 29 the itinerary was booked on. There was a need to transmit the data for the flights on the other airline(s)
From page 30...
... 30 Development of Transactional Data Specifications for Demand-Responsive Transportation Changes to the data specifications system used by airlines are more complicated today because there are more players in the market than when the PNR system was developed over 50 years ago. While the record systems for airline reservations and PNRs remain proprietary, many other organizations, including online travel agencies such as Expedia or Orbitz, now handle PNR data and need access to airline data to provide consumers with information.
From page 31...
... Examples of Transportation Industry Data Specifications 31 that enables transit organizations to publish the real-time location of their vehicles and their schedule adherence on the web. The example here is focused on the core GTFS system.
From page 32...
... 32 Development of Transactional Data Specifications for Demand-Responsive Transportation static GTFS feeds are then provided directly to Google for use in Google Maps. GTFS datasets are often made public by transit agencies and can usually be downloaded from the internet free of charge.
From page 33...
... Examples of Transportation Industry Data Specifications 33 3.3 Example 3 -- General Transit Feed Specification for Flexible Transit (Publish and Subscribe) This example is an in-progress, proposed extension of GTFS known as the General Transit Feed Specification for Flexible Transit.
From page 34...
... 34 Development of Transactional Data Specifications for Demand-Responsive Transportation will deviate to serve on-demand requests within a service zone encompassing the route. The information that defines the feasible deviations is also accommodated by a change in the "stop_times.txt" file.
From page 35...
... Examples of Transportation Industry Data Specifications 35 The Trip Exchange software was implemented by late 2017 and is in the early stages of use by DRT providers in the northern Denver region. This encompasses an area extending from central Denver northward to Broomfield and Boulder counties, including the city of Longmont.
From page 36...
... 36 Development of Transactional Data Specifications for Demand-Responsive Transportation 3. The Trip Exchange identifies potential matches between providers with capacity and unmet customer travel needs based on the following: date and time of trips, location of providers and trip makers, mobility requirements, and service eligibility.
From page 37...
... Examples of Transportation Industry Data Specifications 37 all essential information that transportation providers need to make a decision about whether they can accommodate the trip, such as pickup and drop-off addresses, requested pickup time, whether the passenger is traveling with a mobility aid such as a wheelchair or walker, and whether they are traveling with companions or service animals. The Trip Exchange has its own data specifications.
From page 38...
... 38 Development of Transactional Data Specifications for Demand-Responsive Transportation they can add a trip to an existing vehicle run, which is important given limited vehicular and driver resources. This supports the goal of providing more rides to more people using existing resources.
From page 39...
... Examples of Transportation Industry Data Specifications 39 throughout Sweden, Norway, Finland, and Denmark for the exchange of DRT information between providers (i.e., contracted vehicle operators) and their clients (i.e., the organizations responsible for DRT services)
From page 40...
... 40 Development of Transactional Data Specifications for Demand-Responsive Transportation device in the vehicle to which the trip has been assigned. The software running on the device can then display the trip information to the driver at the appropriate time.
From page 41...
... Examples of Transportation Industry Data Specifications 41 In every case in which the data standards or specifications advanced, organizations were involved that clearly saw the concrete benefits of such standards and had a financial incentive to support their implementation and further development. For example, the airline industry could not function without the ability of airlines to exchange data on customer itineraries that involve multiple airlines.
From page 42...
... 42 Development of Transactional Data Specifications for Demand-Responsive Transportation Time to Implementation and the Evolution of Specifications Another common theme is the time required for implementation: how long it may take to develop, adopt, and integrate specifications into day-to-day activities and the evolution of specifications (or standards) over time.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.