Hacker News new | past | comments | ask | show | jobs | submit login

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



That's totally true (and I missed that), but it seems to me that the Country/State-specific look-up table is still the unversioned weak point.

What if state or national borders change?

Or how about disputed areas? Which table should I go to to look up words for Kashmir? And is the choice of table an (unintended) political statement?

Let's say I am creating an address in Kashmir. I have the integer coordinates 32,76, so I look up the number in the Indian table and I get 04.

I then hand my address to someone else, who believes Kashmir is Pakistani. He looks up the Pakistani table, which includes the table for Azad Kashmir, and looks up the coordinate for 04, which is 33,73. Oops.

True, "Azad Kashmir" is currently considered to be a distinct region, but it is certainly within the bounds of credible that Pakistan officially renames that area to "Kashmir" alone, in an attempt to bolster their claim on the region.

Then you'd have two distinct areas named Kashmir in your tables, but two different interpretations of the geographical bounds of those regions in the minds of the people in Pakistan and India.

The advantage of some of the other systems is that they are dependent on nothing other than latitude and longitude.

----

(Edit: to be clear, I think this is a cool project, and any edge-cases that may be problematic here are much tinier than my original, incorrect concern about word-list versioning.)


Yes, Xaddress creates 2 kinds of codes, the short one is inmutable and does not depend from geopolitical boundaries, you can check http://ubicate.me for the short code implementation.




Applications are open for YC Winter 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: