Transit Operational Data Standard ¶
The Transit Operational Data Standard (TODS) is an open standard for describing how to operate scheduled transit operations which can be used to port scheduled operations between software products (e.g. scheduling systems and CAD/AVL systems), agencies, and more. TODS leverages the existing General Transit Feed Specification (GTFS) and extends it to include information about personnel and non-revenue service.
View the full TODS specification.
Motivation ¶
Transit providers need the systems they use to schedule and operate their service to be interoperable so that they have the flexibility to use various software products and exchange information with other transit operators. Interoperability is best achieved through open standards. The GTFS open standard successfully transmits information useful to transit riders, but is missing key concepts that are necessary for transit providers to operate the service. TODS fills this gap.
TODS is an open standard which extends GTFS to define additional operational details necessary to operate the service such as deadheads and runs.
Does TODS Data have to be Open data?
While GTFS data can and should be public so that riders can learn about service, TODS data is typically not published in order to preserve the privacy of internal operations data.
While the TODS standard itself is an “open standard”, this doesn’t necessitate the data described in TODS to be open.
Who uses TODS? ¶
TODS is used, supported and referenced by transit agencies, technology providers, governments and researchers. Each entry links to its public source and shows the latest TODS version confirmed for it. Using TODS and not listed? Open an issue on GitHub.
supported or in use in progress or recommended
Transit agencies ¶
MBTA (in progress): partial TODS implementations in place (v2.0+)
Keolis Commuter Services (in progress): presented the operator case for TODS (v2.0+)
San Francisco Bay Ferry (WETA): first transit service to use TODS, for non-revenue trip data (v1.0)
Greenlink: exports TODS from Remix into its Navineo CAD/AVL (v1.0)
Technology providers ¶
TMS Online: reads and writes TODS feeds (v1.0)
Swiftly: first to import TODS data, with WETA (v1.0)
Navineo (Equans): TODS datasets part of its standard CAD/AVL offering, in use at Greenlink (v1.0)
HASTUS (GIRO): import/export tools configurable to TODS feeds (v1.0)
Remix (Via): one-click TODS export built with Greenlink and Equans, now including TODS 2.1.0 (v2.1.0)
GMV (in progress): TODS Board backed collaboration on its TODS 2.0 integration (v2.0)
Optibus: imports and exports TODS between scheduling, operations and AVL systems (v2.0+)
TripSpark: supports TODS in Streets product.
In plans, procurement and research ¶
FTA Report No. 267: research report names TODS
MaineDOT: CAD/AVL review names TODS
Caltrans: report recommends formalizing industry commitment to TODS
STLévis: TODS included in a public tender
N-CATT MDIP Translation Guide: procurement guide lists TODS
Triangle Region: Regional Technology Plan names TODS
Polytechnique Montréal: research using TODS for electric bus charging
How do I implement TODS? ¶
If you are transit agency:
- Talk to your current Scheduling and CAD/AVL vendors or
- Include a requirement to use TODS in your next procurement. The Mobility Data Interoperability Principles has sample text for adding TODS and other key interoperability features as RFP requirements in their Interoperable Procurement Resource.
If you are vendor:
- Review the specification and
- Create an development roadmap to adopting it.
Most vendors already read and write to GTFS, so this should be a marginal lift to implement.
Citation ¶
If you use the Transit Operational Data Standard in a report or article, please cite it as follows:
Transit Operational Data Standard Working Group. 2022. Transit Operational Data Standard. Transit Operational Data Standard Board of Directors. https://ods.calitp.org.