We’re looking to release a new app that includes journey planner functionality next week and it has been getting some more thorough testing.
Something that has been flagged which has not been noticed before (doesn’t necessarily mean it didn’t happen before) is that for some routes the first result has already left, sometimes more than 10 minutes ago. We have not found a pattern to all the journeys where this happens yet, but it almost always seems to happen for routes involving Bank.
The app doesn’t specify a departure time for its journey planner query, but I also reproduced this on the TfL journey planner web app, where an explicit start time is specified. This would appear to be a bug? Can anyone confirm - or has this always been the case?
If this is how the API is intended to function I could filter the results after I get them, but I’d prefer not to as it will reduce the number of results returned for these routes, which sometimes removes a route option.
EDIT - I just randomly tried another route from Amersham to Acton Central and the first train left 19 minutes before the time of the search. Must be a bug - caching issue? Some servers have the incorrect time set?