On Jan 12, 4:11*pm, Mizter T wrote:
On 12 Jan, 14:03, "Michael R N Dolbear" wrote:





Mizter T wrote

On a slightly related note, the TfL fare finder appears to return
no fares for Richmond - Clapham Junction journeys.
I wonder what would be charged for an actual PAYG journey (via
Willesden Junction or Earls Court and West Brompton.)

The TfL Fare finder also returns no fares for Kew Gardens - CJ and
Gunnersbury - CJ.

I guess this is either a mistake, or a purposeful omission from the
public Fare finder to try and dissuade people from thinking Oyster
PAYG is valid on the SWT.

Actually I've just checked the Fare finder for a Wimbledon - CJ fare
(via District line and West Brompton) and it does return fares for
that journey, so I dare say the missing fares from Richmond/ Kew
Garden/ Gunnersbury is more likely to be in error.

So yeah, I also wonder how a real journey would be charged.
Essentially depends on whether or not the public Fare finder database
reflects the 'real' Oyster database.

Also, if such a journey was made who would get the money ? and would
SWT get it all next year ?

You raised a similar point in the "Oysterisation" thread so I've
addressed the broad point there.

Good question about what would happen in this situation. One presumes
that a Richmond or Wimbledon to Clapham Jn journey would have to be
charged according to the higher fare NR scale (when using Oyster PAYG)
- though perhaps a very small portion of the money might go to LU
based on the idea that people do take wacky routes, especially ones
that appear on the Tube Map as opposed to ones that don't (and the
direct SWT line doesn't).

A further question would be how would a Richmond to Wimbledon journey
be charged (and resulting revenue distributed) - I can see that some
people would travel by District line all the way, though going by SWT
and changing at CJ would be a far better route. And changing at Putney
for East Putney would avoid going into zone 2 whatsoever.-

If the Putneys became an outerchange, it was raise the old question of
whether touching along the way can override the route assumed by
Oyster between the start and end points (if that was different). That
is, while adjusting to treat two journeys as one continuation, could
it then still use the data about the two journeys to know that the end
to end journey wasn't by a different route?