Canonical GTFS Validator project for schedule (static) files.
feed_info.publisher_name
or agency.agency_id
.#469
#462 #465
#479
#481 #488 #487
#463 #478 #490
You can now run the validator directly on GitHub, see the relevant readme section: https://github.com/MobilityData/gtfs-validator/blob/master/README.md#via-github-actions---run-the-validator-on-any-gtfs-archive-available-on-a-public-url
We now have a local web UI
We now provide Docker images, see https://github.com/orgs/MobilityData/packages/container/gtfs-validator/192493 Release process completely automated, release cycle should be on a fixed schedule now
Our README has been updated.
#387 #423
#394 #429 #433
#395 #438 #439 #443
Extend the number of supported rules to achieve feature parity with the python Google validator for what is strictly in spec.
Complete implementation of CSV validation
Agency related validation
Validate route id reference in trips
Cross validation between agency.txt and routes.txt
Fix for issues #288 and #322
Validate trips.service_id
Validate shape_id references
Feed related validation
Notice format has been reworked
noticeSpecific
object in the JSON outputAdd feature to run the validator with a json configuration file in place of command line arguments
Add a feature to run the validation only on a subset of files
Add GTFS semantics validation
Add documentation detailing implemented rules
Add documentation on how to extend the validation rules
Various bug fixes
First stable release
See the v1.1.0 README for usage information.
Note that command-line parameters in the master branch have changed since this release.
Note: README.md link to GTFS specification schema should point here
First public release
Base validation
Applied to feed_info.txt, agency.txt, stops.txt, routes.txt, trips.txt, pathways.txt and levels.txt
Validation results are visible in the console as well as in result.txt in your output folder. Requires Java 11