View Single Post
  #21   Report Post  
Old April 13th 10, 01:01 PM posted to uk.transport.london
Mizter T Mizter T is offline
external usenet poster
 
First recorded activity at LondonBanter: May 2005
Posts: 6,077
Default Jubilee Line gateline at Stratford is gone!


On Apr 13, 1:45*pm, "Paul Scott"
wrote:

MIG wrote:

On 13 Apr, 13:06, Mizter T wrote:


On Apr 13, 12:58 pm, "Paul Scott"
wrote:


Going back to the original yellow 'interchange validators' having
thought it through again. With extension to the NR routes they do
actually become a major PAYG loophole don't they. Your previous
suggestions about a 'soft exit' cover the situation. Transfer from
LU onto SWT at Wimbledon with a touch on an interchange validator
and the system will treat that as your exit - if you then don't
touch out on exit at an ungated station further down the line
you've saved a few zones. So perhaps most of them will be removed...


Yeah, you see where I'm coming from on that point.


But is it really any different from any other situation of travelling
without a valid ticket? *If you were determined to use that kind of
"loophole"*, you could still touch at the wide gate.


But a touch at a wide gate would be a proper touch out, not one of Mizter
T's 'soft exits'. [...]


If we're referring to a proper "wide aisle gate" (or WAG - LU
terminology!) then yes - it would register as a conclusive touch-out
and end of the journey - albeit one that could be re-opened as a
result of an OSI (e.g. entering the gates at London Bridge tube
station).

[...] If gripped further down the line the 'soft exit' shows up
but your account is still 'pending' a final touch out. IIRC from previous
discussions it will time out eventually?


Yes.


*It's not really a loophole, because it's simply travelling without a
ticket and, if you are gripped, you pays the price.


No, I think unless they've changed something you are still 'touched in'.


Yes.

Others might be able to explain better.


Not sure I've got the energy to invent the requisite terminology at
the moment!

The Oyster card is essentially left in an ambiguous state after
touching on a validator that's configured for (what I've called)
'interchange mode' - the journey may have finished, the journey might
be continuing - if it continues and is inspected, there's no problem
as it is correctly validated. If the journey doesn't continue, the
potential for a continuing journey eventually times out.