Handling agencies that don't have stop codes about timetable_cpp HOT 2 CLOSED

In shark, this is almost kind of sorta a configuration. In fact, DoubleMap doesn't even provide stop_codes for CityBus, but I was able to patch it in by looking at the structure of the data coming from from DoubleMap.

This definitely needs to be made configurable in timetable as well to support this use case. As for why stop_code was chosen initially, it was just to make the channel topic more human-readable. UUIDs aren't very human-friendly, making it harder to debug things along the way. At this point, though, I'd be okay with switching over to UUIDs for compatibility.

I think the real question is what makes a good, universal identifier? This is probably different between most agencies out there, so it should be configurable, as mentioned above. But, it also needs to be consistent across the different sources of information for a given agency (GTFS, anything realtime, etc.) so that they can work together and use the same identifiers/channel topics.

In short, the right thing to do is let each system configure it's "primary attribute" for creating an identifier, so that any system with any set of sources can agree on an identification schema.

I don't have an answer for this yet.

from timetable_cpp.

As of #22, we now fall back to using the stop id if a code is unavailable.

from timetable_cpp.