pelias
/
documentation
mirror of https://github.com/pelias/documentation.git
1
0
Fork 0
Code Issues Releases Activity
Browse Source

Update /place endpoint ids info 

Connected to pelias/api#541
pull/114/head
Diana Shkolnikov 9 years ago
parent
762c3f056c
commit
82a7c1b868
1 changed files with 3 additions and 6 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 9
      place.md

9
place.md
Unescape View File

@ -2,13 +2,10 @@
When you know an identification number and the source it came from, you can use Mapzen Search to get details on the location. When you know an identification number and the source it came from, you can use Mapzen Search to get details on the location.
To get started with a `/place` search, you need a [developer API key](https://mapzen.com/developers) and these three pieces of information: To get started with a `/place` search, you need a [developer API key](https://mapzen.com/developers).
* source - the data source, such as OpenStreetMap The `/place` endpoint accepts Mapzen Search `gid` strings that get returned for every record in all query responses.
* layer - the type of place, such as a venue, address, or country. These `gid` strings should not be built manually, but rather used directly as-is to lookup additional details on the location that `gid` refers to.
* id - the identification number of the item
If you have all those, join them together with semicolons and pass them in with the `ids` parameter.
For example, this `/place` query looks up the Eiffel Tower in OpenStreetMap (OSM): For example, this `/place` query looks up the Eiffel Tower in OpenStreetMap (OSM):

Write Preview
Loading…
Cancel
Save