New thread following on from Problems with /Line/Route/Sequence 16/5/19-31/12/19
Result of update dated 8/1/2020:
Line restored: 211,Piccadilly (finally we can get to Terminal 4, but…)
Line duplicated: Piccadilly
Line 34/outbound: added stop Walthamstow Central Station/AP which no longer exists
Line 107/outbound: HTTP error 503 after multiple retries
hi @nickp
34 Outbound
It appears the stop was left in the Saturday & Sunday night schedules. This has been removed from the source data and should update next week.
107/Outbound
I can’t recreate this - https://api.tfl.gov.uk/Line/107/Route/Sequence/outbound returns a 200 and I can see the route being returned too.
Piccadilly Duplication
I’ve looked at the response of https://api.tfl.gov.uk/Line/piccadilly/route/sequence/outbound?serviceTypes=regular & https://api.tfl.gov.uk/Line/piccadilly/route/sequence/inbound?serviceTypes=regular
I can’t see the duplication you mention - can you share more detail on this?
Thanks,
James
Here’s what I got from the 8/1update. The 100+ numbers are my own renumbering to make duplicates unique. I can send you the raw JSON if you want
Hi @nickp,
Yes, please share the JSON so I can compare it to what I have been looking at.
Are you making these calls or something else?
https://api.tfl.gov.uk/Line/piccadilly/route/sequence/outbound?serviceTypes=regular & https://api.tfl.gov.uk/Line/piccadilly/route/sequence/inbound?serviceTypes=regular
Thanks,
James
The calls are almost like that - they’re actually /Line/{id}/Route/Sequence/{direction}?id=piccadilly&direction=outbound&serviceTypes=Regular&[app keys here] but I can’t see that that should make a difference
The JSON is too large to insert into a post, can I email it to you?
Result of update dated 14/1/2020:
Lines restored: 34, 107
Line duplicated: Piccadilly
Result of update dated 17/1/2020 (published 23/1/2020):
Line duplicated: Piccadilly
Result of update dated 24/1/2020 (published 28/1/2020):
Line restored: Piccadilly
Hallelujah!
@nickp
I was still looking at that issue. Not sure how it has been resolved! Good to see everything is looking good now though. I’ll look into how that’s been restored.
Lol @jamesevans All done by magic! More seriously, this seems to be a recurring problem across the board. I’m guessing that it’s caused by duplicate timetables further up the line that are not successfully being de-duplicated for routeing purposes. I could also point at the branch/rejoin problems and my comments on /timetable in a couple of other threads, as I suspect they are all related…
Ah well, it was too good to last:
Result of update dated 13/2/2020:
Lines deleted: W8, W12
Lines duplicated: H26, N11, N44, N63, N136
Hi Nick,
Both W8 & W12 have now been fixed in the source data and we should be able to resolve this next week with a new reference data build in the API.
I’ll let you know once that has been done.
I’ll have another look into the duplicated routes and let you know how that goes.
Thanks,
James
@nickp
I’ve had a quick look at the H26 and found that the issue is in the TransXChange system too and that there are lots of duplicate Routes (way more than 2 each way!)
<Routes>
<Route id="R_21-H26-_-y05-53644-I-1">
<PrivateCode>R_21-H26-_-y05-53644-I-1</PrivateCode>
<Description>Hatton Cross - Central Parade (TW14)</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-I-1</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-2">
<PrivateCode>R_21-H26-_-y05-53644-O-2</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-2</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-3">
<PrivateCode>R_21-H26-_-y05-53644-O-3</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-3</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-4">
<PrivateCode>R_21-H26-_-y05-53644-O-4</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-4</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-5">
<PrivateCode>R_21-H26-_-y05-53644-O-5</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-5</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-6">
<PrivateCode>R_21-H26-_-y05-53644-O-6</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-6</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-7">
<PrivateCode>R_21-H26-_-y05-53644-O-7</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-7</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-8">
<PrivateCode>R_21-H26-_-y05-53644-O-8</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-8</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-9">
<PrivateCode>R_21-H26-_-y05-53644-O-9</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-9</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-10">
<PrivateCode>R_21-H26-_-y05-53644-O-10</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-10</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-11">
<PrivateCode>R_21-H26-_-y05-53644-O-11</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-11</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-12">
<PrivateCode>R_21-H26-_-y05-53644-O-12</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-12</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-13">
<PrivateCode>R_21-H26-_-y05-53644-O-13</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-13</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-14">
<PrivateCode>R_21-H26-_-y05-53644-O-14</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-14</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-15">
<PrivateCode>R_21-H26-_-y05-53644-O-15</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-15</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-16">
<PrivateCode>R_21-H26-_-y05-53644-O-16</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-16</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-17">
<PrivateCode>R_21-H26-_-y05-53644-O-17</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-17</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-18">
<PrivateCode>R_21-H26-_-y05-53644-O-18</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-18</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-19">
<PrivateCode>R_21-H26-_-y05-53644-O-19</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-19</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-20">
<PrivateCode>R_21-H26-_-y05-53644-O-20</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-20</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-21">
<PrivateCode>R_21-H26-_-y05-53644-O-21</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-21</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-22">
<PrivateCode>R_21-H26-_-y05-53644-O-22</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-22</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-23">
<PrivateCode>R_21-H26-_-y05-53644-O-23</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-23</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-24">
<PrivateCode>R_21-H26-_-y05-53644-O-24</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-24</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-25">
<PrivateCode>R_21-H26-_-y05-53644-O-25</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-25</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-26">
<PrivateCode>R_21-H26-_-y05-53644-O-26</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-26</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-27">
<PrivateCode>R_21-H26-_-y05-53644-O-27</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-27</RouteSectionRef>
</Route>
<Route id="R_21-H26-_-y05-53644-O-28">
<PrivateCode>R_21-H26-_-y05-53644-O-28</PrivateCode>
<Description>Central Parade (TW14) - Hatton Cross</Description>
<RouteSectionRef>RS_21-H26-_-y05-53644-O-28</RouteSectionRef>
</Route>
</Routes>
An example of a good one is 132:
<Routes>
<Route id="R_45-132-_-y05-51934-O-1">
<PrivateCode>R_45-132-_-y05-51934-O-1</PrivateCode>
<Description>North Greenwich Station - Geddes Place</Description>
<RouteSectionRef>RS_45-132-_-y05-51934-O-1</RouteSectionRef>
</Route>
<Route id="R_45-132-_-y05-51934-I-2">
<PrivateCode>R_45-132-_-y05-51934-I-2</PrivateCode>
<Description>Bexleyheath Clocktower - North Greenwich Station</Description>
<RouteSectionRef>RS_45-132-_-y05-51934-I-2</RouteSectionRef>
</Route>
I’m not sure what is causing this, but I’ll speak to the Journey Planner team here about what may be causing this. I imagine there’s a quirk in converting the timetables in the Journey Planner admin system to TransXChange.
More to follow next week…
Hi @jamesevans
Thanks for the info. As regards the H26, I feel that what you are seeing in TransXChange doesn’t quite match up with what’s happening in the API - TXC has 1 outbound (Hatton Cross-Central Parade) and 27 inbound (Central Parade to Hatton Cross) routes, whereas the API has 2 inbound and 2 outbound.
In the API, the two inbound routes are identical, but the outbound ones differ between Harlington Road West and Browells Lane (stop L), reflecting the long-term temporary diversion to the east of Feltham. Interestingly, /Line/Timetable/H26/outbound reflects only the original route, not the diverted one.
My suspicions are that all of the duplications arise from similar such diversions being entered somewhere in the system as additions rather than amendments
Hi All. I’ve had a look at the H26 schedule data and this looks to be a similar issue to that of the W8, I’ve corrected this now and should be in the next TxC upload.
@nickp I have a theory on the root cause of duplicated lines.
I am expecting the issue to occur with the 491 once we’ve built the data and that will confirm my theory.
Watch this space…
Lol, waits with bated breath…
Result of update possibly about 20/2/2020 (still timestamped 13/2/2020):
Timestamp error (see above)
Lines restored: N136, W12
Lines deleted: H26, W8
Lines duplicated: N11, N44, N63