3 ms·

Looks like what3words [0], only less memorable. The Louvre in Plus codes:"V86P+C8, Paris" [1] The Louvre in what3words: "seasons.sharper.scan" [2] I'm much m

Looks like what3words [0], only less memorable. The Louvre in Plus codes:"V86P+C8, Paris" [1] The Louvre in what3words: "seasons.sharper.scan" [2] I'm much more likely to remember "seasons.sharper.scan" than "V86P+C8" 0: https://map.what3words.com/ https://map.what3words.com/ 1: https://plus.codes/8FW4V86P+C8 https://plus.codes/8FW4V86P+C8 2: https://map.what3words.com/seasons.sharper.scan https://map.what3words.com/seasons.sharper.scan

lifthrasiir 8y ago
But you may instead remember "season.sharper.scan", which is 1453 km apart from the Louvre [1]. The what3words word list is deeply flawed. [1] https://map.what3words.com/season.sharper.scan https://map.what3words.com/season.sharper.scan
- tgsovlerkhgsel 8y ago
  Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong, and showing similar addresses as a "did you mean" when you search for one. The FAQ entry is incredibly hard to find but it exists: https://support.what3words.com/hc/en-us/articles/203066992-What-if-I-spell-or-say-a-word-incorrectly-or-get-the-words-in-the-wrong-order- https://support.what3words.com/hc/en-us/articles/203066992-W... https://support.what3words.com/hc/en-us/articles/207065359-What-about-words-that-sound-the-same-or-with-variant-spellings- https://support.what3words.com/hc/en-us/articles/207065359-W... On their map, you have to accept their non-GDPR-compliant cookie "consent" form in order to get access to the real interface, otherwise the cookie notice covers it. Also, they have country-specific word lists. On one hand, that's nice because locals will be able to use it even if they're not familiar with the latin alphabet/the English language, on the other hand, it means you may be asked to search for misant.habiter.jaloux instead, at which point a plus code may become preferable. Their algorithm also seems to be incredibly complex, requiring a 20 MB library (likely wordlists + workarounds to make offensive codes less likely). Their web site does not explain how it works, and varies between claims that the words were assigned randomly and claims that they weren't (shorter words in more populated areas, similar words far apart). However, they've alleviated all need to discuss their technical benefits with their restrictive licensing approach, which guarantees that they will be unsuccessful while preventing anyone else from building a different approach based on words (both because it would create confusion and due to fear that they'll start costly lawsuits/claims).
  - lifthrasiir 8y ago
    > Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong, and showing similar addresses as a "did you mean" when you search for one. I don't buy their claims. If they cared about human-friendliness and recognized the possibility of errors, the proper response would be to add an error detection scheme like barcodes. The use cases of what3words are even more diminished by requiring an app to see what's wrong. > Also, they have country-specific word lists. I do think the needs for localization is properly recognized (of course, one can get better geocodes by eliminating the possibility of natural languages in advance). But the resulting system is bad: they breaks down after the translation. And also as a native Korean speaker the word list is strange enough to me ;)
    - masukomi 8y ago
      > they breaks down after the translation they also break down because systems like Siri are terrible about recognizing words in "foreign" languages (foreign being any language different from the one it speaks in, even if supported by the manufacturer).
  - tzs 8y ago
    > Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong Wow. We live in a world where people will drive off docks or down boat launches and end up in a lake because their GPS said that was the way to go. In such a world purveyors of navigation aids really need to assume that there is no such thing as "obviously wrong". I would think that what we would want in a system that assigns to physical locations elements of a sequence that has a natural ordering is to have the property that elements of the sequence that are near each other in that ordering correspond to physical locations that are near each other. You can do such mappings using fractals. Here is an XKCD that shows such a mapping of the internet, associating with each internet address a place on the plane such that any group of consecutive IP addresses maps to a compact region in the plane: https://xkcd.com/195/ https://xkcd.com/195/ The same principle would work with a what3words-like mapping where the ordering is alphabetic ordering.
tordanik 8y ago
Just make sure you don't misremember it as "seasons.sharper.scans" (notice the "s" at the end) or you end up in Russia. One of the benefits of Plus Codes is that similar codes are close to each other. Besides, what3words makes you dependent on a proprietary database to map the words to coordinates, which as as far as I'm concerned is an instant deal breaker.

lifthrasiir 8y ago

But you may instead remember "season.sharper.scan", which is 1453 km apart from the Louvre [1]. The what3words word list is deeply flawed. [1] https://map.what3words.com/season.sharper.scan https://map.what3words.com/season.sharper.scan

tgsovlerkhgsel 8y ago
Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong, and showing similar addresses as a "did you mean" when you search for one. The FAQ entry is incredibly hard to find but it exists: https://support.what3words.com/hc/en-us/articles/203066992-What-if-I-spell-or-say-a-word-incorrectly-or-get-the-words-in-the-wrong-order- https://support.what3words.com/hc/en-us/articles/203066992-W... https://support.what3words.com/hc/en-us/articles/207065359-What-about-words-that-sound-the-same-or-with-variant-spellings- https://support.what3words.com/hc/en-us/articles/207065359-W... On their map, you have to accept their non-GDPR-compliant cookie "consent" form in order to get access to the real interface, otherwise the cookie notice covers it. Also, they have country-specific word lists. On one hand, that's nice because locals will be able to use it even if they're not familiar with the latin alphabet/the English language, on the other hand, it means you may be asked to search for misant.habiter.jaloux instead, at which point a plus code may become preferable. Their algorithm also seems to be incredibly complex, requiring a 20 MB library (likely wordlists + workarounds to make offensive codes less likely). Their web site does not explain how it works, and varies between claims that the words were assigned randomly and claims that they weren't (shorter words in more populated areas, similar words far apart). However, they've alleviated all need to discuss their technical benefits with their restrictive licensing approach, which guarantees that they will be unsuccessful while preventing anyone else from building a different approach based on words (both because it would create confusion and due to fear that they'll start costly lawsuits/claims).
- lifthrasiir 8y ago
  > Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong, and showing similar addresses as a "did you mean" when you search for one. I don't buy their claims. If they cared about human-friendliness and recognized the possibility of errors, the proper response would be to add an error detection scheme like barcodes. The use cases of what3words are even more diminished by requiring an app to see what's wrong. > Also, they have country-specific word lists. I do think the needs for localization is properly recognized (of course, one can get better geocodes by eliminating the possibility of natural languages in advance). But the resulting system is bad: they breaks down after the translation. And also as a native Korean speaker the word list is strange enough to me ;)
  - masukomi 8y ago
    > they breaks down after the translation they also break down because systems like Siri are terrible about recognizing words in "foreign" languages (foreign being any language different from the one it speaks in, even if supported by the manufacturer).
- tzs 8y ago
  > Their claimed solution when I read about this the last time was that similar words are designed to be very far off in order to make them obviously wrong Wow. We live in a world where people will drive off docks or down boat launches and end up in a lake because their GPS said that was the way to go. In such a world purveyors of navigation aids really need to assume that there is no such thing as "obviously wrong". I would think that what we would want in a system that assigns to physical locations elements of a sequence that has a natural ordering is to have the property that elements of the sequence that are near each other in that ordering correspond to physical locations that are near each other. You can do such mappings using fractals. Here is an XKCD that shows such a mapping of the internet, associating with each internet address a place on the plane such that any group of consecutive IP addresses maps to a compact region in the plane: https://xkcd.com/195/ https://xkcd.com/195/ The same principle would work with a what3words-like mapping where the ordering is alphabetic ordering.

tordanik 8y ago

Just make sure you don't misremember it as "seasons.sharper.scans" (notice the "s" at the end) or you end up in Russia. One of the benefits of Plus Codes is that similar codes are close to each other. Besides, what3words makes you dependent on a proprietary database to map the words to coordinates, which as as far as I'm concerned is an instant deal breaker.