Standardizing Data for Mobility Management (2013) / Chapter Skim
Currently Skimming:
Pages 27-33
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 27... ...
III. DATA FRAMEWORK AND STATE OF THE PRACTICE Framework Effective mobility management requires a system that facilitates the efficient exchange of information among the multiple parties who are involved in organizing, providing, consuming, and financing local transportation services when the process of obtaining and delivering such transportation crosses organizational boundaries.
|
From page 28... ...
TABLE 1: Characteristics of Service Discovery and Transactional Data Discovery Data Transactional Data Where Used: Transit websites, 2-1-1 and 5-1-1 services, other information and referral services Where Used: Providers of demand response services, either within a single organization or among brokers or providers Tasks: • Service type and characteristics: what type of service is available for a given trip; accessibility, and if reservations are taken/needed (fixed route or some form of demand response) • Temporal factors: when service is offered, how long a trip takes, the timing of transfer connections • Eligibility factors: General public or some subgroup (seniors, Veterans, etc.)
|
From page 29... ...
Discovery Data Transactional Data • A variety of trip planners have been developed over the past decade, with substantial improvements over time. The 51-1 websites tend towards more comprehensive trip planners oriented to the diversity of services they provide.
|
From page 30... ...
using GTFS-based data from the transit agencies in the region, and as such offer a highly relevant model for I&R systems targeted at veterans. However, as discussed previously, there is currently no analogous GTFS data for DRT services, which leaves a major gap in what I&R systems are able to accomplish without special data generation activities aimed at remedying this deficiency.
|
From page 31... ...
develop external interfaces to their products that would enable such standardized data to be exchanged with other applications -- it is an essential pre-requisite to true data interoperability. As a result, those transportation providers intending to implement interoperable scheduling and dispatch systems are currently confronted by a choice between adopting a single software package for all participants -- in a situation where there may already be a multiplicity of software packages used by the participating organizations -- or commissioning the relatively expensive unique or "one-off" development of customized software to enable data exchanges among the different software applications.
|
From page 32... ...
only if that application has dominant market share, and no single demand response software vendor appears to have that level of dominance. In addition, without more in-depth understanding of this specific dictionary approach, it is not clear that it encompasses all of the desirable functionality for data exchange standards.
|
From page 33... ...
clearinghouse defines certain data that both service requesters and service producers must provide. This includes information about the trip itself, the passenger, and the costs of the service.
|
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.