Open nekohayo opened 7 months ago
I've been working with New England's feeds since I was planning to make an app like this for the New England region before I found this project. The data I found was:
I found when testing with these live feeds, the updates occur MBTA: 5 sec, RIPTA: 20 sec, CTtransit: 5 sec. CTtransit seems to have removed this document, but they used to have a rate limit of 30 seconds, but they may have scraped that requirement. I wasn't getting rate limited with 3 second updates.
For anyone wanting, MBTA is extremely nice in helping developers with lots of documentation: https://www.mbta.com/developers with a responsive mailing list. RIPTA's setup is almost exactly the same as MBTA, just with no documentation or help. :)
I can help be the maintainer for these three GTFS feeds. I'm still currently working on Rhode Island's GTFS feeds being added to OSM very slowly since it's tedious and boring: https://wiki.openstreetmap.org/wiki/User:Sjwhitak/RIPTA_Import_Plan so I'm quite familiar with RIPTA, though I'm a bit less familiar with the other feeds.
Those are very populous cities, and also tend to be tourist attractions, so it might make sense to add them first? I suspect these cities all have open transit data. Looking at OpenMobilityData transit feeds for the USA, I can see:
* [New York](https://transitfeeds.com/search?q=new+york) * [Los Angeles](https://transitfeeds.com/l/154-los-angeles-ca-usa) and surrounding suburbs and counties (as seen in the map and sidebar on the right) - the Los Angeles metropolitan area seems to be a big pile of counties in a trenchcoat, each with their own mini transit system * [Boston](https://transitfeeds.com/search?q=boston) and [Massachusetts](https://transitfeeds.com/search?q=massachusetts) * [San Francisco](https://transitfeeds.com/search?q=san+francisco) and the [Bay Area Transit Authority](https://transitfeeds.com/p/bay-area-transit-authority) * [Seattle](https://transitfeeds.com/search?q=seattle) * others?
BART and Muni (SF) are covered in #162
Maybe a list similar to the one in #114 could be interesting to make.
Created an issue for tracking North American coverage: #201
Added:
In #222 (Sacramento was also added, but had to be temporarily(?) disabled due to some geoblocking issue)
I realized these might work with gtfsproxy (proxy: true) to circumvent the blocking as long as that server is not blocked as well.
Washington DC added in #372
Boston: #344
Seattle: #390
Those are very populous cities, and also tend to be tourist attractions, so it might make sense to add them first? I suspect these cities all have open transit data. Looking at OpenMobilityData transit feeds for the USA, I can see: