OpenMobilityData is a website and API for browsing GTFS and GTFS Realtime feeds. The service was originally known as TransitFeeds. It is no longer maintained, but portions do remain available for users. Learn how OpenMobilityData compares to Transitland.

Brief history of TransitFeeds and OpenMobilityData

TransitFeeds.com was created in 2013 by the Australia-based app-developer Quentin Zervaas. In subsequent years, TransitFeeds grew to catalog GTFS and GTFS Realtime feeds for roughly 1,300 transit agencies. Users could browse GTFS feeds, as well as stops and routes, using the TransitFeeds.com website.

While Transitland was focused at the time on providing a rich set of APIs, TransitFeeds provided an attractive and easy-to-use web interface. TransitFeed service also provided an API for browsing feed records, but no API for GTFS entity-level information.

In 2019, the for-profit TransitScreen and non-profit MobilityData together acquired TransitFeeds.com from Crunchy Bagel, Quentin Zervaas’s app-development business. TransitFeeds.com was rebranded as OpenMobilityData.

Both domain names continue to be in use, so users searching for GTFS feeds on Google may see similar results listed for both TransitFeeds.com and OpenMobilityData.org.

More recently, MobilityData shifted its efforts to developing a new MobilityData Mobility Database service and announced that it would no longer develop OpenMobilityData. They wrote that “we commit to giving 6 months notice once the decision is finalized” to shut down the OpenMobilityData web application.

Is OpenMobilityData still functional?

OpenMobilityData is partially functional as of 2023:

• No feeds have been added to OpenMobilityData since January 2021.
• January 2021 is probably also the last time that feed records were updated with current URLs.
• Static GTFS feeds continue to be fetched for the existing feed records that still have working URLs; we see some feeds fetched as recently as December 2022.
• The API is available but it is not possible for new users to sign up for an API key, as the “sign in with GitHub” button no longer works.
• Users can browse existing feed records by browsing openmobilitydata.org
• Users are directed to MobilityData’s Mobility Database catalogs for more recent links to GTFS feeds.

OpenMobilityData continues to be a useful source for historical GTFS data between approximately 2015 and 2021.

For example, Carole Turley Voulgaris and Charuvi Begwani at the Harvard Graduate School of Design used feed archives from OpenMobilityData, GTFS Data Exchange, and Transitland to analyze when transit agencies adopted GTFS and what characterized the agencies that were quickest to do so.

How does OpenMobilityData license its data?

OpenMobilityData does not provide information about the terms and conditions attached to each GTFS feed, and leaves it as an exercise to its users to figure out the license for each feed.

Transitland provides information about each source feed’s license, terms, and conditions. Use the Transitland v2 REST API to view feed license information and to filter results by license terms.

Users of Transitland APIs are also able to simplify their experience of working with multiple open datasets using the Transitland Terms. By including a single attribution to Transitland and a link to https://www.transit.land/terms, developers are able to meet the attribution requirement for all source feeds.

Transitland’s information about feed-level licensing enables individual users, large organizations, and for-profit businesses to all have confidence in the open-data sources they are consuming.

Feature Comparison