GTFS Feeds

Mobroute and its associated projects (Mobsql and Transito) are designed to be compatible with all standard GTFS static feeds meeting latest specification. A GTFS feed is a ZIP archive containing a number of CSV files indicating transit data - see the specification for more details.

There are namely two providers of GTFS feeds supported by Mobroute, Transito, and Mobsql in current implementation:

  1. Mobility Database GTFS Feeds
  2. Custom GTFS Feeds

Mobility Database GTFS Feeds

The Mobility Database maps numerical positive integer feed IDs to an underlying GTFS ZIP URL and associated metadata. Integration with this provider is builtin to Mobsql, Mobroute, and Transito and is the simplest and recommended way to get started routing. There are over ~1,500 builtin feeds with this provider to choose from and a wide array of data to available globally.

For end-users, utilizing a feed from the Mobility Database is as simple as specifying which GTFS Feed ID to use. You can search for feed IDs to use here on a web UI for the Mobility Database. Additionally, in Transito there is a text search functionality where you can search for which Mobility DB GTFS feed ID to use by keyword.

If you want more information on finding feeds using the Mobility Database, a helpful few links for quickly determining which Mobility Database feed IDs to use for your metro are below:

If you notice a problem with any of Mobility Database feed and its usage with Mobsql, Mobroute or Transito, users are encouraged to file a ticket on the ticket tracker or alternatively you may also address the problem in the underlying mobility-database-catalogs repo.

Custom GTFS Feeds

Custom feeds may be specified as numerical negative integer feed IDs mapped to a user-provided custom GTFS archive (either via a file:// or http(s):// URI). Since the Mobility Database doesn't contain every feed you might want to use, by using a custom feed ID you can use Mobsql/Mobroute's underlying load logic without integration from the Mobility Database.

By convention, using a negative integer for custom GTFS feed IDs provides disambiguation between Mobility Database Feeds & Custom GTFS feeds (which can be used in combination & loaded to your Mobroute's local SQLite database simultaneously).

Currently custom GTFS feeds are supported in Mobsql & Mobroute; support for custom GTFS feeds in Transito is planned for implementation.