Roadmap

Canonical GTFS Validator Roadmap

👋 As hosts of the Canonical GTFS Validator, MobilityData, wanted a place share our big picture roadmap for the Validator going forward.

We’d enjoy other contributors adding any major items or vision they want to work on or solve!

• You're welcome to edit this wiki to add items, claim items, or show your interest.
• If you're looking to contribute something more specific have a look at contributing.md.

Features

Test changes on all GTFS datasets

• Need: ensure changes to Validator do not result in a large percentage of previously valid datasets to loose validity.
• Stakeholders: Google suggested. MobilityData plans to implement Q2 2021.

MobilityData plan to leverage the data in the Mobility Archives.

"Profile" structure

• Need: some consumers and regulatory bodies have requirements that go beyond the GTFS spec itself, these are useful for producers to know and test validity against.
• Feature: Allow rules that are not in the spec itself yet are required by various consumers or regulatory bodies. Validator users should be able to toggle to use their choice of additional rules beyond the core in-GTFS-spec rules.
• Stakeholders: Google and Cal-ITP interested. MobilityData plans implement Q2 2021.

Integration into mobility repositories

• Need: data producers and consumers need to identity the validity of data as early as possible.
• Feature: validator should run whenever data is published/ingested into data portals.
• Stakeholders: Cal-ITP interested. MobilityData plans to start running validator on data going into the Mobility Archives as they are populated in Q2 2021.

Results UI

• Need: a way for users to better understand content of the validation report.
• Feature: A web user interface that will present the content of the validation report.
• Stakeholders: Cal-ITP and MobilityData interested.

Validation rules