Another Oyster problem
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.
|