About this scorecard
A free, open-source, plain-language data-quality check for a transit agency's GTFS feed. It reads the feed an agency already publishes, runs the same validator the state and the apps use, and turns the result into a grade, the three things to fix, and why each one matters to riders.
Why it exists
A small agency often inherits its GTFS export from a vendor and has no way to know if it is any good. The most common failure is quiet: the feed silently expires and trip planners drop the agency, so riders are told the service does not exist. The official quality reports are thorough but technical. This fills the gap between them and the person at a 20-bus agency who just needs to know what to fix.
It is built first for two people sharing one screen: the transit manager who wants to know where they stand, and the state or program liaison who wants one page open during an agency check-in. A free open dataset now also serves analysts and state programs working across many feeds at once.
How it works
It scores on top of the canonical MobilityData GTFS validator rather than re-validating feeds, and adds the scoring, the trend, the plain-language fixes, and the alerts. The full methodology, with citations, is in docs/rubric.md, and the machine-readable weights are published at scoring.json. It is a data-quality lens, not an official compliance determination.
Who maintains it
Built and maintained by Chelsea Kelly-Reif, starting from the transit systems in Davis, California. It is open source under a public repository; contributions and corrections are welcome, and any agency can ask to be added or removed under the listing and removal policy. Organizations that want to help cover the hosting and data costs can read how on the support page.