Isn’t that much easier than saying ‘The south west corner of the William Gates building at 15 J J Thomson Avenue, Cambridge, CB3 9JW, UK’? Or ‘52.210577 N 0.092133 E’?
It’s even more valuable, though, in countries where addressing schemes are less well established or non-existent.
Now, it has a couple of limitations that I can see. First, you do need to be fairly precise about those words if, say, you’re reading them over the phone. If, instead of ‘faced.ears.sport’, you went to ‘face.ears.sport’, you’d find yourself in a little residential street in Montana, which would be delightful, but you wouldn’t find me there on a typical work day. ‘faced.ears.port’ is in Louisville, Kentucky. However, the fact that they’re so spread out probably makes such errors less likely to go undetected – this is deliberate.
The second limitation is that this is a commercial operation and not an open standard, which is a pity in some ways, but understandable. It’s free for individuals to use – there’s a free iOS and Android app, for example – and the pricing page contains this assertion:
If we, what3words ltd, are ever unable to maintain the what3words technology or make arrangements for it to be maintained by a third-party (with that third-party being willing to make this same commitment), then we will release our source code into the public domain. We will do this in such a way and with suitable licences and documentation to ensure that any and all users of what3words, whether they are individuals, businesses, charitable organisations, aid agencies, governments or anyone else can continue to rely on the what3words system.
I think it’s a brilliantly simple idea. The concept has been used in other situations (passwords, PIN numbers etc), but works really well here.
My friend Mike Flynn has been working for some years on very fast routing algorithms — routing as in maps, that is — and his primary demonstration of this is TimeToAnywhere – a system which can work out how long it takes to drive from one location to everywhere else on the map.
So you can say, for example, “There’s been an accident here. Which ambulances could reach it in less than 15 mins?” Or, “I work in Dry Drayton. Where could I live, and still have less than a half-hour commute?”
Each coloured boundary represents 10 minutes’ driving.
This is pretty, but those of you with a computing background may also realise that, using most of the standard algorithms, this is also a very time-consuming problem when you try do it across this number of points. Mike, however, measures the time taken by his system in microseconds.
He’s recently set up a demo server which, if it doesn’t get too swamped, is fun to play with to get a feel for the speed! You can find it at TimeToAnywhere.com, and if you want to know how to get the most out of it, watch Mike’s short video.
…and so I turn to one of the most useful sites for British dog-walkers (cyclists, etc), which can help you answer the questions, “Is it about to rain?” and “How long will this rain last?” At the moment, the former question is largely rhetorical, but the answer to the latter can be very useful.
It was Richard who first pointed me at raintoday.co.uk, which gives you a rough animation of the radar precipitation map over the last couple of hours, so you can get a feeling for how fast the clouds are moving.