Result of update dated 24/10/2019:
Lines restored: Central, HereEast Shuttle, Piccadilly (duplication removed)
Line deleted: Westminster Passenger Service Association
Lines duplicated: District, H37, Metropolitan
Piccadilly: missing Hatton Cross-Heathrow Terminal 4
Result of update dated 29/10/2019 (published 5/11):
Line deleted: HereEast Shuttle
Lines duplicated: Central, District, H37, Metropolitan, Piccadilly
Reverse franchising: East Midlands Railway, LNER, Transport for Wales and West Midland Trains all replaced by their predecessors
H17: inbound (Wembley-Harrow) direction missing
Piccadilly: also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 5/11/2019:
Lines restored: H17, HereEast Shuttle
Lines duplicated: Central, District, H37, Metropolitan, Piccadilly
Reverse franchising: 4 lines replaced by their predecessors
Piccadilly: also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 12/11/2019:
Line restored: H37
Line deleted: 102
Lines duplicated: Central. District, Metropolitan, Piccadilly
Reverse franchising: as before
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
Result of update dated 20/11/2019:
Line restored: 102
Lines duplicated: Central, District, Metropolitan, Piccadilly
Reverse franchising: as before
Piccadilly also missing Hatton Cross-Heathrow Terminal 4
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
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