Inaccurate and missing data

Inaccurate and missing data

Leading to incorrect exit/interchange

For some stations, we have consciously lined up results to the wrong exit, as that would speed up the passenger's journey.

For example, the Victoria line and Jubilee line interchanges for the Piccadilly line at Green Park will both line up with the street-level exit at the ends of the platform rather than the interchange exits, so that the passenger can cut their interchange time by going up to the exit then down to their next platform rather than going through the long tunnel that directly links the platforms.

At the moment this only applies to interchanges to and from the Piccadilly line platforms at Green Park, but this page will be updated if any similar changes are made at other stations.

How to solve this

This is intentional and so will not be changed.

However, some passengers will obviously not know of the quicker interchange route, so you should present some sort of notice next to where you present our data. One way you can phrase this is:

For a quicker interchange at Green Park, follow the signs up to the exit, then make your way to the Jubilee line platform through the main ticket hall.

If you find such errors at stations not listed above, please submit a Github issue so we can resolve this.

Shared tracks and platforms

Due to train lines crossing over, sharing platforms, and sometimes travelling along the same route, it is often difficult to predict at what platform a train will stop. This significantly decreases the quality of our results, meaning you will get less precise exit locations, if any.

How to solve this

Although the line parameter is optional, it will almost always greatly improve results in stations that serve multiple lines and routes. The value of this parameter must be one of the following (as used in the official TfL API):

Type	Values
TfL Underground lines	'bakerloo', 'central', 'circle', 'district', 'hammersmith-city', 'jubilee', 'metropolitan', 'northern', 'piccadilly', 'victoria', 'waterloo-city'
Other TfL services	'dlr', 'london-overground', 'tfl-rail'
National rail services	'chiltern-railways', 'c2c', 'east-midlands-railway', 'gatwick-express', 'great-northern', 'great-western-railway', 'greater-anglia', 'heathrow-express', 'west-midlands-trains', 'south-western-railway', 'southeastern', 'southern', 'thameslink'

Multiple platforms

Platform predictions for stations where one line can use multiple platforms are also less accurate. In this case, results will usually be less precise.

The side property will be set to null if the train doors open on different sides on each platform.

Similarly, the sections, carriage and door properties potentially having a null value if the exits are differently positioned on each platform.

Please note that each of these 3 properties is dependant on the previous property, so we will never return a door value when a carriage value is not set, and never return door or carriage values when sections is not set.

How to solve this

Unfortunately there is nothing you can do to solve this unless you know the specific platform that a train will arrive at.

We, however, have set a few rules that we follow when predicting the platform that a train will stop at.

• We will only take into account timetabled passenger services. This means we will not consider entries to or exits from depots and sidings.
• If platforms are chosen on the go by a signaller, such as at Earl's Court, we will not make a full guess on what platform the train will stop at, but will return the exits if positioned in the same spaces for all platforms.
• If a train can stop at multiple platforms but almost all arrivals arrive at only one of them, for example the Piccadilly line trains being able to use the District line tracks at Acton Town, we will usually assume that the train will arrive at the most used platform.