On Jan 25, 11:43*am, MIG wrote:

On 25 Jan, 11:36, Mizter T wrote:

On Jan 25, 10:58*am, MIG wrote:

On 25 Jan, 09:39, wrote:
[snip]
In a phrase "unresolved journeys". OSIs can accidentally create them.

Yes; eg you go from Greenwich to Charing Cross (with a change at
London Bridge), take your snaps of Nelson, then go into the
Underground for a trip to Kew Gardens. *Because Charing Cross is an
OSI, probably with a long timeout, the whole thing ends up as a single
journey which could go beyond the time limit, leaving you with an
unresolved journey and an unstarted journey at Kew, both of which are
charged at maximum. *Once you've got an unresolved journey (I'm pretty
sure) all capping goes out of the window.

No, that's not correct - whilst the 'unresolved' journey (i.e. the
problematic one that has 'timed-out') does not contribute towards the
cap, other journeys that are successfully resolved *do* contribute
towards the cap. And yes, I have experienced this first hand.

Ah right, although reaching a cap on the remaining journeys is
probably that much less likely once the disputed ones don't count
towards it. *I was under the impression that if the system felt that
it didn't know what you'd been up to, it wouldn't know which cap to
apply.

The publicity about touching-in and out is certainly suggestive that
any failure to do so will wreck all capping for the day, though it
doesn't actually explicitly state this. However what appears to happen
in practice is that any unresolved journeys are simply excluded from
the capping calculation.