View Single Post
  #19   Report Post  
Old February 15th 08, 10:15 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 Oyster PAYG query

On 15 Feb, 22:46, "Paul Scott" wrote:
Mizter T wrote:

On 15 Feb, 20:30, "Lew 1" wrote:


Unless you are using a tram at Wimbledon, where it all goes out the
window.


I've had no problems at Wimbledon. What problems have you had?
However I am not totally sure of what one should do if they are
changing from National Rail to the LU District line at Wimbledon and
paying for the LU journey with Oyster PAYG. The arrangement certainly
used to be that one could simply touch-in on a standalone Oyster
reader next to the LU District line platforms - however one phrase
from that 'oyster help' page stuck out at me, because it says "Do not
start a pay as you go journey without touching in at the gates at the
entrance to Wimbledon station."


This could indicate that the way things have configured has somehow
changed, however I think it is merely somewhat unclear advice because
otherwise it doesn't make a lot of sense - I strongly suspect that one
can still merely touch-in on one of the standalone Oyster readers next
to the LU District line platforms before one gets on the Underground.
As it happens I will probably be down that way soon and will endeavour
to make a small detour to confirm that this is still the case.


I think you're right, I've used the District line 'platform validators' at
Wimbledon in both directions when changing from LU to NR, a couple of times
this year, seems to work just as you'd expect, same as many other NR/LU
combined stations where access is on the paid side of the gates.

Paul



It's just that oddly worded FAQ answer on the 'oyster help' website
that threw me somewhat. However if it was configured any differently
it would be most odd, and I can't really think of how one would
configure it any differently (at least not in the way that is
suggested by that FAQ answer).