Result of update dated 26/2/2019:
Line restored: 405
Lines deleted: 13, N113
Lines duplicated: District, H3, N25, N550, W8, W9
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 26/2/2019:
Line restored: 405
Lines deleted: 13, N113
Lines duplicated: District, H3, N25, N550, W8, W9
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 5/3/2019:
Lines restored: 13, N113
Lines duplicated: District, H3, N25, N63, N550, W8, W9
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 13/3/2019:
Line restored: N63
Lines duplicated: District, H3, N25, N550, W8, W9
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 18/3/2019:
And we’re back to the original bug that started this thread!:
Lines restored: District
Lines with no stopPointSequences: Hammersmith & City, Metropolitan
Lines duplicated: H3, N25, N550, W8, W9
Circle line has no outbound (clockwise) data
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 28/3/2019:
Lines restored: Circle, Hammersmith & City
Line with no stopPointSequences: Metropolitan
Lines deleted in error: 147, 330, N15
Lines duplicated: H3, H37, N25, N550, W8, W9
B13 weirdly split into 5 inbound and 7 outbound sections
Piccadilly line missing Hatton Cross-Heathrow Terminal 4
Tram: missing Beckenham Junction/Elmers End-Croydon (both directions) and Wimbledon-Croydon
Oops, error in my last two posts:
The problem with H&C/Met on 18/3 and Met on 28/3 is a lack of routeSections in /Line/Mode/{modes}/Route, rather than a lack of stopPointSequences
Result of update dated 28/3/2019: (republication on 8/4 after reversion to 18/3 version):
Line restored: Tram
Lines with no routeSections: Hammersmith & City, Metropolitan
Lines deleted in error: 147, 330, N15, N279
Lines duplicated: H3, H37, N25, N550, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 10/4/2019 (published 15/4):
Lines restored: 147, 330, N15, N25, N279, N550
Lines with no route sections: Hammersmith & City, Metropolitan
Lines duplicated: H3, H37, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 16/4/2019:
Lines with no route sections: Hammersmith & City, Metropolitan
Line deleted: N109
Lines duplicated: H3, H37, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 24/4/2019:
Line restored: N109
Lines with no route sections: Hammersmith & City, Metropolitan
Lines deleted: 124, U7
Lines duplicated: H3, H37, W8, W9
405: missing Purley-Redhill in both directions
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 30/4/2019:
Lines restored: 124, 405, U7
Lines with no route sections: Hammersmith & City, Metropolitan
Line duplicated: Central, H3, H37, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 3/5/2019:
Lines with no routeSections: Hammersmith & City, Metropolitan
Lines deleted in error: 65, 71, K3, N65
Line duplicated: Central, H3, H37, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Result of update dated 7/5/2019:
Lines restored: 65, 71, K3, N65
Lines with no routeSections: Hammersmith & City, Metropolitan
Line deleted: 473
Lines duplicated: Central, H3, H37, W8, W9
B13: weirdly split into 5 inbound and 7 outbound sections, also 119 outbound split into three sections
Circle: outbound (clockwise) direction missing, again due to missing routeSections
Piccadilly: line missing Hatton Cross-Heathrow Terminal 4
Could I suggest starting a fresh thread on this as scrolling down on the wrong piece of kit can take forever!
You don’t have ctrl+end?
If I have Ctrl+End on my smartphone, I haven’t found it yet.
I use Chrome on my phone, which gives me scroll bars and a page n/nnn option for jumping into the middle. Some mobile browsers also have an option to tap in the top r.h. corner to jump to top/bottom. That said, if this is a real problem for people, I have no issues with switching to a new thread - probably with a slightly more useful title.
I have not read all the previous 140+ posts over the past 2 years but would be interested to know why updates constantly introduce bizarre route errors which seem to remain until they are noted on here.
Surely it is possible to devise a way of updating a database w/o more than the occasional human error such as a typo?
misar, I think it’s probably because the API presents data accumulated from a number of different sources, each of which has its own update regime. Changes in the underlying systems will produce inconsistencies and conflicts which are then replicated into the view we see through the API.
Following the discussion about the length of this thread, I’m going to start a new one with either a 6 month or 1 year lifetime
New thread:
Problems with /Line/Route/Sequence 16/5/19-31/12/19