Live data from Hacker News

Open Location Code: An Open Source Standard for Addresses

github.com

51–60 of 95 posts

Re: Open Location Code: An Open Source Standard for Addresses

#51
post #49

Ah https://plus.codes/ .. I've noticed them on Google maps: https://s.natalian.org/2019-08-20/yard.jpeg However: https://plus.codes/8VG3+J4 Says it couldn't find it. Did I make a typo? There is no mention of a checksum in the doc.

In that case you need to include Singapore. The inclusion of Singapore allows the plus code itself to be shorter.

Alternatively, you could use the full plus code: 6PH58VG3+J4

Re: Open Location Code: An Open Source Standard for Addresses

#52
post #48
post #32

Earlier quoted context omitted.

Why should it handle that? If you move a house (say, a trailer home) from Nebraska to Oregon, you wouldn't expect the location to stay the same. OLC encodes position on the globe (basically angles), not points on the crust or other territorial features.

In a previous discussion about the topic it was mentioned that an earthquake can move a road a few meters to a side. Tectonic shift might be less important but physical relocation could be. A road could be moved du to a large urban work in the area for example.

I know that. But why do you insist that a location code stays the same? The location has really changed.

Plus codes are not street addresses.

Re: Open Location Code: An Open Source Standard for Addresses

#53
post #3

Some alternatives that I am aware of: https://wikimili.com/en/Natural_Area_Code , https://what3words.com/ , https://geokey.io/ , http://geohash.org/ , https://www.mapcode.com/ . Some of which are proprietary. Edit: plus.codes was this same proposal. Removed from the list.

Also, much older systems: QRA Locator and Maidenhead Locator System.

Re: Open Location Code: An Open Source Standard for Addresses

#55
Seems like reinventing a solid wheel with a disposable one... I'm more for Latitude and Longitude:

- Latitude/Longitude have been around for a long time, established, proven reasonably reliable.

- Ultimate more calculable, no need for lookup/conversion

- No language issues (three words seem to be primarily English) also unless it becomes an international standard whats to stop someone making a similar service with different words...

- Latitude/Longitude could be added to map legends (even with decimals, it still is quite understandable)

- Letter codes can be more confusing then a general numeric coordinate, get one letter wrong and you are off the map and not sure which letter is the one.

I use Lat/Lon in my apps and can't see how these would make things more efficient or as independent on external resources. They all seem much more arbitrary. (edited for formatting)

Re: Open Location Code: An Open Source Standard for Addresses

#56
post #4

I wish Google to put a tiny bit of their money [0] into promoting this more. To counter the closed-source, for-profit what3words offering. [0] https://www.theverge.com/2019/8/1/20749831/alphabet-google-a...

Google maps shows "Plus Codes" (same thing) in it's UI. eg Salesforce Tower shows plus code of

QJQ3+V3 SoMa, San Francisco, CA

Re: Open Location Code: An Open Source Standard for Addresses

#58
post #29

Earlier quoted context omitted.

The docs also seem to indicate that 3mx3m is the smallest grid they can address, but at the same they use addressing in slums as a use case...who has that much real estate in the slums?

Hi - plus codes founder here. You can just keep adding digits and the area gets smaller. The way I think of it is: +XX "house" (13x13 meters) +XXX "bathroom" (3.5x2.8 meters) +XXXX "chair" (87x56cm) +XXXXX "envelope" (22x11cm) In Kolkata the NGO (Addressing the Unaddressed) are using +XXXX codes.

Thanks for clearing that up!

Re: Open Location Code: An Open Source Standard for Addresses

#59
A good explanation of this against competing standards seems to be available here [1]. It seems weird that they complain about discontinuities in such a system, where there has to be some discontinuities in a tiled system.

Now, could this be used as an alternative to DNS? have a registrar per tile, and delegate if necessary.

I wish this could be used as a geo: URL, or as a location field in my ical invites. I guess I need better support in various apps for it.

Maybe it lack elevation information to specify meeting rooms, though? Perhaps it could be extended to support both ground and absolute elevation.

Excluding words somewhat makes sense, but also removes some opportunities for artificial attractions, it isn't like some areas don't already have interesting ones [2]). So I am a bit split on this one, as it does generate longer names. Maybe emojis would be a better fit?

Now, a note about standard presentation: I would have preferred a technical overview to an introduction that merely sums up some obvious (to me) facts, without really getting into explaining the standard. Perhaps someone has already come up with a way to publish standards together with a few sliders to control the amount of content displayed? That would be great.

[1]: https://github.com/google/open-location-code/wiki/Evaluation...

[2]: https://www.estately.com/blog/2016/09/the-complete-list-of-l... as an example, it gets worse if you include foreign cities, regardless of the language.

Re: Open Location Code: An Open Source Standard for Addresses

#60
post #3

Some alternatives that I am aware of: https://wikimili.com/en/Natural_Area_Code , https://what3words.com/ , https://geokey.io/ , http://geohash.org/ , https://www.mapcode.com/ . Some of which are proprietary. Edit: plus.codes was this same proposal. Removed from the list.

This is why these technologies never get mass adoption; so many solutions duplicating themselves trying to solve the same thing. Fact is, most users would care less about numerous implementation, they need to be educated just one solution which works fine. Personally I find plus.codes from Google user-friendly. They are already integrated in Google Maps which has over 1 billion downloads. They are free and opensource…

As usual there is a relevant XKCD. This time it is https://xkcd.com/927/
Post reply on HN