Overpass Tutorial
- 00 - The Beginning
- 01 - Finding nodes with a bounding box
- 02 - Outputting data about nodes
- 03 - Filtering nodes that have a tag
- 04 - Find nodes by matching tags and their values
- 05 - Find nodes by applying multiple filters
- 06 - Extracting multiple sets of nodes
- 07 - Calculating differences between results
- 08 - Generating JSON output
- 09 - Generating CSV output
- 10 - The default set
- 11 - Querying a set
- 12 - Searching within a radius using around
- 13 - Using around to filter against a set of results
- 14 - Searching by polygon
- 15 - Finding ways
- 16 - Ways and their nodes
- 17 - Ways and their tags
- 18 - Combining node and way queries
- 19 - Finding ways from their nodes
- 20 - Finding relations
- 21 - Type agnostic queries (nwr)
- 22 - Areas
- 23 - Finding the areas enclosing a feature
- 24 - Find the area derived from a feature
- 25 - Areas via Nominatim search
- 26 - Timeouts and endpoints
25 - Areas via Nominatim search
This query shows another way to search for areas to help filter queries.
The Overpass Turbo IDE provides several extensions to the core OverpassQL language.
We met one of those much earlier in the tutorial. We used {{bbox}} to
automatically define a bounding box based on the current view of the map in the IDE.
Another useful extension is geocodeArea, which is demonstrated in this query.
The extension accepts a search parameter which is used to do a free-text search using the Nominatim API to find the first matching area.
This can be a more flexible way to match areas. Otherwise we are limited to doing matching of tag values using regular expressions.
Just remember this is an Overpass Turbo only feature. If you want to achieve a similar effect in an application you'll need to query both APIs.
| Links | |
| Source File | 25-areas-via-nominatim.osm |
| Authors |
|