The Transit Operational Data Standard is an open standard for representing the transit schedules used by drivers, dispatchers, and planners to carry out transit operations.
We would like to change the copy for the Operational Data Standard website to remove redundancies, organize information logically, and make sure all the information is up-to-date in advance of the planned public launch of ODS. This issue contains updates for the Specification page (spec.md).
Requirements
Remove text under Operational Data Standard and Overview headings
Add text:
Reference
The Operational Data Standard was last updated on April 14, 2022 (v1.0). The full revision history can be accessed here.
Dataset Files
File Name
Description
deadheads.txt
Defines scheduled deadheads contained in a transit feed. (This file is analogous to trips.txt for non-revenue operations.)
ops_locations.txt
Significant operational locations relevant to the performance of vehicle deadheads. (This file is analogous to stops.txt for non-revenue operations.)
deadhead_times.txt
Times that a vehicle arrives at and departs from operational locations for each deadhead. (This file is analogous to stop_times.txt for non-revenue operations.)
runs_pieces.txt
Defines daily personnel schedules within a feed.
run_events.txt
Defines other scheduled activities to be performed by a member of personnel during a run.
If ops_location_id is blank, stop_id is required. If ops_location_id is not blank, stop_id must be blank.
location_sequence
Non-negative Integer
Required
Order of locations, including both operational locations and stops, for a particular deadhead. The values must increase along the trip but do not need to be consecutive.
shape_dist_traveled
Non-negative Float
Optional
Actual distance traveled along the associated shape, from the first location to the location specified in this record.
runs_pieces.txt
Field Name
Type
Required
Description
run_id
ID
Required
Identifies a run.
piece_id
ID
Required
Identifies the piece of the run. The piece_id field must be unique.
start_type
Enum
Required
Indicates whether the piece begins with a deadhead, a revenue trip, or an event.
0 - Deadhead 1 - Trip 2 - Event
start_trip_id
ID referencing deadheads.deadhead_id or trips.trip_id
Required
Identifies the deadhead or trip with which the piece begins.
Identifies the first operational location or stop to be serviced in the first trip of the piece. This field should only be filled out if the piece does not begin at the first stop of the start trip.
end_type
Enum
Required
Indicates whether the piece ends with a deadhead, a revenue trip, or an event.
0 - Deadhead 1 - Trip 2 - Event
end_trip_id
ID referencing deadheads.deadhead_id or trips.trip_id
Required
Identifies the deadhead or trip with which the piece ends.
Identifies the last operational location or stop to be serviced in the last trip of the piece. This field should only be filled out if the piece does not end at the last stop of the end trip.
run_events.txt
Field Name
Type
Required
Description
run_event_id
ID
Required
Identifies a run event.
piece_id
ID referencing runs_pieces.piece_id
Required
Identifies the piece during which the run event takes place.
Overview
We would like to change the copy for the Operational Data Standard website to remove redundancies, organize information logically, and make sure all the information is up-to-date in advance of the planned public launch of ODS. This issue contains updates for the Specification page (spec.md).
Requirements