GTFS-ride aggregation and GTFS versioning

[antrim]

More documentation and consideration of how this data should/would be managed, stored, and amended over the course of time would be useful.

• Should GTFS-ride consuming software be able to ingest multiple GTFS-ride feeds and show all data at the same time?
• Is the best practice to collect a growing feed representing all past calendars? Per service period? How does the management of a GTFS-ride feed link up with the ongoing history of a live GTFS feed, with merged calendars, edited calendars, etc.? If GTFS datasets are merged, IDs for calendars and trips may need to be changed.
• What are the implications for managing and publishing GTFS data? Should we have a way of differentiating between when a new dataset (aka feed version) corrects an error in previous data vs. describes an upcoming service change? For some thinking on this, see:
  • Elizabeth Sall's (@e-lo) presentation "Transit Network Version Control"
  • Matthew's (@ODOT-RPTD-mb) comments on GTFS feed start date and end date.