Placekey is a free and open universal standard identifier for any physical place, so that the data pertaining to those places can be shared across organizations easily.
Placekey creates a common industry standard for identifying any physical place. Eventually, there will be a Placekey for every place in the world, even those without a postal address (school district, county, neighborhood, etc.).
However, Placekey goes beyond just an identifier. It’s a movement of organizations and individuals that prize access to data. Placekey members want geospatial data that is easily joined and combined…because real answers come from combining data from many different sources. It is a philosophy that data should be easy to access and data should not be hoarded. These members believe that data, when combined, can do massive good.
Whether you generate a Placekey via this website or use the Placekey API, it will always be free.*
*Should a business ping the Placekey API with a massive number of requests—in the millions per month, for example—we may invite you to help us cover those computing costs.
Yes. Placekey is meant to be free and used widely.
Over 500 organizations have signed on to support Placekey including Esri, SafeGraph, Carto, and Landgrid. See the full list of Placekey member organizations.
Your request data may be stored to improve the match service and better understand the requests that are resolving to specific Placekeys, but they will never be shared or sold to third-parties.
Here is an example of a complete Placekey:
The What Part consists of two unique character sequences.
The first three (or more) characters refer to Address Encoding, creating a unique identifier for a given address. An address at “555 Main Street Suite 105” will have different Address Encoding than “555 Main Street Suite 106.”
The second set of three (or more) characters in the What Part refers to POI Encoding. If a specific place is already included in the Placekey reference datasets, these characters will be present. The benefit of POI Encoding is that it can point to a specific Point-of-Interest that may have existed at a certain address at a given point in time. While Address Encoding allows Placekey to hone in on a specific address, there’s always the chance that either:
The Where Part, on the other hand, is made up of three unique character sequences, built upon Uber’s open source H3 grid system. This information in the Where Part is based on the center point of that place. In other words, we take the exact latitude and longitude of a specific place and then use a conversion function to determine which hexagon in the physical world contains the centroid of that place. The hexagon is currently fixed at H3’s Resolution 10 (about 15,000 square meters). The Where Part of the Placekey is, therefore, the full encoding of that hexagon.
Geohash uses squares while H3 uses hexagons. What’s so great about hexagons?
Additionally, in some instances, the same space can be represented by multiple geohash encodings of the same length. Geohash encodings can spell out inappropriate words (e.g., “jerk” is a valid geohash) or include ambiguous characters such as “o0il1”.
H3 is also open-sourced and has a permissive software license that encourages open and public development. Because of this, it has a vibrant community of contributions, extensions, and collaboration.
Placekey solves a number of industry problems, most notably:
Placekeys are stable on places.
Of course, places themselves change -- and sometimes they merge with other places. Sometimes, two very different addresses resolve to the same place. And sometimes Placekey will have bugs (we are not perfect).Once you associate a Placekey on a place, we suggest pinging the Lineage API on that Placekey every 3-5 months which will return whether or not the Placekey has changed. In the case where it has changed, you would then re-ping the Placekey API on that place to get the new Placekey.
Not at this time (but coming soon!). Right now, only places with postal addresses have a unique Placekey.
In the future, school districts, neighborhoods, and homes that do not have postal addresses will be represented by a Placekey.
This is the easy part. Just by using Placekey you are helping it become an industry standard. You can also help by following and promoting our social channels, including Twitter, Facebook, Linkedin, and Github (where we welcome your contributions to our open source projects).
Plus Codes are intended to help identify locations and typically represent a 14 meter x 14 meter space (roughly the size of half of a basketball court), but can work at multiple resolutions. They were not built to convey POI-related information whatsoever, nor can they distinguish between places on different floors within a building (i.e. specific apartment units) or individual, smaller POIs within a larger footprint (i.e. Starbucks coffee shop within a Target retail store).
A Placekey can provide all of the information available in a Plus Code but then takes it a big step further by providing an extra layer of POI-related information for added precision that can unlock a wealth of unique insights when joined with multiple datasets.
What3Words is not an open standard and, therefore, cannot be easily used or combined with other datasets to extract meaningful value in the rapidly expanding data marketplace.
With Placekey, we have built an open and uniform industry-wide standard for identifying physical places in a truly hyper-local way—and have also created a better way to enable users to unify multiple data sources around a single Placekey to drive innovation like never before.