Earlier quoted context omitted.
Where do I find them in Google maps? what is the plus.code for the Eiffel tower? https://www.google.com/maps/place/Eiffel+Tower,+Paris,+Franc...
I don't know about that specific listing from your link, but I dropped a pin right on l'avenue Gustave-Eiffel behind the tower and got the code V75W+43 Paris, France. Plus codes appear right under the address line.
Open Location Code: An Open Source Standard for Addresses
31–40 of 95 posts
Re: Open Location Code: An Open Source Standard for Addresses
#32So this is based on GPS, right? How does this system deal with tectonic plate shift? A house may move by a couple meters over years, which will exceed the accuracy of the 12 digit code. At the very least the code should include a timestamp (year is probably precise enough).
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.
Re: Open Location Code: An Open Source Standard for Addresses
#33From my point of view, this approach is harder to remember than remembering 3 words (what3words). Try to remember: 6GCRMQPX9G 3FHMRV5JMX 8FJM2QRW78 Or try to remember: tell.fantasy.animal zone.house.horses home.penguin.room Also what3words have got bad thinks as that similar words are far away from each other and the words location are not properly translated
1. Random but fair distribution of domain names to everyone on Earth, if that becomes a thing.
2. Any kind of unique identifier that should be user memorable.
Re: Open Location Code: An Open Source Standard for Addresses
#34From my point of view, this approach is harder to remember than remembering 3 words (what3words). Try to remember: 6GCRMQPX9G 3FHMRV5JMX 8FJM2QRW78 Or try to remember: tell.fantasy.animal zone.house.horses home.penguin.room Also what3words have got bad thinks as that similar words are far away from each other and the words location are not properly translated
In principle, armed with just a compass and odometer and knowing your current plus code, you can make your way to a nearby plus code. Similarly, once you get a feel for the distance increment a plus code give you, you can tell how far away a given location is, and in what direction.
Re: Open Location Code: An Open Source Standard for Addresses
#35In some Latin countries, road names are given after "important" people (for a vague definition of important). On the cultural side, having a standard for naming like this removes that and I think it could be a roadblock for adoption. Politicians' names are specially used for naming roads/squares and they are always after promoting their names in every new opportunity. On the other side, I really like that the code ca…
Re: Open Location Code: An Open Source Standard for Addresses
#36Re: Open Location Code: An Open Source Standard for Addresses
#37Earlier quoted context omitted.
what3words has appeared twice recently as a news story on bbc.co.uk I'd not heard of plus.codes even though now I realise I'd seen them on google maps listings
The most recent article [1] read like an advertisement. They even quoted someone as saying "I just cannot see a downside". It's a shame they didn't find time to mention any of the many criticisms of it, most of which are listed on Wikipedia! [1]: https://www.bbc.co.uk/news/uk-england-49319760
Re: Open Location Code: An Open Source Standard for Addresses
#38So this is based on GPS, right? How does this system deal with tectonic plate shift? A house may move by a couple meters over years, which will exceed the accuracy of the 12 digit code. At the very least the code should include a timestamp (year is probably precise enough).
First, most plates move a couple of centimeters per year, and the fastest plates (those in Australia) move around 7-10 cm. The default precision plus code is 13x13 meters, so it should take a long time to be wrong.
Secondly, one aim is for this to be an addressing solution in places without street names. If the point doesn't exactly align with the house, if they have a sign, it's still going to be easy to get the right place.
Nice question though!
[edit: move corrected to most]
Re: Open Location Code: An Open Source Standard for Addresses
#39Earlier quoted context omitted.
I don't know about that specific listing from your link, but I dropped a pin right on l'avenue Gustave-Eiffel behind the tower and got the code V75W+43 Paris, France. Plus codes appear right under the address line.
Thanks. It seems you have to specify a pin, and not an area to get a plus code.
We display the plus codes in Google Maps on all business listings.
We don't display it on political features or boundaries (typically because having a lat/lng for "France" isn't super useful).
That particular Eiffel Tower result is for the area, not the tower itself, so it doesn't get a plus code.
The entry specifically for the tower, https://g.page/toureiffelofficielle?share, should display the plus code on it.
If you're on mobile, you can get the plus code for any location by just holding your finger on the map, and then expanding the card that appears. It should include the lat/lng and plus code.
Hope that helps!
Re: Open Location Code: An Open Source Standard for Addresses
#40I think triangles would have made more sense.
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?
+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.