3 ms·
I like the idea of a universal addressing system but I don't think we've found the solution yet to this extremely difficult problem. Street addressing is nice
by __initbrian__ 8y ago
I like the idea of a universal addressing system but I don't think we've found the solution yet to this extremely difficult problem.
Street addressing is nice because the addresses with the same street name are on the same street organized by number. (generally at least--there are example of streets that stop/restart) And the numbering is collinear with the direction of travel. i.e. I walk along the street. And I know I'll pass 11XY to get to 12XY.
what3words was interesting but the words for the squares don't seem to be related to each other. From one square, I'd like to be able to generate the addresses of all the adjacent squares. (///jumped.spring.improving directly next to ///book.groups.hiking) and I can't generalize a larger square of w3w squares with an overarching set of words or something
playing around with the plus codes, they seem to increment in a consistent way but I haven't figured out how
e.g. (a random example)
W->E: _+HJV _+HJW _+HJX _+HMR
N->S: _+HMJ _+HMC _+HM6 _+HM2
I also like that I can change the address reference box size based on how many letters I have after the plus sign. In case I want to reference my front door versus my entire city.
It'd be much easier filling out addresses in forms because I could type less info. But it'd be hard for me to associate a string on number letters to an area just in everyday life. Market St or Powell st carries more with it. And is streets aren't directly aligned with the boxes then that poses a difficulty.
Edit: found their doc evaluating other methods [link](https://github.com/google/open-location-code/wiki/Evaluation-of-Location-Encoding-Systems https://github.com/google/open-location-code/wiki/Evaluation...)