Home |
Search |
Today's Posts |
![]() |
|
London Transport (uk.transport.london) Discussion of all forms of transport in London. |
Reply |
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
![]() |
|||
|
|||
![]()
I mentioned this in another thread here (which I can't find), but it's
happened again... Just back from a recent trip to London, I noticed the balance was £8 less than it should have been. Looked on a ticket machine which stated I'd done the journey: "Heron Quays DLR - Unfinished Unstarted - Woolwich Arsenal" Every single trip to London I have done something similar to this has happened and on every occasion it has involved the DLR at Canary Wharf or Heron Quays. |
#2
![]() |
|||
|
|||
![]() On Jul 9, 12:02*am, Commuter wrote: I mentioned this in another thread here (which I can't find), but it's happened again... Just back from a recent trip to London, I noticed the balance was £8 less than it should have been. Looked on a ticket machine which stated I'd done the journey: "Heron Quays DLR - Unfinished * Unstarted - Woolwich Arsenal" Every single trip to London I have done something similar to this has happened and on every occasion it has involved the DLR at Canary Wharf or Heron Quays. You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. |
#3
![]() |
|||
|
|||
![]()
Mizter T wrote:
You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. Well I'd done the journey Heron Quays to Woolwich Arsenal (changing at Poplar) and touched in at Heron Quays and out at Woolwich Arsenal (ticket barriers). From my statement, the journeys before we "Marble Arch - Tower Hill Marble Arch - Canary Wharf DLR Marble Arch - Canary Wharf" Interesting that it's put Marble Arch - Canary Wharf as two separate journeys when it was only one, but wasn't charged due to price capping which had already been reached. (I had done Marble Arch - Canary Wharf DLR and then entered Canary Wharf LU and exited straight away. I still can't see how it could have happened. Surely if you have an unfinished and an unstarted journey then they are the same journey and should be charged accordingly (due to capping, no price). |
#4
![]() |
|||
|
|||
![]()
On 9 July, 13:26, Commuter wrote:
Mizter T wrote: You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. Well I'd done the journey Heron Quays to Woolwich Arsenal (changing at Poplar) and touched in at Heron Quays and out at Woolwich Arsenal (ticket barriers). *From my statement, the journeys before we "Marble Arch - Tower Hill * Marble Arch - Canary Wharf DLR * Marble Arch - Canary Wharf" Interesting that it's put Marble Arch - Canary Wharf as two separate journeys when it was only one, but wasn't charged due to price capping which had already been reached. (I had done Marble Arch - Canary Wharf DLR and then entered Canary Wharf LU and exited straight away. I still can't see how it could have happened. Surely if you have an unfinished and an unstarted journey then they are the same journey and should be charged accordingly (due to capping, no price). How long did you spend at Canary Wharf? I assume you got there via Jubilee and touched out at the Jubilee station. So the issue may be around whether it was taken as one long interchange and timed you out for the overall journey. In that case it would mean that it took Heron Quays as the start of the last leg (rather than the start of the journey) and that the journey was unfinished because the time from Marble Arch to Woolwich Arsenal was more than two hours (or the time limit at the time) more likely if there is a particularly generous interchange time allowed at Canary Wharf/Heron Quays. The statement is weird, but I think it's been established that inaccuracy in the statement doesn't necessarily imply inaccuracy in the calculation of fares. |
#5
![]() |
|||
|
|||
![]() On Jul 9, 2:11*pm, MIG wrote: On 9 July, 13:26, Commuter wrote: Mizter T wrote: You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. Well I'd done the journey Heron Quays to Woolwich Arsenal (changing at Poplar) and touched in at Heron Quays and out at Woolwich Arsenal (ticket barriers). *From my statement, the journeys before we "Marble Arch - Tower Hill * Marble Arch - Canary Wharf DLR * Marble Arch - Canary Wharf" Interesting that it's put Marble Arch - Canary Wharf as two separate journeys when it was only one, but wasn't charged due to price capping which had already been reached. (I had done Marble Arch - Canary Wharf DLR and then entered Canary Wharf LU and exited straight away. I still can't see how it could have happened. Surely if you have an unfinished and an unstarted journey then they are the same journey and should be charged accordingly (due to capping, no price). How long did you spend at Canary Wharf? *I assume you got there via Jubilee and touched out at the Jubilee station. I assume he got there by DLR - via a Tower Hill to Tower Gateway OSI. So the issue may be around whether it was taken as one long interchange and timed you out for the overall journey. In that case it would mean that it took Heron Quays as the start of the last leg (rather than the start of the journey) and that the journey was unfinished because the time from Marble Arch to Woolwich Arsenal was more than two hours (or the time limit at the time) more likely if there is a particularly generous interchange time allowed at Canary Wharf/Heron Quays. That's my basic thinking on the matter as well (see my other post). The statement is weird, but I think it's been established that inaccuracy in the statement doesn't necessarily imply inaccuracy in the calculation of fares. Yes, but the statement isn't weird actually - at least not the three lines he's provided to us - they make perfect sense. When OSIs are concerned, then the starting station on each line always shows as the original station where the overall journey began (in this case Marble Arch). |
#6
![]() |
|||
|
|||
![]()
On 9 July, 14:24, Mizter T wrote:
On Jul 9, 2:11*pm, MIG wrote: On 9 July, 13:26, Commuter wrote: Mizter T wrote: You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. Well I'd done the journey Heron Quays to Woolwich Arsenal (changing at Poplar) and touched in at Heron Quays and out at Woolwich Arsenal (ticket barriers). *From my statement, the journeys before we "Marble Arch - Tower Hill * Marble Arch - Canary Wharf DLR * Marble Arch - Canary Wharf" Interesting that it's put Marble Arch - Canary Wharf as two separate journeys when it was only one, but wasn't charged due to price capping which had already been reached. (I had done Marble Arch - Canary Wharf DLR and then entered Canary Wharf LU and exited straight away. I still can't see how it could have happened. Surely if you have an unfinished and an unstarted journey then they are the same journey and should be charged accordingly (due to capping, no price). How long did you spend at Canary Wharf? *I assume you got there via Jubilee and touched out at the Jubilee station. I assume he got there by DLR - via a Tower Hill to Tower Gateway OSI. Duh. Yes, that bit where he explicitly mentioned Tower Hill was the clue that I missed. So the issue may be around whether it was taken as one long interchange and timed you out for the overall journey. In that case it would mean that it took Heron Quays as the start of the last leg (rather than the start of the journey) and that the journey was unfinished because the time from Marble Arch to Woolwich Arsenal was more than two hours (or the time limit at the time) more likely if there is a particularly generous interchange time allowed at Canary Wharf/Heron Quays. That's my basic thinking on the matter as well (see my other post). The statement is weird, but I think it's been established that inaccuracy in the statement doesn't necessarily imply inaccuracy in the calculation of fares. Yes, but the statement isn't weird actually - at least not the three lines he's provided to us - they make perfect sense. When OSIs are concerned, then the starting station on each line always shows as the original station where the overall journey began (in this case Marble Arch).- Hide quoted text - - Show quoted text - |
#7
![]() |
|||
|
|||
![]()
I assume he got there by DLR - via a Tower Hill to Tower Gateway OSI.
Yes, that's correct. Marble Arch (touch in) - Tower Hill (touch out); Tower Gateway DLR (touch in) - Westferry - Canary Wharf DLR (touch out). I then did what I had to do in Canary Wharf and went to get the Jubilee Line - noticed the platform was packed and the next train 7 mins away so left the station and walked to Heron Quay and then got DLR to Poplar and then to Woolwich Arsenal. So the issue may be around whether it was taken as one long interchange and timed you out for the overall journey. In that case it would mean that it took Heron Quays as the start of the last leg (rather than the start of the journey) and that the journey was unfinished because the time from Marble Arch to Woolwich Arsenal was more than two hours (or the time limit at the time) more likely if there is a particularly generous interchange time allowed at Canary Wharf/Heron Quays. That's my basic thinking on the matter as well (see my other post). The statement is weird, but I think it's been established that inaccuracy in the statement doesn't necessarily imply inaccuracy in the calculation of fares. Yes, but the statement isn't weird actually - at least not the three lines he's provided to us - they make perfect sense. When OSIs are concerned, then the starting station on each line always shows as the original station where the overall journey began (in this case Marble Arch). Thanks for the explanation both of you, which would also explain why the only times I have had this problem before involve the DLR and the three stations around Canary Wharf. I don't understand though why it happens. It is reasonable to class Marble Arch - Woolwich Arsenal as one journey, but there is no logical reason why anyone would travel through Canary Wharf to do that journey and it should instead be two journeys; Marble Arch - Canary Wharf DLR and Heron Quays DLR - Woolwich Arsenal DLR. |
#8
![]() |
|||
|
|||
![]() On Jul 9, 1:26*pm, Commuter wrote: Mizter T wrote: You're going to have to provide more comprehensive information about what journeys you made if we're going to try and fathom this out. Well I'd done the journey Heron Quays to Woolwich Arsenal (changing at Poplar) and touched in at Heron Quays and out at Woolwich Arsenal (ticket barriers). *From my statement, the journeys before we "Marble Arch - Tower Hill * Marble Arch - Canary Wharf DLR * Marble Arch - Canary Wharf" Interesting that it's put Marble Arch - Canary Wharf as two separate journeys when it was only one, but wasn't charged due to price capping which had already been reached. (I had done Marble Arch - Canary Wharf DLR and then entered Canary Wharf LU and exited straight away. I assume you went from Marble Arch to Tower Hill, then from Tower Gateway DLR to Canary Wharf DLR - in which case the way the system displayed the first two lines is how it always displays journeys that contain Out-of-Station-Interchanges (OSIs) - the starting station to the first exit, then the starting station to the next exit, and so on if there's another OSI involved. The third line also makes sense in that when you entered Canary Wharf LU, it assumed you were continuing your journey from Marble Arch - because it was within a certain time of you touching-out at Canary Wharf DLR and there is an OSI between CW DLR and CW LU stations - and on exiting CW LU having not travelled anywhere then the system counts that as a (non-) journey between CW LU and CW LU and charges the minimum fare from that station (although in your case the fare would not have been charged as you'd reached your cap). The next thing to bear in mind is that there is also an OSI between CW LU and Heron Quays DLR. In every likelihood what has happened is that your original journey from Marble Arch 'timed-out'. The current basic assumption is that overall journeys should take no longer that two-and-a-half hours (originally two hours), however this is to change in September as a more complex system of variable maximum journey times is implemented - and this system is currently being trialled at a number of stations including Canary Wharf DLR and LU stations. This might have meant that 80 minutes was the allowed time for a Marble Arch to Canary Wharf journey, as per this information that Peter Smyth obtained from TfL back in May: http://groups.google.com/group/uk.tr...4747db850d431f I'm not going to pretend that I can piece together exactly what has happened (and whether the above stuff about variable max journey times is relevant), but it seems possible that on touching-in at Heron Quays the system assumed you were continuing your original journey from Marble Arch, that original journey then timed out en-route to Woolwich Arsenal and on exiting you were hit with the £4 'penalty' charge twice for (a) not touching out from your original journey - because it had 'timed-out', and (b) touching-out at Woolwich Arsenal without having touched-in - that's from the system's point of view by the way! I'm not quite sure if that would be the sequence of events though. What would be useful to know is when and where those two £4 charges were applied - does this show up in your journey history at all? (Sometimes it's actually easier to see these things on the journey history screen on a Tube ticket machine.) I still can't see how it could have happened. Surely if you have an unfinished and an unstarted journey then they are the same journey and should be charged accordingly (due to capping, no price). As I said above, it seems likely you've been caught out by the journey 'timing-out'. Whether the trial arrangements for variable maximum journeys times implemented at Canary Wharf LU and DLR stations has something to do with this I can't quite say. One other important question - how long were you around Canary Wharf for, i.e. were there any significant gaps between exiting and entering the CW DLR and/or LU stations and Heron Quays DLR station. And have you any idea of the time of the overall Marble Arch to Woolwich Arsenal journey? I trust you'll get in touch with Oyster customer services about this - you'll get a refund of course, and it should help the Oyster systems bods to identify problem areas and adjust the configuration of the system so as to be able to deal with them. They can be contacted online via a secure web form - go to the TfL website http://www.tfl.gov.uk/, then in the top right click on "Help & Contact" -- "Make a complaint" -- "Oyster" -- "Fares/Refunds" and fill out the form. |
#9
![]() |
|||
|
|||
![]()
Mizter T wrote:
As I said above, it seems likely you've been caught out by the journey 'timing-out'. Whether the trial arrangements for variable maximum journeys times implemented at Canary Wharf LU and DLR stations has something to do with this I can't quite say. One other important question - how long were you around Canary Wharf for, i.e. were there any significant gaps between exiting and entering the CW DLR and/or LU stations and Heron Quays DLR station. And have you any idea of the time of the overall Marble Arch to Woolwich Arsenal journey? I think your explanation is perfectly sound, and whatever the time limit was, it clicked in after leaving Heron Quays, but before Woolwich. If the journey HAD met the time requirements I presume the statement would have been a single journey shown like this, in other words listing the four OSIs passed through as the journey proceeds? Marble Arch - Tower Hill Marble Arch - Canary Wharf DLR Marble Arch - Canary Wharf Marble Arch - Heron Quays Marble Arch - Woolwich Arsenal Having timed out, as we suspect, IMHO a better explanation of what had happened would be if the statement had shown: Marble Arch unfinished Unstarted - Woolwich Arsenal Paul S |
#10
![]() |
|||
|
|||
![]()
On 9 July, 14:54, "Paul Scott" wrote:
Mizter T wrote: As I said above, it seems likely you've been caught out by the journey 'timing-out'. Whether the trial arrangements for variable maximum journeys times implemented at Canary Wharf LU and DLR stations has something to do with this I can't quite say. One other important question - how long were you around Canary Wharf for, i.e. were there any significant gaps between exiting and entering the CW DLR and/or LU stations and Heron Quays DLR station. And have you any idea of the time of the overall Marble Arch to Woolwich Arsenal journey? I think your explanation is perfectly sound, and whatever the time limit was, it clicked in after leaving Heron Quays, but before Woolwich. If the journey HAD met the time requirements I presume the statement would have been a single journey shown like this, in other words listing the four OSIs passed through as the journey proceeds? Marble Arch - Tower Hill Marble Arch - Canary Wharf DLR Marble Arch - Canary Wharf Marble Arch - Heron Quays Marble Arch - Woolwich Arsenal Having timed out, as we suspect, *IMHO a better explanation of what had happened would be if the statement had shown: Marble Arch unfinished Unstarted - Woolwich Arsenal Paul S And we hope that with the changes to take into account cheaper route options, evidenced by touching en route, the system will no longer disregard the fact that it knows where the punter is and will restart the timer as OSIs as well. After all, if you've touched at Heron Quays, there is no possibility that you've spent two hours in the pub at an ungated location, so you aren't the intended catcheree-out of the time limit. It might end up as two journeys instead of one, but I can't see why that isn't possible. |
Reply |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Unusual Oyster PAYG Problem | London Transport | |||
Spammer problem | London Transport | |||
Oyster - the online-bought top-up problem solved | London Transport | |||
Oyster Annual and Extension Tickets - a problem? | London Transport | |||
Bakerloo southbound track problem? | London Transport |