Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions tutorial/22-areas.osm
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
/*
This query finds all natural rock formations within Uluṟu-Kata Tjuta National Park.
This query finds all natural rock formations within Uluṟu-Kata Tjuṯa National Park.

The results include Uluṟu, Kata Tjuta, Taputji and Mala Kata.
The results include Uluṟu, Kata Tjuṯa, Taputji and Mala Kata.

Kata Tjuta is a more complex rock formation and is represented as a relation in
Kata Tjuṯa is a more complex rock formation and is represented as a relation in
the OSM database. So if we had used only a `way` query then it wouldn't be present
in the results. The `wr` query lets us do a type agostic query to find the areas
of interest.
Expand Down Expand Up @@ -34,7 +34,7 @@ using the standard range of filters.
For example in this query we're finding an area based on its name.

```
area["name"="Uluru-Kata Tjuta National Park"]
area["name"="Uluṟu-Kata Tjuṯa National Park"]
```

The advantage of using areas rather the original ways and relations is that the API and
Expand All @@ -60,7 +60,7 @@ interested in a named set. I find this a bit clearer in practice.
Here's how this would look, using a named set called `ourArea`:

```
area["name"="Uluru-Kata Tjuta National Park"]->.ourArea;
area["name"="Uluṟu-Kata Tjuṯa National Park"]->.ourArea;
(
way(area.ourArea)["natural"="bare_rock"];
>;
Expand All @@ -82,7 +82,7 @@ relation(area.ourArea);
@title 22 - Areas
*/
//find any area with this name
area["name"="Uluru-Kata Tjuta National Park"];
area["name"="Uluṟu-Kata Tjuṯa National Park"];
(
//find any ways and relations that are WITHIN that area, filtering them by their tag
wr(area)["natural"="bare_rock"];
Expand Down