|
Post by snoggle on Nov 18, 2015 19:04:19 GMT
|
|
|
Post by Nathan on Nov 18, 2015 19:11:13 GMT
Oooh, this is very interesting. I bet they'll be someone out there checking the times religiously, then complaining to the driver when a bus is one min late Having looked at the 172 schedule, I can see that the PDF includes the running numbers, as well as the number of trips per day too. It's also interesting to see that the 171 has separate M-T and F schedules as opposed to M-F
|
|
|
Post by snoggle on Nov 18, 2015 19:15:29 GMT
|
|
|
Post by ServerKing on Nov 18, 2015 19:24:25 GMT
Oooh, this is very interesting. I bet they'll be someone out there checking the times religiously, then complaining to the driver when a bus is one min late You might say that ..... I couldn't possibly comment. Enough about the 192 Sadly, none of the Prefixed routes (i.e C2, E10) are up on the schedule yet, just regular route numbers like 243
|
|
|
Post by Alex on Nov 18, 2015 19:38:01 GMT
Thank you so much for posting!!!! I've been waiting for these for so long, I'd given up that TfL were going to do it. Looks like my evening is sorted lol
|
|
|
Post by thesquirrels on Nov 18, 2015 19:53:41 GMT
Various routes I've keyed in at random not throwing anything up yet e.g. 492, 493, 323.. lower numbers seem to be more or less fully present, though.
|
|
|
Post by Danny on Nov 18, 2015 21:39:50 GMT
|
|
|
Post by snoggle on Nov 18, 2015 22:14:24 GMT
Thanks. That's helpful but it does rather rely on you knowing what daily variants there are for any particular service. Let's hope TfL get the look up interface working properly if all the data is actually there!
|
|
|
Post by paulsw2 on Nov 19, 2015 2:45:41 GMT
Oooh, this is very interesting. I bet they'll be someone out there checking the times religiously, then complaining to the driver when a bus is one min late Having looked at the 172 schedule, I can see that the PDF includes the running numbers, as well as the number of trips per day too. It's also interesting to see that the 171 has separate M-T and F schedules as opposed to M-F That would be down to interworking with night bus
|
|
|
Post by schedcomp on Nov 19, 2015 7:07:22 GMT
Oooh, this is very interesting. I bet they'll be someone out there checking the times religiously, then complaining to the driver when a bus is one min late Having looked at the 172 schedule, I can see that the PDF includes the running numbers, as well as the number of trips per day too. It's also interesting to see that the 171 has separate M-T and F schedules as opposed to M-F That would be down to interworking with night bus Whilst this is probably correct, many operators give increased running times on Friday evening, after around 1900-2100 until end of service. I suspect this route is for both reasons.
|
|
|
Post by eggmiester on Nov 20, 2015 1:56:18 GMT
Different Friday schedules are indeed normally due to the variations in night bus cross links.
|
|
|
Post by northken on Nov 20, 2015 17:59:12 GMT
I like how how they've devised their own form of telling the time, with some buses arriving back at their garages at "25:17".
|
|
|
Post by VPL630 on Nov 20, 2015 18:28:18 GMT
I like how how they've devised their own form of telling the time, with some buses arriving back at their garages at "25:17". It makes a lot of sense to us and operation people, it saves confusion etc
|
|
|
Post by schedcomp on Nov 20, 2015 18:31:01 GMT
I like how how they've devised their own form of telling the time, with some buses arriving back at their garages at "25:17". TfL system is to a 36 hour clock. There needs to be a simple way of differentiating between a bus leaving garage at 4am but returning at 2am the next morning. Night buses will thus include times at 2900. The N9 may push 3200.
|
|
|
Post by snoggle on Nov 20, 2015 18:32:44 GMT
I like how how they've devised their own form of telling the time, with some buses arriving back at their garages at "25:17". Pretty much standard practice on transport systems where an operational day can be longer than 24 hours. Years and years ago I was dealing with 26.5 hour days when creating data for LU's ticketing system.
|
|