Some Tube lines don't have outbound Timetable's

The Hammersmith & City / Circle lines don’t give you any stations/stops/timetable data if you set it up for the outbound direction (?direction=outbound).

Some examples:
https://api.tfl.gov.uk/Line/circle/Timetable/940GZZLUGPS?direction=outbound - This has no stations, no stops. It does have the timetables & the Interval ID. But the array that would normally tell you where the train is going is empty.

Though if you set the direction to inbound: https://api.tfl.gov.uk/Line/circle/Timetable/940GZZLUGPS?direction=inbound you will be able to look at the stations, stops & the Interval ID’s.

This problem exists with the Hammersmith & City line also. (There may be others, but I haven’t seen any yet).

Also the Circle line only has the Timetable for Sunday (its the same on the TFL website https://tfl.gov.uk/tube/timetable/circle?FromId=940GZZLUBST&fromText=Baker+Street+Underground+Station&toText=Edgware+Road+%28Circle+Line%29+Underground+Station&ToId=940GZZLUERC)

Thanks Heaps!

1 Like

Hi,

Yes, this has been the case for a while. The “unified api” tube system is based on incoming data. This is because it mirrors what is shown on departure displays in stations, I think.

You can get around this by using the TrackerNet calls sometimes…

    const CALLFORDETAILSINFO = "https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/";
    $strNewCall = self::CALLFORDETAILSINFO . "{$strTflLineFirstLetter}/{$this->strTFlThreeLetterStatioName}?" . disruptionViews::TFLAPISUFFIX;

Thanks briantist,

Yes I’ve tried using

https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/D/EBY

It shows me the outbound destination for any trains in one of the platforms, but it doesn’t provide a plausible departure time and it doesn’t show outbound destinations for trains yet to arrive [as far as I can tell]. Is that information just not available for this station?

The departure time is in GMT…

Hi briantist,

Thanks for the TrackerNet data.
A couple of questions:

  • Does TrackerNet include DLR, Overground & Trams (or should I use the other system)
  • What is the one letter code for the Circle Line (If i use C it comes up with the central line)

If you don’t know the answers, don’t worry.

Thanks

No problem.

  • Does TrackerNet include DLR, Overground & Trams (or should I use the other system)
  • What is the one letter code for the Circle Line (If i use C it comes up with the central line)

DLR - no use https://api.tfl.gov.uk/line/dlr/arrivals - it returns the whole DLR in a single call.

Overground - best system to use it the “Darwin Push Port”. See https://www.nationalrail.co.uk/100296.aspx and filter for “LO” code.

Trams - not sure, I’ve not used that interface.

Circle Line is got via “H”

https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/H/HST

Hope this helps.

Hi @OscarStickland @briantist

I’m currently investigating the issue of missing route sections for H&C and Circle lines. I believe that I have found the cause in the TransXChange data and we are attempting a fix. I’ll keep you up to date with our progress, but I hope we can fix this issue this week.

Thanks,
James

Even allowing for GMT, the departure time is earlier than the current time, and the train was still in the platform. I’m pretty sure that the ‘departure time’ given in the response is actually the train’s arrival time at Ealing Broadway. I’m not sure if that’s the scheduled, predicted or actual arrival though?

Trains approaching Ealing Broadway are predicted into all three platforms with a departure time that must also be their arrival time I think.

Train 44/6 is timetabled to arrive at 13:17 and depart at 13:28

@briantist
Thanks heaps you’ve been a life saver!