New Journey History with picturesAug 20, 2011
Further to the earlier post I am now able to comment further about the new journey history, and include a screenprint so that others who might not have any recent history can still comment. Oysteronline is very keen to recieve feedback on this project, good or bad. What we are currently seeing is the first beta version which was released at the beginning of August. There is an update due next month which will address some of the issues highlighted in feedback so far. Please keep it coming though, either directly from the Oyster online website, or by replying to this post.
Anyway, onto the screenprint. This is the current last week on my card which demonstrates some of the features and one of the issues so far.
The first thing you notice is that each journey is shown on one line with the actual fare charged instead of the old entry charge and exit adjustment that caused so much confusion. Where text or headings are coloured blue it means that there is a message which can be seen by hovering over the text concerned.
The orange star means that it is possible that not all journeys have reached the central system yet, particularly bus journeys which take a little longer to transfer. This indicator seems to stay for about 3 days, although rail journeys are usually complete by the second day, often the next day.
The green upward pointing arrow with a line above means that the journey triggered the daily cap for the zones covered and may thus be less than expected. The blue circle with an ‘i’ in it indicates that some other information is available by hovering over the line. In the screenprint above, the first and second ones tell me that that journey was zero charged because it was a continuation of the previous journey with no additional payment required. The other two explain that the system is unable to tell where the journey started or finished. Usually that is either because it started within the zones covered by a travelcard, or because the maximum journey time was exceeded or a touch was forgotten or not recorded, resulting in a maximum journey charge. In the example above, however, it is a fault in the handling of the data. The touch in appeared on the history the next day, but the touch out didn’t arrive until the following day. The developers are aware of this and are hoping to fix it with a future release.
I have also taken some other screenshots during the week which include some of the messages shown when you hover over a line. Click on each thumbnail to view the image.