Interesting! This could be really useful for getting better directions on Google Maps, the Transit app etc. in some situations.
Funny you should say that, then, since GoTriangle is asking for feedback on an update of their Regional Transit Technology Plan (see executive summary of recommendation here)!
A lot of the details here are nerdy even by my standards - but here's what I understood as the most important recommendations (click to expand).
| What currently sucks | What’s proposed to change things |
|---|---|
| Bus location tracking, service disruptions etc. are not always reported by every transit agency, tracking systems, or transit-related apps. This seems to be because not every agency has the tools, knowhow, or bandwidth to implement the technology for that consistently. | Enforce standards for how each transit agency digitally represents bus schedules, how real-time updates are reported. Make the schedule-building process less dependent on specific onboard hardware. |
| Transit agencies don’t plan routes, collect data, and measure performance in a standardized way, so they have a hard time sharing information across the Triangle in a timely way | Develop a central portal for data, upkeep for cybersecurity standards etc. for the entire Triangle - and leverage state contracts so that agencies can share the same tools for cheaper. |
| Different agencies collect data from different sources (onboard trackers, manually edited spreadsheets etc.) - and not all apps, backend platforms etc. can handle them | Set up a central custodian who keeps data up to date for the region (and also manages related regional transit-related cybersecurity vulnerabilities). |
| Some systems that let buses in the Triangle have traffic signal priority in some intersections use proprietary systems, and inconsistent standards mean it’s hard to deploy it in more places and still make things work. | Adopt a specific, emerging national standard and do inter-agency tests to make sure it works across multiple agencies as well as with BRT. |
| Different agencies use different fare collection technologies and policies - and they tend to be disconnected from microtransit. | Integrate payment systems across the region, ensure that fare information is a part of transit-tracking data, and ensure that off-board validation and open payment solutions for BRT are supported. |
Note: The table below does not include any personnel changes. It’s likely that the costs will get more expensive if agencies need to hire their own specialists for any of these recommendations - though I’m not sure how likely that would be.
TL/DR: It turns out we don’t have a lot of inter-agency/government collaboration or standardization for transit data, but they’re looking into ways to change that (and that could work really well with what Mitch posted)!