Comment by mslate
7 days ago
While cool, this does not incorporate real-time data, just the static schedule.
I've explored this--you need 511 API access to obtain real-time data, and to conceal your API key you need to stand up a web application.
Cool proof-of-concept, need to take it to the next level!
For anyone interested in getting the aforementioned access, you can find the 511 request URL here: https://www.transit.land/feeds/f-sf~bay~area~rg~rt
GTFS-RT data isn't a lot of fun to work with directly, though, so I'd recommend that you use an intermediary like OneBusAway (OBA) to interpret the data and give you a nicer to use API.
You can find more about OBA here: https://onebusaway.org
and our GitHub organization is here: https://github.com/onebusaway
Our docker images repo has pretty good docs about running a server: https://github.com/OneBusAway/docker
And the SDKs can all be found here: https://developer.onebusaway.org/api/sdk
(n.b. I've been a volunteer on the project for years and am currently serving as the part time exec director of the nonprofit behind OBA.)
I thought about this, but I've seen several times where the signs say that the train is running late, but it's actually there and leaves perfectly on time!
The schedule has been much more reliable since the electrification