Notice: GTFS Data Exchange Shutting Down

http://www.gtfs-data-exchange.com/

I started GTFS Data Exchange in 2008 to encourage adoption of the GTFS specification when barely a dozen transit agencies were sharing schedule data. Since then, much has changed as there are over a thousand agencies from almost every country around the world sharing GTFS data. Thus, the time has dome to close the chapter on GTFS-Data-Exchange.

What's next for the Transit Community?

https://transit.land/ has steadily been growing as the reference spot for worldwide GTFS data, and the spot for transit agencies to connect with developers. It is also built to expose schedule data from a single consistent database which makes it even easier for developers to access schedule information. Most importantly though, Transitland has a sponsor, Mapzen, so developers can rely on it where gtfs-data-exchange has always been a side project, and more often than not in recent years, neglected.

Timeline for shutting down GTFS Data Exchange:

April 1, 2016 - Feed registry and manual uploads disabled May 1, 2016 - Automatic feed updates disabled July 1, 2016 - API access to feeds disabled. Sept 1, 2016 - GTFS-Data-Exchange updated w/ a minimal format that provides an index of agencies, and instructions for accessing historical GTFS data for research.

Frequently Asked Questions:

Q: Where should I go to list my transit agencies feed? A: https://transit.land/feed-registry/

Q: What will happen to historical feeds on gtfs-data-exchange? A: They will remain available for research via S3 accessor pays policy. Please contact me if you'd like access.