Sound Transit & Open Transit Data

Sound Transit is leading the region’s effort to gather static (schedules, routes, fares, etc.) and dynamic (real-time and predictive location) transit data and make it accessible to developers and their applications. We work closely with our partner agencies to improve data quality and enhance the scope of what’s offered. More information is available at http://www.soundtransit.org/Open-Transit-Data

Getting started

• Search the forums listed below to get an idea of how this works and what others are working on
• Check out the trending ideas for inspiration: http://onebusaway.ideascale.com/a/ideas/recent/campaign-filter/active
• Request an API Key: Send an email to OBA_API_Key@soundtransit.org. For the moment all we need is your name and email address. Please allow two business days to receive your key

Downloads

• Several of the region's GTFS files are made available via download at: http://www.soundtransit.org/Developer-resources/Data-downloads

• For access to services you will need an API key (see how to request a key above)

Discussion

• If you want to contribute (code) to OneBusAway: https://groups.google.com/forum/#!forum/onebusaway-developers
• If you are an independent user of the OneBusAway code repository: https://groups.google.com/forum/#!forum/onebusaway-users
• If you are writing an “app” using OneBusAway: https://groups.google.com/forum/#!forum/onebusaway-api

Issues

For data issues: you can post them here on github or send an email to Open_Transit_Data@soundtransit.org. When an issue comes in via email, it’s verified for specifications. If it can’t be addressed quickly it will be posted to the github issues list for the community’s benefit.