diff --git a/ids.md b/ids.md index 1c4a9b0..e958991 100644 --- a/ids.md +++ b/ids.md @@ -12,30 +12,16 @@ A record's `gid`'s in Mapzen Search looks like: **1. Do not use Mapzen Search `gid`'s as permanent identifiers for places.** -`gid`'s in Mapzen Search can change because several of our data sources also lack permanent IDs. Some of our sources do not provide ways to track [...]. - +`gid`'s in Mapzen Search can change because several of our data sources also lack permanent IDs. Some of our sources do not provide ways to track changes between each release of the data. This is particularly true for OpenAddresses, where there are no general ID's for each address. With OpenStreetMap it is possible for an entry to be superseded by another place, but for there to be no indicator of what the replacement place is. **2. The structure of identifiers in Mapzen Search may change.** +This is not necessarily the final configuration of ID's in Mapzen Search. We reserve the right change their structure at some time in the future. - -## Source-specific `gid` structures - -
Source | Examples | Structure | Notes | -
Who's on First | -
-
|
+**3. The Mapzen Search ID for a place may not be the same exact ID in other systems.**
+While some of our sources do have persistent ID's (e.g. Node/Way ID's in OpenStreetMap or all Who's on First ID's), we augment them to fit into our taxonomy and add the source dataset. While the numeric component of a Mapzen Search record coming from Who's on First can be used as its ID, you can't just use a Who's on First ID to get the record from Mapzen Search.
-