hi @nickp
Not sure what happened on your run, but the 220 seems to returning fine now: https://api.tfl.gov.uk/line/220/Route/Sequence/outbound
We’ll take another look at the P12.
Thanks,
James
Thanks @jamesevans :
Result of intermediate update on 8/12/2023:
Line restored: 220
Lines duplicated: B16, C10, EL1, H10, N2, N11, N38, N44, N136, N137
P12/inbound: Clayton Road is not a passenger stop (yet again)
Result of update dated 13/12/2023:
Line restored: P12
Line deleted: 40
Lines duplicated: B16, C10, EL1, H10, H37, N2, N11, N38, N44, N136, N137
63/outbound: Clayton Road is not a passenger stop(yet again, again)
Hi @nickp - thanks for flagging again. We’re going to roll back our data build in the morning and try again to sort out the 40 and 63 as this was meant to be the last data build of 2023.
Many thanks,
James
Hi @jamesevans - I don’t normally comment on the rail data you provide, as it’s such a mess but, if this is to be the last update this year, you might also want to take a look at c2c: the routes via Basildon & Ockendon have gone missing and I can’t see any closure plans for the whole period from now to next year
@jamesevans @geraldbutler
Not entirely confident that it’s the same thing but will there be more updates of the Journey Planner Datastore zip file thus year? Plenty of Christmas Eve and Boxing Day material has been loaded but not a lot for the period between Boxing Day and New Year’s Eve and next to nothing for New Year’s Eve itself.
Hi @mjcarchive - there should be a subsequent upload to London Datastore.
@nickp - we’ll have a look at c2c. Can you please advise what you mean by closure period? Do you mean tube & rail engineering works etc?
Hi @jamesevans ,
What I meant is that the c2c changes would be justified if those particular branches were closed due to engineering works from now until January, but I have not found any evidence of that.
Also I note that there are 15 lines in yesterday’s update whose ValidTo date is on or before the end of the year. These, presumably, will need to be updated before 2nd Jan
LineId, MaxValidTo
110, 2023-12-15 00:00:00
124, 2023-12-14 00:00:00
126, 2023-12-14 00:00:00
17, 2023-12-22 00:00:00
180, 2023-12-16 00:00:00
195, 2023-12-15 00:00:00
246, 2023-12-15 00:00:00
273, 2023-12-14 00:00:00
624, 2023-12-14 00:00:00
638, 2023-12-14 00:00:00
87, 2023-12-30 00:00:00
99, 2023-12-15 00:00:00
central, 2024-01-01 00:00:00
n32, 2023-12-28 00:00:00
n551, 2023-12-31 00:00:00
ah I see - let me see if other schedules come into play after those.
FYI - our rollback should be completed in the next 30 minutes.
Hi @nickp - thanks for the details. I’ve checked and the statuses are below:
110 - new schedule valid from 16/12/2023-23/12/2024
124 - new schedule valid from 15/12/2023-23/12/2024
126 - new schedule valid from 15/12/2023-23/12/2024
17 - new schedule valid from 23/12/2023-23/12/2024
180 - new schedule valid from 16/12/2023-23/12/2024
195 - new schedule valid from 16/12/2023-23/12/2024
246 - new schedule valid from 16/12/2023-23/12/2024
273 - new schedule valid from 15/12/2023-23/12/2024
624 - new schedule valid from 15/12/2023-23/12/2024
638 - new schedule valid from 15/12/2023-23/12/2024
99 - new schedule valid from 16/12/2023-23/12/2024
Central line - new schedule valid from 02/01/2024-23/12/2024
The 99 and N551 will have to be reworked. We’ll get this sorted with the 40 and 63.
Update Unfortunately we can’t rework the N551 the way we wanted. We’ll try to get this resolved as soon as possibly after new year.
So, result of rollback to 6/12/2023, as expected:
Lines restored: 40, 63, H37
Lines duplicated: B16, C10, EL1, H10, N2, N11, N38, N44, N136, N137
P12/inbound: Clayton Road is not a passenger stop
c2c: a different, but still incomplete, set of routes, including the, rather surprising, outbound route Barking>Grays>Upminster (via Chafford Hundred)>Pitsea (via Laindon) [may have been like this anyway prior to the 13/12 changes]
Thanks @nickp - sorry for the flip-flopping, but we’ve just gone live with the fixes mentioned above 
Thanks,
James
OK, result of update dated 14/12 2023:
Line restored: P12
Lines duplicated: B16, C10, EL1, H10, H37, N2, N11, N38, N44, N136, N137
63/inbound: terminates at The Bricklayer’s
c2c: still rubbish, but no worse than all the other rail data, will follow this up in another thread
hi @nickp
I think the 63 has a short school version of the route that starts from St Saviours & St Olaves School and joins the main route at Bricklayer’s Arms / New Kent Road.
I can see that route section along with the main route (St Pancras International Station to Therapia Road) in the inbound response.
I will be looking into c2c / National Rail modes this week, although there are some source data issues (such as NaPTAN 910 dataset) which are a bit deficient at the moment.
Many thanks,
James
Hi @jamesevans
You’re quite right about the 63, my apologies. Blame it on the pre-Christmas rush.
I think the main problem on the rail side is a generic one that applies to other modes as well. You would appear to have some code in your route section analyser that is trying to optimise/simplify the result by eliminating duplicate sections. It isn’t working for several reasons. Firstly, a pair of route sections that start and end at the same locations are not necessarily the same route. Secondly, rail and other modes need treating slightly differently here - if the sections go A>B>C and A>C then for rail this would normally imply the same route with the train not stopping at B in one case, but for other transport modes, particularly bus, this would normally imply two different routes. Thirdly, the code is not tidying up next and previous links when it removes a section. Fourthly, primarily a rail problem, you are reusing section numbers every time you get a new set of input data, which leads to duplication of section numbers
Result of intermediate update on 24/12/2023:
Line restored: EL1
Lines duplicated: B16, C10, H10, H37, N2, N11, N38, N44, N136, N137
Result of intermediate update on 27/12/2023:
Lines duplicated: B16, C10, EL1, H10, H37, N2, N11, N38, N44, N136, N137
1 Like
Result of intermediate update on 31/12/2023:
Line deleted: 87
Lines duplicated: B16, C10, EL1, H10, H37, N2, N11, N38, N44, N136, N137
Thread split to new thread Problems with /Line/Route/Sequence 1/1/2024 to 30/6/2024
This is to keep the thread size manageable