Tag: what3words

Adventures in Unpreparedness

Published on by Jonathan Crowe

Two recent cautionary tales about the risks of going forth without proper navigational tools. First, I’m a bit confused about this BBC News report, which cites what3words as coming through when a boat broke down in the Channel Islands area:

[The rescue service] said although the vessel had no working on board GPS and an inoperative VHS radio, crews were able to establish a position using the location app “what3words”. […]

The coastguard said an operator was able to translate the vessel’s what3words location from a mobile phone into latitude and longitude.

Now hold on: if you’re able to use what3words on a mobile phone to get a fix on your location, it’s because your phone has a built-in GPS, so it’s not like they didn’t have access to GPS. More likely is that they couldn’t figure out how to get lat/long coordinates to rescue services in any other way. (It’s a long press on your location in either Apple Maps and Google Maps, but to be fair, that might not be obvious or easy to figure out for the first time in the middle of a crisis.)

Meanwhile, an unprepared hiker without a map who got lost in New Hampshire will likely be billed for the cost of his rescue.

What3Words Confusion Rate Under Scrutiny

Published on by Jonathan Crowe

The What3Words geocoding service assigns a three-word mapcode to every three-square-metre patch on the planet, the premise being that three words are easier to remember and share than longitude and latitude to the equivalent decimal places. But the main complaint about What3Words (apart from the proprietary nature of its algorithm and database) is that it’s possible to get even those three words confused, especially in contexts where plurals and homophones may not be heard clearly, or where similar combinations of words are close enough to each other that they can be mistaken for each other. There’s actually an entire website dedicated to chronicling errors in W3W.

W3W maintains that their algorithm keeps similar combinations “so far apart that an error is obvious. We also worked hard to remove homophones and near homophones like sale and sail.” They rate the the chance of two confusing combinations appearing close enough to be unclear at about 1 in 2.5 million. But in a new analysis of the algorithm, currently in preprint, computer scientist Rudy Arthur argues that despite W3W’s claims this chance of confusion is far higher, and warns against adopting W3W as critical infrastructure (it’s used by emergency services, particularly in the U.K.) without testing and comparing against available alternatives. [The Register]

Previously: What3Words Hasn’t Had the Greatest Couple of Months: A Roundup.

What3Words Hasn’t Had the Greatest Couple of Months: A Roundup

Published on by Jonathan Crowe

The proprietary geocoding system What3words, which assigns a three-word mapcode to each three-square-metre point on the planet, has been getting some grief lately. It’s always been somewhat controversial because it’s a closed system, and because of the steps What3words has taken to protect its proprietary database and algorithms: it’s issued takedown notices relating to the compatible, open-source WhatFreeWords (details here), to the point of threatening a security researcher over his tweets about it last April. Which, you know, got noticed.

It’s also been the subject of several parodies, including what3emojis (emojis instead of words), Four King Maps (four swear words, UK and Ireland only on account of a lack of swear words, which frankly disappoints me) and Maps Mania’s own April Fool’s joke for this year, what2figures, which expresses any point on the globe in just two numbers (I’ll wait).

But more recently it’s come under criticism for having similar sounding word combinations for addresses only a few miles apart: see Andrew Tierney’s blog post (which expands upon this Twitter thread) and What3words’s response. This is especially a problem for first responders trying to locate someone who may have misspoken or mistyped their location, or because of their accent, resulting in rescue teams being sent to the wrong location.