Consistent station/stop IDs across OneBusAway and the MTR webmap #11
Description
While the OneBusAway integration is much appreciated and works great with the Android app, building a custom client that uses data from both the webmap (for drawing stations and lines) and OneBusAway (for trip updates) is very frustrating - I have to make a ton of API requests to both servlets to associate a parent station ID from the map with a stop ID in OneBusAway, then query that stop's arrivals just to get the trip ID of an arrival from the map. It also flat out doesn't work in some cases, as only the stops-for-location OBA endpoint is implemented properly, and that doesn't return stops outside of the narrow provided search radius.
An ideal solution to this would be a system where parent stations (those listed on the MTR webmap) would keep their current random IDs, and the OBA stop ID could be that same ID with the platform number appended - station complex 4359E463763C773E on the MTR map would be listed as stops 4359E463763C773E-1 and 4359E463763C773E-2 in OBA. This would be incredibly helpful for building more complex integrations, and would mirror the real-world GTFS paradigms for locations, where parent stations contain "stops" for each train boarding location.
Love the mod, keep up the good work. Never would have thought bringing data from my MC world into OneBusAway would even be possible in the first place (!)