I came across a Scottish post code, which covered two addresses five or ten miles apart - they were 'next door neighbours' along the road, there just wasn't anything in between (except moorland).They are also nowhere specific enough for the purpose required here. One postcode could be a whole side of a street for example or a number of disparate buildings.
And another couple in Scotland, both of which also applied to addresses across the border, in England...
The underlying principle of W3W is that for a location, it will generate three words which you can easily remember, and give them to someone else who will be able accurately enter them to reverse the process to get the location. But for the W3W app, a word is no more than a string of letters... In theory, fine, but in practice, when you have some of the more difficult words, similarities between words, thick accents, poor spelling, their approach to multilingualism, it soon becomes not - and if you get it wrong, it could be anywhere, from the other side of the world, to just far enough away to be a problem. Apart from all the other problems down to it being a commercial, supposedly money making (in practice, I believe not) operation, these make it something best avoided. Another issue perhaps its fixed precision - to an approximately 3m square - meaning anything larger will have many unrelated locations...I wasn't aware of the problems with what3words, but it is far superior to OS Grid references, for example. OS may be fine for safety critical trained staff, but is very poor for the public, as it is so easy to get it wrong, numbers transposed, longitude and latitude the wrong way around, etc. What3words at least provides three easily remembered words.
While I would not disagree that, for anything using long numbers - grid references, lat & long, phone numbers, account numbers,etc., there is a risk of them being got wrong, but I suspect this is balanced by - realising this - greater care being taken that they are correct.
