As an example, when the 45 coming back from Belchertown reaches Studio Arts Building and becomes the 46, two trip stops occur in GTFS at the same time for both 45 and 46 (the end of the 45 trip and the beginning of the 46 trip).
However, the feed only shows this as a departure for the 46, which is correct also.
It'd be nice to be able to store expected differences in a file and check for them before raising errors.
Or perhaps, a generic way to exclude trip ends while parsing the GTFS data would cover most of the cases here. There may not be an efficient way to do that without leveraging a relational database.
As an example, when the 45 coming back from Belchertown reaches Studio Arts Building and becomes the 46, two trip stops occur in GTFS at the same time for both 45 and 46 (the end of the 45 trip and the beginning of the 46 trip). However, the feed only shows this as a departure for the 46, which is correct also.
It'd be nice to be able to store expected differences in a file and check for them before raising errors.