Talk:Tag:barrier=block

From OpenStreetMap Wiki
Jump to: navigation, search

Large flower buckets

Does this tag also apply to large flower buckets that are placed on roads as barriers? Example images: [1] [2] [3] --Head 12:43, 31 August 2010 (BST)

Yes, if they were put in place as a barrier to some kinds of vehicle rather than just nice-looking traffic calming. --achadwick 17:06, 26 April 2011 (BST)

Barrier=planter was suggested for large flowerpots on the tagging maillist, or man_made=planter and barrier=block. /Johan Jönsson 20:50, 4 September 2012 (BST)

Gates / any barrier

Also gates (example)? Does this tag apply to any barrier? --Owenh 03:17, 20 April 2011 (BST)

Definitely not: this is quite a specific kind of barrier. See barrier=gate for gates, and barrier=* for lots of different kinds of barrier ☺ --achadwick 17:06, 26 April 2011 (BST)

Default access

Does this type of barrier placed on a middle of highway=service for example means that will stop larger vehicles, but will permit bicycles and pedestrian, or some access=* tags are still needed? --mafiainc 23:58, 06 May 2011

Not sure what to say here, though we probably should say something. Adding some access tags is probably a good idea, you can state motor_vehicle=no, for example. IMO, perhaps this should be the default. --achadwick 14:14, 9 May 2011 (BST)

I agree that motor_vehicle=no (or at least motorcar=no) and foot/bicycle=yes (or permissive). I usually just tag every barrier explicitly with at least motor_vehicle, foot, and bicycle though. --Olejorgenb 21:48, 20 September 2011 (BST)
  • In barrier=bollard we see "access=no, foot=yes, bicycle=yes" by default. I propose to add the same text in this page. Dinamik (talk) 18:14, 24 June 2013 (UTC)
For the obvious cases, each feature, like a bollard, is intended to restrict a certain type or a group of users. Usually third part routing services will create the default rules of such feature. On another hand, a motorcycle'ss restriction may be added to the the bollard or on the way itself (this may change the rendering if a specific code behavior has been integrated).
As for the access tag, it's a shortcut tag for the general access of an element, it should not be used in coordination with other specific access tags, it will confuse how third part services should interpret the combination. It's best to stay simple and harmonize the use of the tags. --SHARCRASH (talk) 13:46, 22 November 2018 (UTC)

block barriers as ways

I wonder why block barriers are only allowed as points. In reality, large lines of concrete blocks could be placed as traffic dividers or to temporarily shape traffic in a particular direction.

Because usually in line they rather form a wall, like bricks joined together form a wall. In practice it changes how users have to deal with the feature. With a single block on a way, pedestrians, cyclists can still use the way, but let's imagine on a temporary junction as you suggested, blocks in line are often intended to restrict pedestrians also because often there are no other safe features yet installed, for example like crossings. We have to think how each of the feature deals with pedestrians, cyclists, normal vehicles, GHV... since this is for a map.--SHARCRASH (talk) 13:36, 22 November 2018 (UTC)