My grand vision was to do a comet-style app where you see the buses "move" towards your position/stop on a Google Map -- but I haven't been able to sit down and design that yet.
They've added a few more endpoints recently:
http://svc.metrotransit.org/NexTrip/help
Although, I am annoyed because:
NexTrip/{ROUTE}/{DIRECTION}/{STOP}
does not accept the same kind of IDs as the main endpoint 'NexTrip/{STOPID}' and also there are not valid {STOP} ids for every stop on a route.
Otherwise the API is a nice service. Previous versions of TCTransit relied on scraping. Dirty, but it still performed nicely.
My grand vision was to do a comet-style app where you see the buses "move" towards your position/stop on a Google Map -- but I haven't been able to sit down and design that yet.
They've added a few more endpoints recently:
http://svc.metrotransit.org/NexTrip/help
Although, I am annoyed because:
NexTrip/{ROUTE}/{DIRECTION}/{STOP}
does not accept the same kind of IDs as the main endpoint 'NexTrip/{STOPID}' and also there are not valid {STOP} ids for every stop on a route.