Result of update dated 26/11/2019:
Line deleted: 406
Lines duplicated: Central, District, Metropolitan, Piccadilly
Reverse franchising: as before
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 27/11/2019:
Lines deleted: 58, 109, 406
Lines duplicated: Central, District, Metropolitan, Piccadilly
Reverse franchising: as before
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 6/12/2019:
Lines restored: 58, 109, 406, District, Metropolitan
Line deleted: U3
Lines duplicated: Central, Piccadilly
Reverse franchising: as before
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 12/12/2019:
Lines restored: East Midlands Railway, LNER, Transport for Wales, U3, West Midlands Trains
Line deleted: 248
Lines duplicated: Central, District, Piccadilly
Line 211/outbound: permanent HTTP error 503 after multiple retries
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 19/12/2019:
Line restored: 248
Lines duplicated: Central, District, Piccadilly
Direction restored: 211/outbound (although the routing is still wrong in both directions between Westminster Abbey and Waterloo - the buses go over Westminster Bridge, not Lambeth Bridge, as verified by on-street signage at the relevant stops and also by riding the route)
Piccadilly: missing Hatton Cross-Heathrow Terminal 4
Results of update dated 23/12/2019:
Lines restored: Central, District, Piccadilly (de-duplicated)
211: routing wrong in both directions between Westminster Abbey and Waterloo - the buses go over Westminster Bridge, not Lambeth Bridge, as verified by on-street signage at the relevant stops and also by riding the route)
Piccadilly: missing Hatton Cross-Heathrow Terminal 4
1 Like
Hi @nickp
Thanks for the heads up on the 211. We’re going to have a look at the data and see if we can rectify this for the next data build.
Thanks,
James
Also, I believe I have made a fix on the Picc line between Hatton Cross & T4. I’ll test this and hopefully we can release this around 7th Jan.
Does this mean https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/P/HTF will then work? It a little annoying not having the Terminal 4 Piccadilly line…
It’s docs says it’s HTF for Terminal 4…
Hi @briantist - it’s not related to the route-section fix, but it appears that the data in the original trackernet documentation is incorrect. The code is HRF.
I can call the T4 predictions as below:
http://cloud.tfl.gov.uk/TrackerNet/PredictionDetailed/P/HRF
Thanks,
James
However, I should caveat that as Heathrow T4 is technically a terminal, it won’t show eastbound predictions until trains come into service on the platform
@jamesevans Thanks for that. Is that the same reason why these codes don’t work? Sorry to ask…
Paddington doesn’t work - https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/D/PAD
Bayswater doesn’t’ even have a Trackernet code+++
Notting Hill Gate doesn’t work - https://api.tfl.gov.uk/TrackerNet/PredictionDetailed/D/NHG
The codes should be as follows:
Paddington (District/Circle): PADc
Bayswater: BAY
Notting Hill: NHG
Thank you @jamesevans for dealing with these. However, you know what they say about people who solve problems… A couple of older threads are about to be bumped.
Best, Nick
Hi @briantist @nickp
We’ve updated the routesections for the Piccadilly Line this afternoon so that it now includes Hatton Cross to T4.
Please let me know if you have any feedback.
James
1 Like
I can see Arnos Grove & Cockfosters trains appear in our data.
I think this is because the train only appears once it has pulled into the station and set it’s new destination ID. This is consistent with the other termini on London Underground.
Thanks,
James
Odd, I’m looking at http://cloud.tfl.gov.uk/TrackerNet/PredictionDetailed/P/HRF and can see the data but the code wasn’t showing it for some reason.
It seems that
$simpleXml = simplexml_load_string($fileContents);
return json_decode(json_encode($simpleXml));
Works differently when there is one platform element, rather than two. I’ve fixed this so I’m pleased to say that the API is working!
We had the same a while back as well I think! The nature of this station is quite different to any other station on the network.
1 Like