[Talk-GB] Google "Plus Code" Locators

[Paul Berry]

Looks like it was discussed in depth three years ago. Not sure what came of
it: https://wiki.openstreetmap.org/wiki/Proposal_Open_Location_Code

The main issue I have is that if the codes can be automatically derived
from latitude and longitude then they don't contain any original
information and don't need adding to OSM. If a particular user wants to
show Plus Codes on an overlay or similar then they are free to do so but it
wouldn't be part of the map data.

If I have this wrong, please let me know.

Regards,
*Paul*

On Mon, 28 Feb 2022 at 14:08, David Woolley <forums at david-woolley.me.uk>
wrote:

> I've just noticed Google using a new locator system, which works on
> similar principles to the Maidenhead system, except that each resolution
> step is 20 x 20, rather than alternating letter and number codes, so the
> algorithm is public, and they don't seem to be imposing any licensing on
> it.  I don't remember seeing any mention of it here.
>
> Below 0.45 second resolution, 4 x 5 subgrids, coded by one letter are used.
>
> The full codes are 8 characters, a "+" and, normally at least two more.
> If you know the approximate location, the 8 can be truncated to 4, and
> the approximate location can be given with a locality name, which is the
> bit that could end up depending a bit on Google Maps for reliable
> reproducibility.
>
> It seems that they have existed since 2014, although this is the first
> time I've noticed them in a Google business listing.
>
> I did an OSM search on some examples, and it does not look as though the
> search currently recognizes them.
>
> They are also known as open location codes
> <https://en.wikipedia.org/wiki/Open_Location_Code>
>
> _______________________________________________
> Talk-GB mailing list
> Talk-GB at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-gb
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-gb/attachments/20220228/0ae4312e/attachment.htm>