Talk:Tag:barrier=log

From OpenStreetMap Wiki
Jump to navigation Jump to search
Road into Dalnahaitnach - geograph.org.uk - 1593566.jpg
Log Gate - geograph.org.uk - 258685.jpg

Should this tag be used in barriers like the images on the right? Or this tag is only for logs sitting on the floor? Zermes (talk) 19:07, 4 October 2016 (UTC)

The lower images looks like being a barrier=lift_gate made from a log, i.e. IMHO it's a lift_gate, just like a wooden house is a house not wood/log. In the upper image I cannot recognize any mechanic to move the log, hence I'd map as a log. --Schoschi (talk) 12:35, 26 July 2018 (UTC)

Duplicate

This is a duplicate with barrier=block since by definition and practice it means the same: a large block of something meant to obstruct the passage of users. That something being different is not important as long as they influence all kinds of users in the same way. Also as awkward as it may sound, land managers cut trees intentionally to block passage. Let's compare a block of concrete with a fallen trunk, pedestrians and cyclist are still able to pass quite easily but not 4 wheeled vehicles on both situations.

Also, a cut log, fallen trunk or complete tree with its dense branches blocking passage are different kinds of situations of a same kind of material, therefore i think it is necessary to keep some tag modularity to represent all the possible situations.

Finally, i noticed users using "barrier=block" + "description=fallen trunk" or ="fallen tree" to map such elements. If the element really restricts a kind of user, let's just use the specific access tag per kind of user. For example a fallen tree whith branches dense enough to block passage of cyclists even by carrying the bicycle but not for pedestrians, it would be a node tagged as: "barrier=block" + "natural=tree" + "description=fallen tree" + "foot=yes" + "bicycle=no".

--SHARCRASH (talk) 18:46, 5 December 2018 (UTC)

Mapping as a linear way?

The page currently only allows/recommends mapping as a node, but many are mapped as linear ways. This is not as helpful for routing applications if the way does not share a node with the highway. Should this be updated to say that mapping as a way is possible, but there must be a shared node with the highway, or is it best to just recommend mapping as a node, since the direction or length of the log is usually irrelevant to rendering or routing. --Jeisenbe (talk) 04:22, 10 October 2019 (UTC)

I would think that the ways are being used in a similar fashion to fences. Reubot (talk) 13:42, 3 November 2019 (UTC)
28% of uses are on ways, so I've edited the page to reflect that. I agree with Reubot that it's likely the same as fences. --GoodClover (a.k.a. Olive, GodClovere, ) (talk) 17:15, 19 May 2021 (UTC)