[openstreetmap/openstreetmap-website] Add OpenLocationCode to OSM website (#1807)

[Peter]

Hi, seems the problem is not about latitude/longitude encoding technology only... There are a lot of good ones: OpenLocationCode (not the better), Geohash (why OSM never used?), S2geometry (the better!), ... 

The problem is the [shortening-codes techonology](https://github.com/google/open-location-code/wiki/Guidance-for-shortening-codes) that is a black-box maintained by Google: 

* how to **decide** that some city name is limited or not to rectangular area that **is not a complete cover**?  Example: a building in the municipality of Altamira (PA) in Brazil is at location  [QQVJ+6F](https://plus.codes/6889QQVJ+6F), a short code  of six digits... But other location of Altamira are not, [6889CW6G+6X](https://plus.codes/6889CW6G+6X), [68588VMH+W2](https://plus.codes/68588VMH+W2), ... And have no naming schema to  shortening 90% of Altamira's big area,  because there are no Google interest in the region... Is a sovereignty question. 

* how to fix an "official cover" or "official prefix" for a location?  The main "technology" is to replace prefixes by [coverings](http://s2geometry.io/devguide/examples/coverings.html), changing the original grid codes... There are a  group here discussing coverings?

Seems that if OSM community whant to maintain a good technology, need to maintain a governance schema to (legitimes/sovereign local) decisions.



-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-451538525
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190104/3bdb1d9f/attachment.html>