Some civic hacking on the MTA's Real-time Bus Data
- Archival and sharing of Real-time data
- Reporting on the quality, consistency, and availabiity of real-time data from the MTA
- Reporting on "timeliness" of individual bus routes by comparing real-time data to schedules
- Building a more developer-friendly proxy API with good documentation so that third parties can build apps using this real-time data wihtout having to figure out the vendor's undocumented API
Some wishlist items from the Central Maryland Transportation Alliance
- Track the percentage of buses that give users a real-time update vs. a scheduled ETA and hold the MTA accountable for improving on this measure.
- Evaluate the on-time-performance of individual bus routes (scheduled arrival vs. real-time arrivals) and compare that with rider feedback about bus route performance via Rate Your Ride.
- When a service change goes into effect such as the changes this week to the 11 and 20 routes use the real-time data to compare on-time performance pre- and post-service change to see if reliability improved.
- For a given employment hub map the commute shed as defined by the area of points of origin that a commuter could start from and reach the employment destination by a given time (say 9am) within 60 minutes or 90 minutes on public transportation.
- Similar to #3 above, evaluate the on-time-performance and end-to-end run time reductions on a route after bus stops are eliminated or consolidated as was done on the 50, 53, 56, and 59 routes last fall. We'd also like to do this for the Central Light Rail along the Howard Street corridor as signal prioritization and other improvements go into effect over the coming months.