Bakerloo Line - Wrong Paddington!

Good afternoon

When fetching arrivals for a Bakerloo Line train in either direction, Paddington H&C rather than Bakerloo is returned.

Not a massive issue as I can amend it in my processing but wondered if there might be more?!

	"$type": "Tfl.Api.Presentation.Entities.Prediction, Tfl.Api.Presentation.Entities",
	"id": "-217293458",
	"operationType": 1,
	"vehicleId": "236",
	"naptanId": "940GZZLUPAH",
	"stationName": "Paddington (H&C Line)-Underground",
	"lineId": "bakerloo",
	"lineName": "Bakerloo",
	"platformName": "Southbound - Platform 4",
	"bearing": "",
	"destinationNaptanId": "940GZZLUEAC",
	"destinationName": "Elephant & Castle Underground Station",
	"timestamp": "2020-03-07T16:38:02.8987743Z",
	"timeToStation": 291,
	"currentLocation": "At Kilburn Park Platform 2",
	"towards": "Elephant and Castle",
	"expectedArrival": "2020-03-07T16:42:53Z",
	"timeToLive": "2020-03-07T16:42:53Z",
	"modeName": "tube",
	"timing": {
		"$type": "Tfl.Api.Presentation.Entities.PredictionTiming, Tfl.Api.Presentation.Entities",
		"countdownServerAdjustment": "00:00:00",
		"source": "0001-01-01T00:00:00",
		"insert": "0001-01-01T00:00:00",
		"read": "2020-03-07T16:37:55.491Z",
		"sent": "2020-03-07T16:38:02Z",
		"received": "0001-01-01T00:00:00"


Looking into it further it seems that the API is rendering Paddington as Paddington (H&C) and Edgware Road as Paddington (Bakerloo). All a tad strange!



How does this comare to the underlying Trackernet data?

Bakerloo/Paddington -
Bakerloo/EdgewareRoadBakerloo -

@digestif , @briantist

Curious, in the API, /Line/Route and /Line/Timetable both show the same issue for the Bakerloo (PAC/ERB), while the Circle (PAC/PAH/ERC) & Hammersmith and City (PAH/ERC) get it right. If I try to substitute PAC or PAH into the Trackernet URL, I get redirected to PAD, similarly ERC redirects to ERB

1 Like

This is a known issue that I’m looking at with the Trackernet team

1 Like