The National Academies Press

Currently Skimming:

Pages 18-37

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 18... ... The proposed data structure is relational, with key identifiers that allow users to join data across files. As noted, some transit agencies may opt against using the Event Data Files. Read the entire page →
From page 19... ... Supporting Train_cars Optional Assets that comprise vehicles, such as train cars, with descriptive information. Supporting Vehicle_train_cars Optional Relationships between assets and vehicles. Read the entire page →
From page 20... ... Figure 5. Data structure files and relationships excluding Event Data Files. Read the entire page →
From page 21... ... GTFS-Realtime longitude Float Optional Degrees East, in the WGS-84 coordinate system. GTFS-Realtime gps_quality Enum Optional Indicates the quality of data and communication provided by the GPS. Read the entire page →
From page 22... ... GTFS-Realtime odometer Integer Optional Odometer value, in meters. GTFS-Realtime schedule_deviation Integer Optional Indicates schedule adherence in seconds. Read the entire page →
From page 23... ... 5 - Travel for onroute replacement of breakdown. 6 - Other not in service schedule_relationship Enum Optional Indicates the status of the stop. Read the entire page →
From page 24... ... 4.2.3 Fare_transactions File This file contains timestamped fare transactions with relevant fare media and amount information (Table 6) Read the entire page →
From page 25... ... GTFS group_size Positive integer Optional The number of customers included in the transaction. Table 6. Read the entire page →
From page 26... ... fare_capped Enum Optional Indicates if fare capping is in effect (fare capping options defined by transit agency) Read the entire page →
From page 27... ... In Table 8, transaction_revenue_x and transaction_count_x, each represents eight distinct fields recording transaction revenue and transaction counts for eight potential types of fare media. 4.2.6 Trips_performed File This file contains a record for each trip for each service date, including both scheduled and unscheduled trips as well as in service and not in service trips. Read the entire page →
From page 28... ... dwell Integer Optional Indicates the amount of time a vehicle spent stopped at a stop in seconds. stop_id ID referencing Stops.stop_id Optional Identifies the stop. Read the entire page →
From page 29... ... 7 - Other type. transaction_count_x Non-negative integer Optional Number of fare transactions made by a specified fare medium. Read the entire page →
From page 30... ... number_of_transactions Non-negative integer Optional Number of fare transactions that occurred at a stop. transaction_revenue_x Currency Optional Indicates the revenue from a specified fare medium. Read the entire page →
From page 31... ... vehicle_id ID referencing Vehicles.vehicle_id Required Identifies the vehicle. trip_id_scheduled ID referencing Trips.trip_id in GTFS Optional Identifies the scheduled trip associated with the trip performed. Read the entire page →
From page 32... ... actual_trip_end POSIX time optional Time at which the vehicle arrived at its destination. in_service Enum Optional Indicates status of travel with regard to service. Read the entire page →
From page 33... ... device_type Enum Optional Indicates the type of device. Valid options are: 0 - APC. Read the entire page →
From page 34... ... 1 - Vehicle does not have a useable bike rack. capacity_standing non-negative integer optional Standing capacity of the vehicle set by the manufacturer. Read the entire page →
From page 35... ... 4.2.10 Vehicle_train_cars File This optional file contains information to match individual assets (train cars) to vehicles (train consists) Read the entire page →
From page 36... ... bike_capacity Non-negative integer Optional Number of bike spaces on the train car or asset. bike_rack Enum Optional Indicates if the train car or asset has a useable bike rack. Read the entire page →
From page 37... ... train_car_id ID referencing Train_car.train_car_id Required Identifies a train car or an asset that is a component of the vehicle. order Non-negative integer Optional The assigned order of the train car or asset within the vehicle. Read the entire page →

From page 18...

... The proposed data structure is relational, with key identifiers that allow users to join data across files. As noted, some transit agencies may opt against using the Event Data Files.