Professional Documents
Culture Documents
Open Location Code: Stop Giving Directions
Open Location Code: Stop Giving Directions
org/web/20180301114837/http://openlocationc…
View on GitHub
Open Location Codes are a way of encoding location into a form that is
easier to use than
latitude and longitude. They are designed to be used like street addresses, especially in
places where buildings aren't numbered or streets aren't named.
Most places just need a six character code and a locality to get an accurate,
unique
reference. For example, this football pitch
in Belo Horizonte, Brazil has the location "Belo
Horizonte 22WM+PW". Try it on
the demo site!
If you don't want to use the locality, you can use the full 10 character code. That
same
football pitch has the full reference 58GR22WM+PW. "58GR" is like an area code
of a
telephone number, and like an area code, if you're in the town (or even near it)
you don't
need it.
Small businesses rely on people being able to find them. This is especially true for guest
houses, because they
are mostly used by people who are not local to the area. If a guest
house provides their location using these codes,
a visitor is able to use that code to go
directly to the location.
Crisis response organisations need accurate location information. These may be existing
buildings (storage warehouses)
or things such as wells that don't have addresses, or
temporary camps that could be long distances from the nearest
road. Latitude and
longitude coordinates are long and prone to errors, leading to wasted time and resources.
Using
short codes that importantly, do not require expensive satellite communications,
could provide such organisations with
improved location information.
Alternatively, if you know someone who would be interested, let them know.
The other methods were mostly designed with different ideas in mind, and
so this isn't a
criticism of them.
Authors
Open Location Codes were developed at Google's Zurich engineering office, and then open
sourced so that they can be freely used.
The main author is Doug Rinckes (@drinckes), with
the help of lots of colleagues including:
Philipp Bunge
Aner Ben-Artzi
Jarda Bengl
Prasenjit Phukan
Sacha van Ginhoven