Xaddress

There is https://xaddress.org 1) Opensource and free 2) Can be used offline 3) Designed to be used in low tech environments and decoded by hand 4) Multilanguage 5) Error correction incorporated with visual avatar. 6) Short code for storing or linking. 7) Works with any map. 8) Yow know is an address when you see it. ----------------------------------------- Here is a comparision side by side of each option For GPS : -6.7184 , 129.5080 XADDRESS: 7150 Magical Pearl - Maluku, Indonesia WHAT3WORDS: percolator.surmount.retooled GEOHASH: qyu1g0by7 MAPCODE: VQ6.1MFD OPENLOCATIONCODE: 6Q5F 7GJ5+J6 ----------------------------- Article about it: https://medium.com/hackernoon/an-algorithm-that-can-give-an-... Github: https://github.com/roberdam/Xaddress (Disclosure: im the creator of Xaddress.)

Indeed, xaddress lists alternatives on its readme (including what3words): https://github.com/roberdam/Xaddress/blob/master/README.md#a...

From the list of words at https://github.com/roberdam/Xaddress/blob/master/en/adj_en.c..., I take it that some locations will be labelled DESPERATE, UNSPEAKABLE, POSTDOCTORAL, OBSTETRICAL, GENEALOGICAL, ASSASSINATING,CORRUPTED, PROGESTERONE, etc. etc., also RUSSIAN, UKRAINIAN, DUTCH, ...etc. Where did that list come from?

good point... resembles a normal address compared with the alternatives at least. https://github.com/roberdam/Xaddress#compare-encodings

Your Xaddress will work even if we remove the word from the available list, you can try encoding or decoding by hand to understand how it works https://github.com/roberdam/Xaddress/tree/master/by_hand

I have seen a lot of these co-ordinate based alternative address mechanisms (in fact the author gives a list -- https://github.com/roberdam/Xaddress#compare-encodings). But in my opinion, one thing they all ignore or get wrong is establishing some kind of linking mechanism between real world and co-ordinate based addresses. This is a hard problem, but one without which it is not going to be able to gain significant adoption. How do we solve it? I am not sure. Maybe somehow augmenting regular national postcodes with coordinates would work better than these (kinda like the 4-digit augmentation to US ZIP codes) – because those are things you use on a daily or atleast monthly basis, and remember. Something like 98002-MAGICAL PEARL would be more easily remembered, and not get rid of existing information.

Thanks pingec, it seems to be something with the Google Api, I will check that, in the meanwhile you can try the CLI if you know ruby or try it by hand https://github.com/roberdam/Xaddress/tree/master/by_hand

Thanks for the feedback, I will work to translate all the variables to make it more readable, in the meanwhile you can check the logic behind the problem here: https://github.com/roberdam/Xaddress/tree/master/by_hand

Thanks!, of course, you can encode/decode the Xaddress even by hand so it can be used in low tech environments, the guide is https://github.com/roberdam/Xaddress/tree/master/by_hand