The National Academies Press

Currently Skimming:

4. Data Structure
Pages 20-40

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 20... ... 4.2 Files and Fields Table 4 through Table 14 correspond to each of the proposed files and list the field names, data types, field descriptions, and external references (where applicable) for each file. 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... ... This should not be deduced from the sequence of previous positions, which clients can compute from previous data. GTFS-Realtime speed Float Optional Momentary speed measured by the vehicle, in meters per second. 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... ... trip_id_performed ID referencing Trips_performed.trip_id_performed Conditionally required Identifies the trip performed. May be null if the fare collection device is NOT located on a vehicle. Read the entire page →
From page 26... ... For example, the fare card ID. balance Float Optional Stored value remaining on an account after the transaction is made. 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... ... schedule_arrival_time POSIX time Optional Scheduled time at which the vehicle arrives at a stop. GTFS schedule_departure_time POSIX time Optional Scheduled time at which the vehicle departs from a stop. Read the entire page →
From page 29... ... transaction_revenue_x Currency Optional Indicates the revenue from a specified fare medium. For example, cash revenue would be represented by the field name transaction_revenue_0. Read the entire page →
From page 30... ... time_period_end POSIX time Required Aggregation period end time. time_period_category Text Optional Indicates a standard time period to aid further aggregation. 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... ... Used if Train_car is not used. bike_rack Enum Optional Indicates if the vehicle has a useable bike rack. 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... ... Field Name Type Required Description External Reference operator_id ID Required Identifies an operator. If possible, this should match other internal agency operator IDs. Read the entire page →
From page 38... ... , data security, runtimes of processes, and hosting. 5.2 Format Validation Tool The Format Validation Tool is used to ensure that the data types in both the Event Data Files and Summary Data Files are useable for data transfer and analysis. Read the entire page →
From page 39... ... REQ. ID REQUIREMENT TEXT 1 The data files, fields, and types shall conform to the proposed data structure. Read the entire page →
From page 40... ... and three Summary Data Files (Stop_visits, Trips_performed, and Station_activities) to the proposed data structure. Read the entire page →

From page 20...

... 4.2 Files and Fields Table 4 through Table 14 correspond to each of the proposed files and list the field names, data types, field descriptions, and external references (where applicable) for each file.

4. Data Structure Pages 20-40

4. Data Structure
Pages 20-40