-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show Santa Monica Big Blue Bus arrivals, on GTFS-realtime #302
Comments
Almost have the interface code working, once I figure out how it works I can try to write interface code, though it may require a fair bit of modification to match how the GTFS server works. |
Ok, looks like problem is that gtfs does everything as one big data dump every like, 30 seconds, and then references things against the schedule, rather than giving you absolute times. This looks like it's going to require a new framework for handling GTFS data. |
trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { trip { |
Ugh. I guess since we have bart on its proprietary deal, we don't really need to Loading and parsing through schedules is going to take way more work than On Mon, Aug 24, 2015 at 5:58 PM, Nighelles David notifications@github.com
|
A good question I think, is are the schedules transient enough to require updating often. We could create a sort of "dummy" server that could act like the servers we already support so that all the GTFS work happens externally. |
It's just text data, I don't think there's really a huge cost to pulling in the entire file compared with how many network calls we're already doing. |
Schedules change every 6 months on Metro. Even with no major service changes, each arrival is often adjusted a few minutes in some direction. But then each individual agency changes their schedule on a different day. So we can't just issue one big update every 6 months. A dummy server would work, if we were to set that up. Not worth it just for BBB, but if we came up with other reasons to use one we might make a big deal out of it in the future. Either way, it's looking like we'd need to maintain a server and up-to-date info to support gtfs. Whereas right now we don't really need to follow any news at all with our supported agencies, since it's rare for stops to be changed. |
I mean, like, downloading the entire schedule when the agency becomes enabled isn't even that much of a delay if you do it while they're still in the selection screen. |
It's not about how long the process would take on-device once we write it. It's about writing a whole table-updating system, showing it to the user, hosting a server, and having to keep our server updated with databases. And all that isn't worth it yet, just for the one gtfs agency we want. So it's like, if we do all that work, then to justify it we'd also need to add offline schedule support to use all the data, and serve up variable messages from the server to use the server more, and a whole load more. If we later want to do those things, then it would be reasonable to set it all up then. But on the near-term, this is an obvious wontfix. |
Huh? Why do we need a server? |
Where are you going to download from? Each individual agency server? That's
|
GTFS has like, a standardized request method for the realtime data, and the GTFS standard is standardized as well. You'd have to do some extra processing like, once a day or something to check if the schedule has changed, but that's not more data than say downloading a webpage on a phone. We can write something like GTFSAgency class that knows how to do the things given the url for the standard server type. |
Unless you really want to avoid doing anything extra on device. |
We already wrote the whole scraper to avoid that. It took 60s to make a db
|
And, I know it's fun to talk about the technical challenge of writing this, If it takes more than the single night Bart took, it's not worth thinking
|
Ping. |
Santa Monica's Big Blue Bus is something like the second biggest transit provider in LA. They enabled realtime predictions this month, using gtfs-realtime. We should support them, and make sure it's easy to add new gtfs providers in the future.
See their dev site: http://gtfs.bigbluebus.com/
The text was updated successfully, but these errors were encountered: