Skip to content

TIDES Tables Schema

Schemas for TIDES suite.

Files in Specification

TIDES consists of a package of files as defined in the following table.

The following table is automatically generated from [tides.spec.json]

name title description required
vehicle-locations Vehicle Locations Timestamped vehicle locations and speeds. False
passenger-events Passenger Events Timestamped passenger-related events, including boardings and alightings. False
fare-transactions Fare Transactions Timestamped fare transaction, associated with devices. False
stop-visits Stop Visits Summarized boarding, alighting, arrival, departure, and other events (kneel engaged, ramp deployed, etc.) by trip and stop for each service date. False
trips-performed Trips Performed Trips performed for each service date. False
station-activities Station Activities Summarized transactions, entries, and exits by stop or station and time period for each service date (for events not associated with a trip). False
devices Devices Measurement devices, such as AVL, APC, and AFC devices, associated with vehicles or stops or stations. False
train-cars Train Cars Assets that comprise vehicles, such as train cars, with descriptive information. False
vehicle-train-cars Vehicle Train Cars Relationships between assets and vehicles. False
vehicles Vehicles Vehicles, including buses and train consists, with descriptive information. False
operators Operators Personnel who operate vehicles. False

File components for TIDES are specified in [tides.spec.json] in a format compatible with the frictionless data data package standard.

Relationships

Files in the TIDES suite are related to each other and other open standards as follows:

Additional Data
Proposed GTFS
GTFS
Summary Files
Event Data
stop_id,trip_id,vehicle_id
stop_id
trip_id
stop_id
service_id
vehicle_id
train_car_id
train_car_id
vehicle_id
vehicle_id
operator_id
stop_times.txt: stop_id,stop_sequence
stop_visits: stop_id,scheduled_stop_sequence
trips.txt
stop_id
stop_times.txt: stop_id,stop_sequence
vehicle_locations: stop_id,scheduled_stop_sequence
stop_times.txt: stop_id,stop_sequence
passenger_events: stop_id,scheduled_stop_sequence
stop_times.txt: stop_id,stop_sequence
fare_transactions: stop_id,scheduled_stop_sequence
devices
operators
train_cars
vehicle_train_cars
vehicles
stop_times.txt
stops.txt
trips.txt
calendar.txt
station_activities
stop_visits
trips_performed
vehicle_locations
passenger_events
fare_transactions
AVL
APC
AFC
Summary Process

Relationship of trip_id_scheduled to GTFS Schedule trip_id

trip_id_scheduled in TIDES and trip_id in GTFS Schedule should be consistent when a performed trip exists in the published GTFS Schedule.

If a trip does not exist in the published GTFS Schedule, trip_id_scheduled values in TIDES do not have any assumed relationship with GTFS.