In message of Wed, 6 Jul
2011 19:56:21 in uk.transport.london, Paul Corfield
writes
On Wed, 06 Jul 2011 02:28:27 -0500,
wrote:


[snip]

Just because there is a fare shown on a tariff for a given zonal
combination does not mean that it applies for every origin and
destination pair when using PAYG. This is why TfL have provided the
Single Fare finder - to make it explicit as to whether there is just
one fare for a journey on a given priced route or if there are options
whereby you may need to interchange at a given point or else use a
route validator.

Paul, Have you any perspective on missing data in the Single Fare
Finder?

I grabbed it in January and so have the following sample information
immediately to hand. No fares are shown between Acton Central and Acton
Town. I tried both Oyster and LU CSCs and got no satisfactory answer.
The Oyster helpline was able to give me missing fares, but could not
explain the absences. 453 locations out of 620 do not have fares with
Crouch Hill. Starts Abbey Wood [National Rail], Acton Main Line
[National Rail], Acton Town. There are even holes in the set Overground
+ Underground. (An example of this would take me longer.)

I got the impression that Colin did not understand my notion of
splitting a journey. If you use PAYG to go between two nodes in zones 1
and 2 in 0430-1900 Mon-Fri in more than 100 minutes and less than 200,
you must pay two fares.

This is usually achievable by touching in at point 1.0 touching out and
in at point 1.4 and touching out at point 2.

I say usually. If there is a self OSI such as at King's Cross St
Pancras, touching out and in does not complete a journey and start a
second. Any applicable OSI vitiates splitting attempts.

Touching out at the same station as you touch in will attract incomplete
and unstarted journey penalties. e.g. Board at Farringdon, go to
Liverpool Street, buy a coffee from the shop on platform 1 and return to
Farringdon. I can't remember the timeout on this. Finsbury Park is a
surprising example of this - I have not tried since FCC platforms got
gates there. ISTR the relevant FPK timeout is 30 minutes.

Occasionally, randomly, unrepeatably and inexplicably (this list is
probably tautological), Oyster decides to ignore a 1.4 stop. I have seen
it do so at London Bridge and Stanmore among others. Stanmore!!!

LU ticket office staff do not seem to have enough power to resolve
overcharging situations. They can remove the marginal fare, but can't
take account of caps. e.g. After I achieved a Z1-2 cap, I wandered past
the gateless inbound validator at Waterloo and was clobbered at Bank. LU
staff cured the 2.50, Oyster helpline the 1.90. Had I realised that I
had not touched in, I could have saved this tedium by touching the bi-
directional validator between Northern and FCC platforms at Moorgate and
out at Moorgate.
--
Walter Briscoe