I had assumed Google Maps just knew I’d want to use a car. I’ve used Google Maps through a web browser on my laptop a few times a week for what must be years.
And every time I ask it to give me directions to somewhere, it has defaulted to telling me how best to go there by car. It can tell you how long it takes to walk somewhere or use the train and bus but, usually, the car turns up.
Surely, a default setting. And one that’s fair enough. Google probably knows everything else about me, so why shouldn’t it know that I’d probably want to use a car? Its settings, as a rule, suited me just fine.
If I wanted to know how bad the traffic was on a Friday night, I’d stick in the office and home addresses and it would tell me where the hotspots were. If I wondered how best to get to a photoshoot venue, it’d suggest a few routes, from which I’d pick one that gave the best en route access to biscuits.
But always it would be the same: from here to here, Matthew, is x hours and xx minutes by car – which would usually turn out to be accurate to within a couple of minutes.
Sometimes, there’d be a train icon hovering underneath the suggested car route, but obviously Google knows I won’t be needing that. Until…
Yesterday, I typed in two locations: Harpenden and Flitwick. And the map’s response threw ‘22 minutes, via Thameslink’ at me. Even I know this is a train.
This time, the car routes – two suggested, of half an hour each – were the subscripts to public transport. In a heartbeat, everything that I thought I knew about the map application was bunkum, and everything I had long suspected about the best way to traverse Britain was confirmed.