Stop(s) are not found in NaPTAN
Operators should notify the relevant Local Transport Authority to request a stop in advance of the timetable being published.This observation identifies cases where a stop used in a timetable is still not in the NaPTAN reference database. Operators should notify the relevant Local Transport Authority immediately to request the stops, notifying them of issues found by this observation.For temporary stops that do not include a reference to NaPTAN, they must be defined geographically using a latitude and longitude in the data. This will support consumers to provide accurate stop information to passengers.
Impacts
NaPTAN provides key stop information across different transport types, enabling multi-modal journey planning that can encourage bus patronage. It is therefore important for the public transport ecosystem to work together to ensure the stop data inputted is correctly detailed and can be referenced to the NaPTAN database.
The following timing pattern(s) have been observed to have stops that are not in NaPTAN.
| Line | Timing pattern (93) |
|---|---|
| — | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| — | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| — | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| 165:Wing Soulbury Turn Opp | There is at least one journey where stop(s) are not in NaPTAN |
| — | There is at least one journey where stop(s) are not in NaPTAN |