Relax stop times sequence policy to strictly increasing integers.

[GoogleCodeExporter]

(On behalf of TomH)

In Trapeze, each actual stop pattern comes from (is a subset of) the master
pattern (the entirely of the master pattern may never be used in any actual
stop pattern). The sequence numbers come from the master pattern.

We should only detect a bad sequencing if a stop is missing for all trips
of a route.

An example,
A master pattern and sequencing.
stop_id     sequence
a              1
b              2
c              3
d              4

Applying the master pattern to a trip which only services b-c-d,
stop_id     sequence
b              2
c              3
d              4
will generate a sequence error.

Original issue reported on code.google.com by fredf...@gmail.com on 15 Jun 2007 at 12:00

[GoogleCodeExporter]

Thanks for the report, Fred.  I think this is a pretty good idea, though it will
require a related change to the GTFS spec itself.

Original comment by joe.hugh...@gmail.com on 15 Jun 2007 at 12:10

• Added labels: App-FeedValidator, Language-Python, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Checked in but not released yet.

Original comment by joe.hugh...@gmail.com on 17 Oct 2007 at 7:09

• Changed state: Fixed