Talk:Tag:barrier=jersey barrier

Proposal / approval status?

The current page says this tag is approved, but I am unable to find any previous proposal that mentions "jersey_barrier"

There is also a suggestion to use barrier=wall with wall=jersey_barrier on the page for Tag:barrier=wall although this is much less commonly used.

I am going to change the status to "de facto", but please correct this and provide a link to the approved proposal if possible. --Jeisenbe (talk) 23:45, 11 April 2019 (UTC)

I was wrong, there was a proposal. I've fixed the status: Proposed_features/New_barrier_types

Also, we discussed this on the Tagging list, and while the term "Jersey Barrier" is originally American, it does not seem to be a problem for British English; it's just not a common feature there. --Jeisenbe (talk) 13:24, 14 April 2019 (UTC)

"You should also add further tags to more fully specify what kinds of vehicle or foot traffic have reasonably unhindered access using access=*" - this implies that access=* is a physical restriction but as defined on access=* page it's supposed to be a legal one.

Rendering

The development version of OSM Carto now renders barrier=jersey_barrier when used as a way (drawn as generic barrier, e.g. barrier=wall). The significance of barrier=jersey_barrier as a node was felt to be unclear: a (semi)permanent closure af a way would be better mapped as a break in the way, optionally micro-mapped with barrier=jersey_barrier as a way across the break. A single jersey barrier used as a block for vehicle traffic would be more clearly mapped as barrier=block. The discussion is here. Phodgkin (talk) 11:29, 27 January 2024 (UTC)