MobilityData/awesome-transit

Move or change GTFS Data Exchange to Historical

themonki opened this issue · 5 comments

The site http://www.gtfs-data-exchange.com/ on the secction feed, according to what they have reported on them website, will not be updated feeds:

GTFS Data Exchange Shutting Down

Timeline for shutting down GTFS Data Exchange:

April 1, 2016 - Feed registry and file uploads disabled
May 1, 2016 - Automatic feed updates disabled
July 1, 2016 - API access to feeds disabled.
Sept 1, 2016 - GTFS-Data-Exchange will switch to a minimal index of agencies

I'd vote for leaving it on the list, but clearly marking it as deprecated. Access to historical data via S3 is still available.

Maby addition on section like "Historical feeds" because it continues to have a good list with different agencies.

I opened a PR to move gtfs-data-exchange.com down the list and update its description: #44.

Also, the data isn't easy to access:

Q: What will happen to historical feeds on gtfs-data-exchange?
A: Historic feed archive will be available for research via AWS S3 "requestor pays" policy. The dataset is currently 13k files totaling 93G from 2008 onward. Contact me if you'd like access.

I wonder if that data could be hosted on GitHub instead? To avoid having to pay, you could shard the data across multiple repos (by time/agency).

What is the limit on Github repo sizes?
On Jul 3, 2016 4:54 PM, "Luqmaan Dawoodjee" notifications@github.com
wrote:

I opened a PR to move gtfs-data-exchange.com down the list and update its
description: #44 #44.

Also, the data isn't easy to access:

Q: What will happen to historical feeds on gtfs-data-exchange?
A: Historic feed archive will be available for research via AWS S3
"requestor pays" policy. The dataset is currently 13k files totaling 93G
from 2008 onward. Contact me if you'd like access.

I wonder if that data could be hosted on GitHub instead? To avoid having
to pay, you could shard the data across multiple repos (by time/agency).


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#43 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA4pLZ1-iLrQca2RxTATY0dHnGUFf0b2ks5qSCF0gaJpZM4JDSjk
.