Frequency type 0 trips must not have delay values

[barbeau]

Summary:

New rule - If a frequency type 0 trip (a trip defined in frequencies.txt with exact_times=0 or empty) TripUpdate has an arrival or departure delay value, this is an error. Arrival and departure times within stop_time_updates for these trips must only have a time value. This is because by definition frequency type 0 trips do not have a schedule, and therefore they can't be "delayed".

cc @scrudden

Steps to reproduce:

Run a feed for a trip defined in frequencies.txt with exact_times=0 or empty that contains an arrival or departure delay in a TripUpdate through the validator

Expected behavior:

Frequency type 0 trips with delay values should be flagged as an error

Observed behavior:

Frequency type 0 trips with delay values are not flagged as an error.

Platform:

N/A

[scrudden]

Have started working on this on this branch.