Developers please note:
The trip_ids generated by the BART to Antioch system are not coordinated with trip_ids in the BART schedule system. As a result, GTFS-Realtime trip_ids for Pittsburg Center and Antioch stations (in the 600 range) have no match in GTFS. The ‘etd’ command in the BART API is unaffected. Service alerts for the BART to Antioch system are still available.
The Oakland Airport Connector system does not publish real time data for use in GTFS-Realtime or the BART API, but service alerts for the system are still available.
BART worked with Google and an international partnership of transit agencies to create a standard, lightweight way to describe real time arrivals and service advisories. The resulting General Transit Feed Specification - Realtime is built with the General Transit Feed Specification in mind, so if you're already using BART's GTFS Schedules you're good to go!
No registration required
We won't make you jump through hoops to use BART GTFS-Realtime. Just follow our short and simple Developer License Agreement and give our customers good information.
Keep your work up to date
Things change. When they do we'll try to give you plenty of notice through the BART developer email list.
Don't use the official BART logo or system map
Only we get to use official BART trademarks and copyrighted works to let customers know they're getting info directly from BART versus one of the tons of other places that use BART open data. (If you need a BART system map for your project, check out our editable App Map with a CC-By license).
Don't forget about us!
Give us a shout out or a link back and let us know about the cool stuff you're doing.
- What about help?
Sorry: if we help you, it's only fair that we help everyone else, too. We simply don't have the resources for that, beyond our detailed documentation.
- Plans for the future
We're doing our best to add features, fix problems and keep BART developer services reliable. Drop us a line if you have any suggestions.