A General Transit Feed Specification (GTFS) Schedule (static) feed validator, maintained by MobilityData.

Using the Desktop app ● Using the command line ● Using Docker

☑️ List of rules implemented

🤝 Contribute to the project

This README contains information for the latest version of the project, which is under active development. You can find the latest version of the validator application on the Releases page.

This is a cross-platform application written in Java that performs the following steps:

1. Loads input GTFS zip file from a URL or disk.
2. Checks file integrity, numeric type parsing and ranges.
3. Performs complete validation against the GTFS Schedule standard.
4. Provides an easy-to-use validation report in HTML format that can be opened in the browser and shared with other parties. See an example of a validation report. The report is also available in JSON format that can be used for parsing and running additional analyses.

1. Navigate to the Releases page and download the latest Gtfs Validator installer for your operating system:
   • Windows => .msi
   • Mac OS => .dmg
   • Linux => .deb
2. Install application to your workstation.

Once installed, run the application and you will see the following screen:

There are two primary options to set:

• GTFS Input: Use this to specify the GTFS feed to validate. You can specify a URL, ZIP file, or a directory containing the individual .txt files of a feed. You can paste the input location directly into the input field or use the Choose Local File... button to open a file-chooser dialog to select a file on your local system.
• Output Directory: This is the directory where the validation reports will be written.

With these two options set, click the "Validate" button to begin validation.

When validation is complete, the application will automatically open the HTML validation report in your local browser. In addition, the application creates the following files in the output directory:

• report.html: the validation report in HTML format. It can be opened in a browser.
• report.json: the validation report in JSON format.
• system_errors.json: this file will be created every-time the validator is run. If no system errors were encountered, this file will be empty.

Before running validation, tap the Advanced button to configure other aspects of the application, including:

• Number of threads used to run the validator.
• The country code used for phone number validation.

1. Install Java 11 or higher. To check which version of Java is installed on your computer, type the following command in the terminal: java --version.
2. Navigate to the Releases page and download the latest Gtfs Validator CLI jar (not OS-specific). It is located in the Assets section of the release, and it looks like gtfs-validator-vX.X.X_cli.jar
3. Open the terminal on your computer
4. Navigate to the directory containing the jar file. You can do this by typing the following command in the terminal:cd {directory path}, where {directory path} is the absolute or relative path to the directory. You can then make sure you're in the right directory by typing pwd in the terminal (this stands for present working directory). You can also make sure the jar file is there by typing ls in the terminal (this stands for list and will display the list of files in this directory). More about commands to navigate file and directories here.

You can run this validator using a GTFS dataset on your computer, or from a URL.

• To validate a GTFS dataset on your computer, run the following command in the terminal, replacing the text in brackets:

  • java -jar {name of the jar file} -i {path to the GTFS file} -o {name of the output directory that will be created}
  • here is an example of what the command could look like: java -jar gtfs-validator-cli.jar -i /myDirectory/gtfs.zip -o output

• To validate a GTFS dataset from a URL, run the following command in the terminal, replacing the text in brackets:

  • java -jar {name of the jar file} -u {URL to the GTFS file} -o {name of the output directory that will be created}
  • here is an example of what the command could look like: java -jar gtfs-validator-cli.jar -u https://www.abc.com/gtfs.zip -o output

More detailed instructions with all the parameters that exists are available on our "Usage" page.

In the output directory, the reports will be created as described here.

1. Download and install Docker
2. To obtain a validator Docker container image, you have two options:

   • Pull a published Docker container image from GitHub. For example, to pull the latest build of the master branch:

     docker pull ghcr.io/mobilitydata/gtfs-validator:latest

   • Build a Docker container image locally from any branch or working tree:

     docker build . -t ghcr.io/mobilitydata/gtfs-validator:latest

To verify you can run the Docker image in a new container and see the help text:

docker run --rm ghcr.io/mobilitydata/gtfs-validator:latest --help

In order to pass files in and out of the validator, you'll need to use a volume mount to share a directory between your host computer and the Docker container:

docker run --rm -v /myDirectory:/work ghcr.io/mobilitydata/gtfs-validator:latest -i /work/gtfs.zip -o /work/output

where:

• -v /myDirectory:/work: syntax to share directories and data between the container and the host (your computer). With the above command, any files that you place in /myDirectory on the host will show up in /work inside the container and vice versa.

NOTE: On Windows, you must provide the local volume (e.g., c:) as well:

... c:/myDirectory:/work ...

The validator can then be executed via bash commands. See the preceeding instructions for command line usage.

In the output directory, the reports will be created as described here.

• See the list of all the noticed emitted by this validator in RULES.md.
• If you'd like to map notice names between two validator versions, see NOTICE_MIGRATION.md.
• Possible future rules for:
  • GTFS Reference
  • GTFS Best Practices
  • Community rules

Have a suggestion for a new rule? Open an issue. You can see the complete process for adding new rules on the "Adding new rules" page.

• If you'd like to run the bleeding-edge pre-release Snapshot of the application, see the access instructions.
• If you are looking for older releases, see the Releases page.
• If you'd like to view documentation for past releases of the project, see:
  • v1.4.0
  • v2.0.0
  • v3.0.0

We suggest using IntelliJ to import, build, and run this project.

Instructions to build the project from the command-line using Gradle are available in our Build documentation.

The architecture of the gtfs-validator is described on our Architecture page.

In order to avoid sudden changes in the validation output that might declare previously valid datasets invalid, all code changes in pull requests are tested against GTFS datasets in the MobilityDatabase. The acceptance test process is described in ACCEPTANCE_TESTS.md.

CalTrans California Integrated Travel Project (Cal-ITP) GTFS Validator API - A thin wrapper around MobilityData/gtfs-validator.

Code licensed under the Apache 2.0 License.

We welcome contributions to the project! Please check out our Contribution guidelines for details.