Hacker GitHub

← All repos

google/open-location-code

View on GitHub ↗ ★ 4,370 Java

Open Location Code is a library to generate short codes, called "plus codes", that can be used as digital addresses where street addresses don't exist.

68 mentions on Hacker News by 55 people: 15 stories, 53 comments · first 2015-02-11 · latest 2024-08-23

Mentions per year 68 mentions · busiest year 2018 (17)
20082026
  1. …also link tax filings and a Plus Code for physical location: https://maps.google.com/pluscodes/ https://github.com/google/open-location-code
  2. …Map also has 'plus codes' CPR2+J7 SeaTac, Washington https://maps.google.com/pluscodes/ and https://github.com/google/open-location-code Which seems like a compelling variation for encoding the GPS value. The algorithm is described here:…
  3. Pluscode is a trademark. The actual standard is called "open location code" and is unrestricted - https://github.com/google/open-location-code/
  4. …does make harder to remember, but I think the memorizability constrains other goals too much. [1] https://github.com/google/open-location-code/wiki/Evaluation...
  5. …name is "double U". And tried a letter like N or Y, which would be much harder to confuse. [0] https://github.com/google/open-location-code/blob/main/docs/...
  6. ▲ 32
    Evaluation of Location Encoding Systems (2021)
    story by tosh · 2023-03-26 · 14 comments
  7. It's licensed Apache 2.0 https://github.com/google/open-location-code
    comment by orangepurple · 2023-03-04 · in Costa Rica’s enigmatic addresses (2021)
  8. ▲ 2
    An Evaluation of Location Encoding Systems (2018)
    story by Tomte · 2022-12-22 · 0 comments
  9. ▲ 3
    Evaluation of Location Encoding Systems
    story by sandebert · 2022-06-17 · 0 comments
  10. ▲ 2
    Open Location Codes
    story by agmm · 2021-12-02 · 0 comments
  11. ▲ 1
    Open Location Code
    story by Natfan · 2021-08-31 · 0 comments
  12. An Evaluation of Location Encoding Systems https://github.com/google/open-location-code/wiki/Evaluation...
  13. > An Evaluation of Location Encoding Systems https://github.com/google/open-location-code/wiki/Evaluation...
  14. …in Kolkata, this was then used in Native American communities. P.S. Plus Codes are open source - https://github.com/google/open-location-code And they are well researched. > The character set for Open Location Code was selected out of over…
  15. Plus Codes are a better choice. https://github.com/google/open-location-code/wiki/Evaluation...
  16. pluscodes are also known as "Open Location Code" and the github repo is: https://github.com/google/open-location-code
    comment by CA0DA · 2021-05-02 · in What3Words – The Algorithm
  17. check out Open Location Code ( https://github.com/google/open-location-code ) (aka PlusCodes)
    comment by CA0DA · 2021-05-02 · in What3Words – The Algorithm
  18. https://github.com/google/open-location-code/wiki/Evaluation...
  19. …anyone under an Apache 2.0 license with a whole bunch of example implementations on github[1] [1] https://github.com/google/open-location-code
    comment by paranoidrobot · 2021-04-11 · in Setting up Starlink
  20. It's open source... anyone can encode and decode plus codes: https://github.com/google/open-location-code
    comment by coder543 · 2021-04-10 · in Setting up Starlink
  21. …other proprietary systems with this open one. https://en.wikipedia.org/wiki/Open_Location_Code https://github.com/google/open-location-code
    comment by coder543 · 2021-04-10 · in Setting up Starlink
  22. ▲ 45
    An Evaluation of Location Encoding Systems (2018)
    story by Tomte · 2021-03-12 · 10 comments
  23. …in many languages [2], which means the effect of the project being abandoned would be limited. [1] https://github.com/google/open-location-code/blob/master/doc... [2] https://github.com/google/open-location-code
  24. …k=5)) # check against id in dict if userinput.toupper() in idmapping: ... [0]: https://github.com/google/open-location-code/blob/master/js/... [1]: https://github.com/google/open-location-code/blob/master/doc... , under "Easy to use"
  25. https://github.com/google/open-location-code/wiki/Evaluation...
  26. …selected 20 character set is made up of "23456789CFGHJMPQRVWX". [2] [1]: https://plus.codes [2]: https://github.com/google/open-location-code/blob/master/doc...
  27. …considerably. Thank you for the write up, will be keeping my ears open for GeohashPhrase. --- [0] https://github.com/google/open-location-code/wiki/Supporting...
    comment by lioeters · 2019-10-11 · in What’s going on with WhatFreeWords?
  28. …from Google (AKA Plus Codes). They have a useful wiki article which compares existing systems: https://github.com/google/open-location-code/wiki/Evaluation...
    comment by lol768 · 2019-10-10 · in What’s going on with WhatFreeWords?
  29. …it's not clear that a computer would recognize incorrect but valid codes as well as a human. [1] https://github.com/google/open-location-code/blob/master/FAQ...
  30. …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…
  31. I'm not sure why you want fixed point. Some of the reasoning behind them going with base20 is here: https://github.com/google/open-location-code/blob/master/doc... * 10 characters can represent a 14x14 meter area suitable for many…
  32. Some of which are mentioned here: https://github.com/google/open-location-code/wiki/Evaluation...
  33. ▲ 184
    Open Location Code: An Open Source Standard for Addresses
    story by ColinWright · 2019-08-20 · 90 comments
  34. ▲ 2
    Open Location Code
    story by tosh · 2019-05-12 · 0 comments
  35. …What they do have is a great PR person who gets them fantastic advertising article like this one. https://github.com/google/open-location-code/wiki/Evaluation...
    comment by client4 · 2019-05-12 · in A Geocode Is Not an Address
  36. …many geocoding systems entirely forwent vowels for that reason [2]. [1] http://wiki.yak.net/589 [2] https://github.com/google/open-location-code/wiki/Evaluation...
  37. ▲ 41
    An Evaluation of Location Encoding Systems (2018)
    story by Tomte · 2019-04-01 · 0 comments
  38. …I work for Google/Geo, the opinions expressed here are mine, and not of my employer . [1] https://github.com/google/open-location-code/blob/master/doc... [2] https://plus.codes/map [3] https://plus.codes/howitworks
    comment by romwell · 2019-03-28 · in Why Bother with What Three Words?
  39. …for Plus Codes), where they compare it against numerous location encoding systems including W3W. https://github.com/google/open-location-code/wiki/Evaluation... For W3W, they say: - The codes may be pseudo-randomly generated and so nearby…
    comment by lioeters · 2019-03-28 · in Why Bother with What Three Words?
  40. Out of interest here's a list of alternatives and why they're worse than plus codes: https://github.com/google/open-location-code/wiki/Evaluation...
    comment by rakoo · 2019-03-28 · in Why Bother with What Three Words?
  41. Project: https://github.com/google/open-location-code
    comment by maxerickson · 2019-03-28 · in Why Bother with What Three Words?
  42. …are no licensing fees. They also compare different location encoding systems like Lat-Long etc. https://github.com/google/open-location-code/wiki/Evaluation...
    comment by denzil_correa · 2019-02-04 · in German town votes ‘No’ to street names
  43. Quite a bit, it seems. https://github.com/google/open-location-code/wiki/Evaluation...
    comment by ascorbic · 2018-12-11 · in Open Location Code
  44. There's a pretty solid evaluation of the new system in terms of the old ones at: https://github.com/google/open-location-code/wiki/Evaluation... Indeed maidenhead seems to be the strongest of the previous approaches, they rejected it…
    comment by nmca · 2018-12-10 · in Open Location Code
  45. For those wondering why they invented yet another grid coding system, here's their justification : https://github.com/google/open-location-code/wiki/Evaluation... The XKCD on competing standards comes to mind…
    comment by arnoooooo · 2018-12-10 · in Open Location Code
  46. https://github.com/google/open-location-code/wiki/Evaluation... One of the design decisions was to avoid ambiguous characters, so that cuts out at least 9 (I1L 0OB8).
    comment by richthegeek · 2018-12-10 · in Open Location Code
  47. …recognisable words. The selected 20 character set is made up of "23456789CFGHJMPQRVWX". [1]: https://github.com/google/open-location-code/blob/master/doc...
    comment by awirth · 2018-12-10 · in Open Location Code
  48. ▲ 137
    Open Location Code
    story by FriedPickles · 2018-12-10 · 118 comments
  49. …included recognisable words. The selected 20 character set is made up of "23456789CFGHJMPQRVWX". https://github.com/google/open-location-code/blob/master/doc...
    comment by adambrenecki · 2018-11-08 · in Base58
  50. …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... )
    comment by __initbrian__ · 2018-09-30 · in Plus codes: addresses for everyone