[Tagging] tower types, cooling towers, etc.

François Lacombe fl.infosreseaux at gmail.com
Fri Nov 17 15:44:24 UTC 2017


*François Lacombe*

fl dot infosreseaux At gmail dot com
www.infos-reseaux.com
@InfosReseaux <http://www.twitter.com/InfosReseaux>

2017-11-16 18:18 GMT+01:00 Martin Koppenhoefer <dieterdreist at gmail.com>:

>
> I would also like to point out that tower:type=communication_tower is
>> redundant.  Tower:type=communication is sufficient.
>>
> they are describing (physically) very different features, that only have
> the same or similar function from a specific abstract point of view (radio
> communication, actually broadcast = oneway communication). As they are both
> only about radio communication, I find the name generally not well chosen.
>

Just my 2 cts without any ultimate solution:

To go in Mark direction, I think that man_made=* should be usage agnostic.
A tower is commonly described as a really longer vertical infrastructure
compared to its width.
Human can usually go inside, instead of a mast.
The same comparison could be done with building vs cabinets : human can
only go inside the first.

It can be completed by structure=*, material=*, colour, design...

Theoretically, usage can be completed by tower=*, mast=*, pole=* like done
with street_cabinet=* with well known values like : telecom, power,
surveillance, water, and so on to stop confuse usage and structure inside
one single key.
Just beware of power towers or lighting poles to support telecom antennas

Anyway, telecoms (communications, telecommunications, mobile phones, why
not radio broadcast ?) should go in telecom=* key
communication=*, telecommunications=*, communication:telecom=* may be not
used any more for sake of consistency.

To be continued


François
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20171117/cb06955e/attachment.html>


More information about the Tagging mailing list