Skip to content
This repository has been archived by the owner on Dec 16, 2020. It is now read-only.

Support for Open Location Code #31

Closed
2 tasks done
karussell opened this issue Jun 27, 2016 · 3 comments
Closed
2 tasks done

Support for Open Location Code #31

karussell opened this issue Jun 27, 2016 · 3 comments

Comments

@karussell
Copy link
Member

karussell commented Jun 27, 2016

We should not only support GPS coordinates but also open location code from Google. Standing under Apache License. See here for a good comparison where open location code stands out from its logical point of view and being pure algorithmic based as well as the code license.

We need to clarify

An alternative would be https://github.com/roberdam/Xaddress

@karussell karussell changed the title Open Location Code Support for Open Location Code Jun 27, 2016
@karussell
Copy link
Member Author

We won't support this

@mmd-osm
Copy link

mmd-osm commented May 12, 2020

Apologies for hijacking this issue a bit. Maybe you've seen the discussion to implement OLC on osm.org which has attracted a lot of attention in recent years: openstreetmap/openstreetmap-website#1807.

As you seem to have spent some time analyzing OLC in more detail and eventually decided against it, your reasoning might be helpful for the discussion on osm.org as well.

@karussell
Copy link
Member Author

I prefer OLC over all other existing "codes". But IMO the client can&should decode OLC and use coordinates for all API related stuff.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants