I’ve come across the following inconsistencies in bus-related data in the Unified API, that I have not been able to resolve on my own understanding:
- 490000345Z, 999188670, 999188661 and 999188652 are all listed as stops on bus routes, but are of type NaptanRailAccessArea and have no child records. I have not seen predictions when querying any of these ids
- 490G000117 is listed as a stop on a bus route, but is of type NaptanRailAccessArea, and has a child record 490000453X which is a NaptanPublicBusCoachTram; should the route be referencing this instead? I have not seen predictions when querying either id
- Several route sequences have a difference between the number of line strings and ordered line routes - e.g. 142 outbound has 1 line string, and 2 ordered line routes. Should there be 2 line strings? Or 1 ordered line route?
- Some stops are not mentioned in any route sequences. e.g. 490000149L has no lines, and is not on any route sequences, yet has live predictions for route 21 inbound. Conversely, stop 490000149Z looks like it is the same stop, has lines and is on the route sequence for route 21 inbound, but has no live predictions.
Is anyone able to shed some light on these? Are they anomalies, or am I missing something?