Hacker News new | ask | show | jobs
by cwp 4351 days ago
Globally-unique identifiers make sense on the web, where "going" to a website being served from the other side of the world is as easy as one served from across the street.

That's not true for navigation in the physical world. If you're sitting in Nebraska, how often do you have to navigate to a location in Mongolia? Approximately never! Map codes are optimized for the common case, where you want to go to a location that's nearby.

In fact, it's even more clever than that, since it defines "nearby" as a political unit. Borders may be artificial, but they're real, and crossing them has practical implications. If you're planning to buy something in another jurisdiction, there might be tax implications. You may need your passport to cross the border. You may not speak the language of that area. All of this means that having the political unit as a human-readable part of the map code is useful.

Finally, consider that some URLs do resolve differently depending on where you are. They're called relative URLs. They're very handy and very common. I'd guess that the vast majority of URLs on the web are relative. MapCodes work the same way. The code "Ireland 0C.T4" is globally unique. If you're already in Ireland, you can omit the territory, much as you would omit the country when inviting a friend to your house for dinner.

For cases where you really do have to travel to the other side of the planet, is it really so onerous to specify "Mongolia 0C.t4"?