Problems with /Line/Route/Sequence 1/1/2024 to 30/6/2024

Unified API
1

New thread, following on from Problems with /Line/Route/Sequence 1/7/2023 to 31/12/2023 .
Thread split to keep the size manageable

2

Result of intermediate update on 1/1/2024:

Lines deleted: 87, N551
Lines duplicated: B16, C10, EL1, H10, H37, N2, N11, N38, N44, N136, N137

3

Thanks. We now have new schedules to build those 2 with. We should hopefully get a fix in for tomorrow.

4

hi @nickp - these 2 routes are restored now.

Many thanks,
James

5

Thanks, @jamesevans , and for putting back quite a few of the missing stops mentioned in another thread

Result of update dated 2/1/2024:

Lines restored: 87, B16, C10, H37, N2, N11, N38, N44, N136, N137, N551
Lines duplicated: EL1, H10

638/inbound split into stopping/non-stop sections
P12/inbound: Clayton Road is not a passenger stop (round we go again)

6

Result of intermediate update on 8/1/2024:

Line deleted: 220
Lines duplicated: EL1, H10

638/inbound split into stopping/non-stop sections
P12/inbound: Clayton Road is not a passenger stop

7

Thanks @nickp - it appears the generation of the timetable file for 220 starting today had failed. We’re promoting a datafix for it now. Hopefully this will be available either this afternoon or early tomorrow.

I’ll update here.

Many thanks,
James

8

@nickp - 220 fix is live now. We’re hoping the P12 is fixed again in the weekly databuild.

Thanks,
James

9

Thanks @jamesevans
Result of update dated 8/1/2024:

Line restored: 220
Lines duplicated: EL1, H10

638/inbound split into stopping/non-stop sections
P12/inbound: Clayton Road is not a passenger stop

10

Result of update dated 15/1/2024:

Lines restored: EL1, H10, P12

638/inbound split into stopping/non-stop sections

1 Like
11

thanks @nickp - we should hopefully be fixing the 638 this week

12

Result of update dated 17/1/2024:

Line duplicated: Piccadilly

638/inbound split into stopping/non-stop sections

13

Result of intermediate update on 22/1/2024:

Line deleted: 66
Line duplicated: Piccadilly

638/inbound split into stopping/non-stop sections

14

hi @nickp - we should have a fix in for the 66 and 638 tomorrow

1 Like
15

Thanks, @jamesevans
Result of update dated 24/1/2024:

Lines restored: 66, 638, Piccadilly

nothing else to report at this time!

1 Like
16

Result of update dated 30/1/2024:

Lines duplicated: K1, K2, K3, N65

17

thanks for updating the news
it’s so helpful

18

Result of update dated 1/2/2024:

Lines duplicated: K1, K2, K3, N65

(seems a lot of work, just to add the SL5)

19

Hi @nickp - unfortunately the solution is a big monolith so we can’t release individual schedules/lines into the API. We had to get the SL5 and some underlying tube predictions mappings in so did a separate build for this.

Many thanks,
James

20

Result of update dated 6/2/2024:

Lines duplicated: K1, K2, K3, N65