#16898 closed enhancement (fixed)
[Patch] Add man_made=communications_tower
Reported by: | gaben | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 20.06 |
Component: | Internal preset | Version: | latest |
Keywords: | tower communication | Cc: | Klumbumbus |
Attachments (5)
Change History (27)
comment:1 by , 6 years ago
Keywords: | tower added |
---|
comment:2 by , 5 years ago
Keywords: | communication added |
---|---|
Owner: | changed from | to
Presets/MastAndTower supports the tags
follow-ups: 5 6 comment:4 by , 5 years ago
Replying to anonymous:
Also, a validator heuristic can be used if something tagged with:
man_made=tower
material=concrete
- and higher than 100m
it possibly would be a
communications_tower
instead oftower
.
I find many false positive with this search request even with tower:type=*communication*
. Most of them a correctly tagged man_made=tower
as wikipedia shows.
[out:xml][timeout:300]; ( nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["tower:type"~"communication"]; ); (._;>;); out meta;
and filter (type:node ways:1-) OR (type:way parent (type:relation))
(filter is broken, so the second part does not work and ways with membership are not filtered.
Edit: (type:node ways:1-) OR (type:way child (type:relation))
The opposite is definitely more interesting:
[out:xml][timeout:300]; ( nwr["height"~"^[1-9][0-9]$"]["man_made"="communications_tower"]; ); (._;>;); out meta;
finds communications_tower as small as ten meters and all eight tagged wikipedia pages clearly show that these eight are man_made=tower
.
comment:5 by , 5 years ago
Replying to skyper:
…
and filter(type:node ways:1-) OR (type:way parent (type:relation))
(filter is broken, so the second part does not work and ways with membership are not filtered).
Sorry, wrong search. Should be (type:node ways:1-) OR (type:way child (type:relation))
.
follow-up: 7 comment:6 by , 5 years ago
You missed the material=concrete
part. Just checked, it affects 24 objects globally. I consider the heuristic addition a nice to have, but not important.
BTW it was reported by me originally :)
follow-up: 8 comment:7 by , 5 years ago
Replying to gaben:
You missed the
material=concrete
part. Just checked, it affects 24 objects globally. I consider the heuristic addition a nice to have, but not important.
Yes, I missed tower:type=communication
and material=concrete
. material=concrete
will miss some objects without material
tagged.
Strange, I only find 16 objects (Rel: 1 / Ways: 11 / Nodes: 4). Not sure if this check is needed.
Still, I find 202 objects (Ways: 110 / Nodes: 92) with height between 11 and 99 tagged as man_made=communications_tower
. So, in my eyes, this check would make more sense.
BTW it was reported by me originally :)
Sorry, cannot adjust the reporter.
follow-up: 10 comment:8 by , 5 years ago
Replying to skyper:
Strange, I only find 16 objects (Rel: 1 / Ways: 11 / Nodes: 4).
I used your modified query:
nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["material"="concrete"];
For easiness https://overpass-turbo.eu/s/T03
Still, I find 202 objects (Ways: 110 / Nodes: 92) with height between 11 and 99 tagged as
man_made=communications_tower
. So, in my eyes, this check would make more sense.
Yeah, this is probably a better approach.
Sorry, cannot adjust the reporter.
No problem, wrote it here just for the record.
comment:9 by , 5 years ago
Reporter: | changed from | to
---|
follow-up: 11 comment:10 by , 5 years ago
Replying to gaben:
Replying to skyper:
Strange, I only find 16 objects (Rel: 1 / Ways: 11 / Nodes: 4).
I used your modified query:
nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["material"="concrete"];
Ok, you'll find some tower:type=cooling
with this query. Try:
nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["material"="concrete"]["tower:type"="communication"];
comment:11 by , 5 years ago
Replying to skyper:
Ok, you'll find some
tower:type=cooling
with this query. Try:
nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["material"="concrete"]["tower:type"="communication"];
I haven't found a single one, can you please give at least one OSM id?
by , 5 years ago
Attachment: | josm_16898_tower_example.osm added |
---|
tower with height 100 or higher and material=concrete
comment:12 by , 5 years ago
This is the result of nwr["height"~"^[1-9][0-9][0-9]"]["man_made"="tower"]["material"="concrete"];
:
josm_16898_tower_example.osm
follow-up: 16 comment:13 by , 5 years ago
How about adding validator tests for:
man_made=tower
withouttower:type
: Suggesting to addtower:type
man_made=tower
,tower:type=communication
,material=concrete
andheight
over 99 meters: Suggesting to useman_made=communications_tower
man_made=communications_tower
andheight
below 100 meters: Suggesting to useman_made=tower
andtower:type=communication
Only problem, I see, is that you might get a second warning after adding tower:type=communication
to a man_made=tower
, material=concrete
and height
over 99 meters.
comment:14 by , 5 years ago
Owner: | changed from | to
---|---|
Summary: | Add man_made=communications_tower → [Patch] Add man_made=communications_tower |
I made a patch for the validator part, see josm_16898.patch. The preset part is covered in #17818.
comment:15 by , 5 years ago
josm_16898_v2.patch includes possible decimal numbers and m
as unit for height
Not covered, yet, are feet and inches.
follow-up: 18 comment:16 by , 5 years ago
Find final validator patch: josm_16898_v3.patch
adds warnings for:
man_made=tower
withouttower:type
man_made=tower
,tower:type=communication
,material=concrete
andheight
100 m or above, respectively 328 ftman_made=communications_tower
andheight
below 100 m, respectively 328 ft
comment:17 by , 5 years ago
Cc: | added |
---|---|
Milestone: | → 20.06 |
comment:18 by , 4 years ago
Replying to skyper:
man_made=tower
,tower:type=communication
,material=concrete
andheight
100 m or above, respectively 328 ftman_made=communications_tower
andheight
below 100 m, respectively 328 ft
There is no strict rule in the wiki that towers >100m must be communication_towers and <100m towers.
"It is often made from concrete and usually a far visible landmark. An indication could be a height greater than 100 meters. "
I would not warn about values around 100m. For the only 25 towers >100m a rule is anyway not really needed. The other way round, communication towers < ≈75m a warning would be useful imo.
by , 4 years ago
Attachment: | josm_16898_v4.patch added |
---|
version 4 only warning about communications_tower < 75m
see #8076