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
24 - Find the area derived from a feature
The previous example illustrated how to turn an area into a way, so that we
can plot it on the map. For that we used the pivot filter.
Sometimes it can be helpful to go the other way and find the area that
corresponds to a way or relation. To do that we use the map_to_area statement.
This allows us to then do spatial queries using that area, which we can't do with the original way or relation.
For example in this query we find the OSM relation tagged as Mutitjulu.
This is intended to represent an administrative boundary for the Mutitjulu community that is found just east of Uluášu. This is stored in a temporary named set.
We then use the map_to_area statement to find the area corresponding to
that relation. This is saved in a variable called mutitjulu.
We then do a couple of type agnostic queries to find node, ways and relations that are tagged as buildings or leisure areas.
| Links | |
| Source File | 24-mapToArea.osm |
| Authors |
|