@Steven_Ramage are there differences between @google #openlocationcode and @what3words?
-
-
Replying to @caribbeangis
@caribbeangis@what3words is more memorable, less prone to errors & easier to communicate |@Steven_Ramage@googlepic.twitter.com/JymTNyEVbU
1 reply 0 retweets 1 like -
Replying to @what3words
Thanks
@Steven_Ramage.@what3words seems not-systematic? Is that bad for humans trying to understand it as a ref. system?@google1 reply 0 retweets 1 like -
Replying to @caribbeangis
@caribbeangis@Steven_Ramage intentionally non-sequential/non-hierarchical in favour of error detection/usabilityhttp://what3words.com/faq/#toggle-id-19 …1 reply 0 retweets 1 like -
Replying to @what3words
@what3words@Steven_Ramage FAQ doesn't say why intentionally non-sequential/non-hierarchical, but why hide relationship between places?1 reply 0 retweets 0 likes -
Replying to @caribbeangis
@caribbeangis@Steven_Ramage happy to explain in detail | DM | Also see here http://what3words.com/about/ & you can download the tech report1 reply 0 retweets 0 likes -
Replying to @what3words
@what3words@Steven_Ramage thanks for tech report. Some +s but no 'commonality'. Why remove concept of neighbourhood in addressing?2 replies 0 retweets 0 likes -
Replying to @caribbeangis
@caribbeangis We favoured error-detection over commonality in our system design, as it’s impossible for a point ref system to have both.1 reply 0 retweets 0 likes -
Replying to @what3words
@what3words what errors? And seems commonality and ease of use together in#mapcode - e.g. GUY 9Z.LJ, 9Z.LK & 9Z.LL are neighbours1 reply 0 retweets 0 likes
@caribbeangis was that a Z or a 2, and l or a 1 or a 7. Errors are easy to make and hard to spot in random alphanumerical lists.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.