Line K1:Aylesbury Railway stn has no timing point for more than 15 minutes
Next timing point after Synthetic Stop is missing or is greater than 15 minutes away
Timing pattern
Arrival | Departure | Stop name |
---|---|---|
0:00:00 | 0:00:00 | *Armstrong Fields |
0:02:00 | 0:02:00 | Central Square |
0:03:00 | 0:03:00 | *Synthetic Stop |
0:06:00 | 0:06:00 | Synthetic Stop |
0:08:00 | 0:08:00 | Synthetic Stop |
0:13:00 | 0:13:00 | Synthetic Stop |
0:17:00 | 0:17:00 | Synthetic Stop |
0:21:00 | 0:21:00 | Synthetic Stop |
0:22:00 | 0:22:00 | Synthetic Stop |
0:27:00 | 0:27:00 | Synthetic Stop |
0:29:00 | 0:29:00 | *Central Square |
0:31:00 | 0:31:00 | *Armstrong Fields |
Which journeys have been affected?
6
Total journeys affected
from 22/11/2021
Example vehicle journeys affected
Below is a sample of up to 100 vehicle journeys from your data set that use the above timing pattern. Please refer back to these journeys in your scheduling tool and update the corresponding timetables(s) to address the observation "No timing point for more than 15 minutes".
Line | Journey date | Start time | First stop |
---|---|---|---|
K1:Aylesbury Railway stn | 22/11/2021 | 10:19 | Armstrong Fields |
K1:Aylesbury Railway stn | 22/11/2021 | 11:19 | Armstrong Fields |
K1:Aylesbury Railway stn | 22/11/2021 | 12:19 | Armstrong Fields |
K1:Aylesbury Railway stn | 22/11/2021 | 13:19 | Armstrong Fields |
K1:Aylesbury Railway stn | 22/11/2021 | 14:19 | Armstrong Fields |
K1:Aylesbury Railway stn | 22/11/2021 | 15:19 | Armstrong Fields |