gtfs-analyzer

Validate a GTFS Schedule feed from the command line.

cargo install gtfs-analyzer
gtfs-analyzer validate feed.zip

What it does

• 600+ rules across four classes — Spec conformance, interoperability, data quality and analytics.
• Notices carry remediation: every finding says what is wrong, where, and what to change.
• Scores: a weighted overall score plus a publication score built only from blocker-eligible findings.
• JSON or human-readable output, selectable severity and rule filters.
• Handles large feeds: the archive is read into memory once — the ZIP central directory is at the end, so it has to be — but the row-heavy files are streamed out of it rather than materialised whole. Across the 4,300-feed corpus, peak memory is 14 MiB at the median and 425 MiB at the 95th percentile.

gtfs-analyzer validate feed.zip --json --lang en
gtfs-analyzer validate feed.zip --today 20260820
gtfs-analyzer --version --verbose

--version --verbose prints the package version, commit SHA and provenance source without embedding a wall-clock build timestamp.

Exit code is 0 when the feed is clean, 1 when notices were produced, and 2 on a fatal error.

Accuracy

Every release is measured against the entire MobilityDatabase GTFS Schedule catalogue — over 4,300 real feeds — and compared feed by feed with the reference implementation, MobilityData/gtfs-validator. Divergences are adjudicated and recorded rather than silently accepted.

Library crates

gtfs-core, gtfs-config, gtfs-rules and gtfs-pipeline are published so this binary can be built from crates.io. They are internal to the analyzer and their APIs carry no stability guarantee — depend on them only if you are prepared for breaking changes in patch releases.

License

MIT. Source and issue tracker: https://github.com/ttezer/gtfs-analyzer