[Tagging] RFC: more barrier types

[M∡rtin Koppenhoefer]

2010/9/20 Tobias Knerr <osm at tobias-knerr.de>:
> M∡rtin Koppenhoefer wrote:
> * Couldn't we just use barrier=rope/chain on ways, too? Introducing
> barrier=post_and_rope/post_and_chain for this seems unnecessary.


yes, I agree, actually someone else put this value there


> * Isn't a guardrail a linear feature? It should be possible to use this
> on ways.

yes
yes, use them on ways (I'd allow nodes as well, but it is preliminary
mapping, I agree)


> * barrier=curb has an area element type. This seems /somewhat/
> excessive, especially since none of the other barriers has.


I'd not expect many of them, but there might be cases where it is
needed for micromapping (I noted these broad and long lowered kerbs in
Amsterdam, which permit easy bicycle movement along the kerb).
Generally I'd tag them as ways.


>> There is also an addition for control devices (see subtags on the
>> page) to be part of thyest e proposal.
> That seems like a somewhat different idea - and might be more
> controversial than the rest, or at least for different reasons - , so I
> wonder why it's in the same proposal.


well, it came to my mind when I was adding the full_height-turnstile.
Often they have these kind of devices attached.

cheers,
Martin