From e5e1fcdc9606310997567215a8b2681bae333fff Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 02:23:46 +0100 Subject: [PATCH 01/10] Update 01-nodes.osm --- tutorial/01-nodes.osm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorial/01-nodes.osm b/tutorial/01-nodes.osm index 34a1d4d..5b96654 100644 --- a/tutorial/01-nodes.osm +++ b/tutorial/01-nodes.osm @@ -29,12 +29,12 @@ If you define a bounding box using a fixed set of points, then the query will only ever use that geographic area. But sometimes you want to run a query over whatever section of the map you're currently looking at. -The Overpass Turbo IDE provides a third way to define a bounding box. But automatically +The Overpass Turbo IDE provides a third way to define a bounding box, by automatically inserting the coordinates for the current map view into your query. This is specified by including the "`{{box}}`" shortcut instead of the coordinates. Overpass Turbo will then adjust your query before its run. -This won't happen if you submit a query directly to the API. Its only a feature of the IDE. But +This won't happen if you submit a query directly to the API. It's only a feature of the IDE. But helpful when you're writing queries interactively. When should you use the different variations? From 12c4d1839183a49ad3a65e13d4a203d07b6ed4de Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 02:32:22 +0100 Subject: [PATCH 02/10] Update 02-node-output.osm --- tutorial/02-node-output.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/02-node-output.osm b/tutorial/02-node-output.osm index 5c761ea..860141d 100644 --- a/tutorial/02-node-output.osm +++ b/tutorial/02-node-output.osm @@ -44,7 +44,7 @@ node; //...and output data about those nodes -//Outputing ids only means Overpass Turbo can't draw you a map, +//Outputting ids only means Overpass Turbo can't draw you a map, //you'll just get some XML output out ids; From fe528521643dca3cb31ba2abcb129fc5773a64e4 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 03:16:11 +0100 Subject: [PATCH 03/10] Update 10-the-default-set.osm --- tutorial/10-the-default-set.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/10-the-default-set.osm b/tutorial/10-the-default-set.osm index 34fdee7..1a97a62 100644 --- a/tutorial/10-the-default-set.osm +++ b/tutorial/10-the-default-set.osm @@ -22,7 +22,7 @@ and produce output from multiple named sets of results. */ [bbox:-25.38653, 130.99883, -25.31478, 131.08938]; -//find nodes within out bounding box that have a name +//find nodes within our bounding box that have a name //and write the result to the default set node["name"]->._; From 1ec64d855a94290bd3ca6e607bff8eda3f58fc87 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 03:33:04 +0100 Subject: [PATCH 04/10] even number of values, but any number of pairs --- tutorial/14-searching-by-polygon.osm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorial/14-searching-by-polygon.osm b/tutorial/14-searching-by-polygon.osm index bb6ae96..4f41962 100644 --- a/tutorial/14-searching-by-polygon.osm +++ b/tutorial/14-searching-by-polygon.osm @@ -3,8 +3,8 @@ OverpassQL supports searching for features within a polygon defined by a collect points. The `poly` filter accepts a single parameter. This must be a string value that -contains an even number of latitude and longitude pairs. Collectively these -coordinates should define a closed shape on the map. +contains latitude and longitude pairs. Collectively these coordinates should define a +closed shape on the map. This polygon is then used as the boundary for the query. From 26f913f4377b37e19d52acaae9d309d0e2b71313 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 22:23:18 +0100 Subject: [PATCH 05/10] Update 16-ways-and-their-nodes.osm --- tutorial/16-ways-and-their-nodes.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/16-ways-and-their-nodes.osm b/tutorial/16-ways-and-their-nodes.osm index 9f87b9b..a10c0dd 100644 --- a/tutorial/16-ways-and-their-nodes.osm +++ b/tutorial/16-ways-and-their-nodes.osm @@ -5,7 +5,7 @@ their outline. In OverpassQL we do this using the "recurse down" statement "`>`". This statement takes an input set of elements and then finds any -node (or way, or relation) that are a member of those elements. +node (or way, or relation) that is a member of those elements. The members of a way are its nodes. From fda3a673bd4fcdd8dccc1a4d52aa512298744958 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 22:25:35 +0100 Subject: [PATCH 06/10] Update 17-ways-and-their-tags.osm --- tutorial/17-ways-and-their-tags.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/17-ways-and-their-tags.osm b/tutorial/17-ways-and-their-tags.osm index 0bd88e2..0910b76 100644 --- a/tutorial/17-ways-and-their-tags.osm +++ b/tutorial/17-ways-and-their-tags.osm @@ -6,7 +6,7 @@ That includes filtering them based on their tags. Or using them to search nearby on the map. The query below selects just those ways in our bounding box that have been -tagged as a tourist attraction. As the time of writing, that results in a +tagged as a tourist attraction. At the time of writing, that results in a single way which marks out the boundary of Uluṟu. See the query comments for other variations to try, including finding From 96de4c79e4cfc34b2f0b4ecdde6bfa5226d2fc8a Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 22:45:56 +0100 Subject: [PATCH 07/10] Update 20-relations.osm --- tutorial/20-relations.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/20-relations.osm b/tutorial/20-relations.osm index 52701f7..9ade207 100644 --- a/tutorial/20-relations.osm +++ b/tutorial/20-relations.osm @@ -6,7 +6,7 @@ Relations are collections of nodes and ways. They describe logical groupings of objects that go beyond their basic spatial relationship. For example a relation can be used to describe: -* a bus route, which connects a set of bus stop (nodes) and ways (the route) +* a bus route, which connects a set of bus stops (nodes) and ways (the route) * an administrative boundary * a multipolygon, such as a collection of buildings that represent a single location From 2058822ade90643c93ce2c8323507d6101156883 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 23:03:09 +0100 Subject: [PATCH 08/10] Update 22-areas.osm --- tutorial/22-areas.osm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tutorial/22-areas.osm b/tutorial/22-areas.osm index 7f26ed9..dadeadf 100644 --- a/tutorial/22-areas.osm +++ b/tutorial/22-areas.osm @@ -47,7 +47,7 @@ way(area); ``` The `area` filter restricts the ways (or nodes, or relations) we're interested in -to just those that within an area we've already found. This type of spatial query +to just those within an area we've already found. This type of spatial query isn't normally available for ways and relations. I presume this is to limit the amount of indexing required to support this type of query. @@ -55,7 +55,7 @@ The `area` query and the `area` filter both work with named sets. By default the with the default set (`_`). And this is what the example query uses. But an alternate way to write this example is to explicitly store the area we're -interested in a named set. I find this a bit clearer in practice. +interested in in a named set. I find this a bit clearer in practice. Here's how this would look, using a named set called `ourArea`: From e8b335da702c3ea376e50b74fe1ab3bb2f1481c9 Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 23:30:43 +0100 Subject: [PATCH 09/10] update area name --- tutorial/22-areas.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/22-areas.osm b/tutorial/22-areas.osm index dadeadf..49fa25b 100644 --- a/tutorial/22-areas.osm +++ b/tutorial/22-areas.osm @@ -60,7 +60,7 @@ interested in 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"]; >; From 55655a655c0e63bb55cf03a53afa90ebaf23099b Mon Sep 17 00:00:00 2001 From: Fabian Iwand Date: Thu, 27 Mar 2025 23:38:30 +0100 Subject: [PATCH 10/10] Update 24-mapToArea.osm --- tutorial/24-mapToArea.osm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorial/24-mapToArea.osm b/tutorial/24-mapToArea.osm index 6348dfa..f1c3552 100644 --- a/tutorial/24-mapToArea.osm +++ b/tutorial/24-mapToArea.osm @@ -16,7 +16,7 @@ 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 +We then do a couple of type agnostic queries to find nodes, ways and relations that are tagged as buildings or leisure areas. @title 24 - Find the area derived from a feature