Opal – the recent ticketing overhaul for transport services in NSW has been greeted with a warm welcome from the state’s weary commuters. The concept of one electronic ticket appeals to the masses for its convenience across multi-service travelling (ferry, buses, and trains). But what I find really interesting, and an exciting prospect for the ‘big data’ world, is the sheer volume and granular nature of data that is being captured.
Commuters are required to tap on and tap off, at first glance this seems a simple and almost pre-existing habitual exercise for your frequent travellers. However, upon closer investigation, it begs the question of: what data is being captured? And more importantly, what are the implications?
Well for starters, any given individual with an opal card can login to the opal website and see the location and time of travel for all their given trips.
So there is some supporting evidence for telling your boss that the traffic was truly the reason why you were late and not sleeping in.
Moreover, on a serious note, this has far reaching implications. For one, the transport body can look to investigate trips which are running late, and the periods that they are running the most poorly. This data could not only help in monitoring traffic flows on given days, specific routes and during certain times, but allow for better planning and improving services.
Done correctly and coupled with some basic statistical assumptions, transport could be monitored to see areas that require more services and those areas which are being underutilised, such an analysis would have significant implications in ensuring tax payer money is being maximised and allocated efficiently. Despite still being in its infancy, I remain quite excited at the tantalising prospect of what my simple ‘tapping on and off’ could eventually lead to having a faster trip home.