-
Notifications
You must be signed in to change notification settings - Fork 2
Revisions
It is key important that a revision history exists for the data. The Transitime system is GTFS based but for GTFS there is only a single schedule that is specified. One needs to be able to be able to examine data for old schedules when looking at historic information, such as schedule adherence. One also needs to be able to have multiple revisions available in the database simultaneously because one might need to switch between configurations. For example, there might be a schedule change occurring on Saturday so one needs both the schedule for up to Saturday and the schedule for after Saturday available so that can easily switch between revisions at the appropriate time. Since GTFS data does not contain revision information it is added to all data in the Transitime system.
There are actually two revisions: one for static schedule information and a separate for travel times. In this way one can update travel times without having to duplicate all the static data into a new revision. This significantly saves on database resources.