Home › Forums › Fare and Capping Queries › Greenwich DLR to national rail
- This topic has 5 replies, 4 voices, and was last updated 9 months, 1 week ago by Mike (admin).
25/08/2022 at 11:27 #4104AllieParticipant
Hi! I’m new here and Mike suggested I reach out here in response to my FOI request at https://www.whatdotheyknow.com/request/greenwich_station_dlr_to_nationa
In my experience, Mike’s suggestion of not tapping any reader doesn’t work and results in two maximum fares. In fairness, it’s been about a year since I’ve tried this – I’m tempted to try again, but waiting until September as I’m already at my three allowed maximum fare corrections for the month (thanks to this station…). I do not believe I’ve exceeded the maximum journey time when doing so. Have others seen this?25/08/2022 at 12:19 #4105FeathersParticipant
I think we can predict what TfLs answer to the posed questions will be because of the way the Oyster system works:
1. You don’t need to tap anything, it should just work (subject to maximum times etc.)
2. It is a valid interchange
You’ll never get a different answer to question 2 since there’s no such thing as valid or an invalid interchanges within a station. The Oyster system doesn’t know where you’ve been, it only knows where you’ve tapped – you could (theoretically) travel by balloon, jet ski or teleportation between stations and, as long as you tapped in and out within the permitted journey times, it would likely be counted as a valid journey.
The real question to answer is what happened in the case of the journeys you tried.
The ‘one tap in the middle’ journey is obvious since you terminated your Oyster trip at Greenwich and didn’t start a new one before getting on a train. Without knowing where you started and finished, however, there’s really very little that anyone can offer.
I have one theory (hence the use of the word ‘likely’ in the balloon paragraph) but I suspect it would look silly once I found out where your journey ended so I’ll hang on to it for the moment.25/08/2022 at 12:24 #4106FeathersParticipant
As an afterthought, I assume you could tap twice on the reader at Greenwich but then you’ll probably be charged for two journeys which will be cheaper than a maximum fare but probably more expensive than a single fare.
(Mike can correct me if there’s some sort of OSI type system that joins up exits and entrances at the same reader.)25/08/2022 at 18:17 #4108MikeModerator
Thanks for dropping by. The reason I suggested potentially exceeding the maximum journey time is because on WDTK you mentioned disruption. On Mondays to Friday daytimes you have 100 minutes to complete a zone 1-2 journey. This should be absolutely plenty of time, but it might depend on where you start and end and how much disruption there is. If you can say what the journey is that would help.
Although TfL limit you to three online corrections to an incomplete journey in a month, you can contact the helpdesk and explain what’s happened and they will correct it for you.
Do you by any chance get emailed statements, or if it’s contactless can you still see the journey history from the last time you didn’t tap? If you can copy/paste the details here that would help.
Feathers: Thanks for your input (I think, really not sure about balloons and jetskis). There’s no OSI in play at Greenwich, but to get two journeys you have to leave two minutes between touches.25/08/2022 at 22:19 #4109AllieParticipant
Hi Mike, generally I’d make this journey if I knew there was disruption on the Jubilee Line. Thus making (DLR station) to Greenwich to London Bridge make more sense than (DLR) to Heron Quays to London Bridge. The revised journey is still well under 100 minutes.
I’ve already had a helpdesk correction this month as well 🙁 (for a river boat journey round trip)
It looks like the journey history for old cards is long gone, but I’ll definitely test again in September!27/08/2022 at 21:53 #4112Mike (admin)Keymaster
So, yesterday I travelled from Crossharbour to London Bridge NR via Greenwich without touching any validators en-route. Here is the journey history:
- You must be logged in to reply to this topic.