Line MAS002:208 has at least one journey where stop(s) are not in NaPTAN
Synthetic stop(s) (49003815690) not found in NaPTAN.
Timing pattern
Arrival | Departure | Stop name |
---|---|---|
0:00:00 | 0:00:00 | *Synthetic Stop |
0:33:00 | 0:33:00 | Synthetic Stop |
0:41:00 | 0:41:00 | Synthetic Stop |
0:43:00 | 0:43:00 | Synthetic Stop |
0:44:00 | 0:44:00 | Synthetic Stop |
0:46:00 | 0:46:00 | Synthetic Stop |
0:49:00 | 0:49:00 | Synthetic Stop |
0:51:00 | 0:51:00 | Synthetic Stop |
0:53:00 | 0:53:00 | Synthetic Stop |
0:54:00 | 0:54:00 | Synthetic Stop |
0:55:00 | 0:55:00 | Synthetic Stop |
0:56:00 | 0:56:00 | Synthetic Stop |
0:57:00 | 0:57:00 | Synthetic Stop |
0:59:00 | 0:59:00 | *Synthetic Stop |
Which journeys have been affected?
1
Total journeys affected
from 06/09/2023
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 "Stop(s) are not found in NaPTAN".
Line | Journey date | Start time | First stop |
---|---|---|---|
MAS002:208 | 06/09/2023 | 15:45 | Synthetic Stop |