Can someone give an example? I don't understand this proposal. Anthony 04:48, 1 February 2010 (UTC)
- +1 Me neither. I think an exemple "in real life" + "as an .osm file" could help us understand the idea and how to tag it. sletuffe 14:24, 28 March 2011 (BST)
- +1 second that. please provide two or three real life examples with links to the IDs in the OSM database and/or provide some mockup screens. i think that would help non native speakers like me a lot. --Flaimo 12:19, 11 May 2011 (BST)
Just more barrier attributes ?
If there is e.g a fence or wall between two ways, they can be tagged as e.g barrier=fence on a line and height=*. If the barrier is there they can be mostly tagged as barrier=* Why should I use a relation for that? For lowered kerbs this is more useful, if they are all the same in this street or city, if not, they can be tagged at the particular highway=footway segment. --Fabi2 17:33, 18 April 2010 (UTC)
- the difference is that this proposal lets you do routing across linear connections, i.e. you can model connections between ways without really connecting them (or connecting them for routing before they really connect). Here come the barriers into play. You can define general (this means just tags, no geometry) barriers (e.g. railing, curb) and exceptions (geometry like nodes or ways) from that (lowered_kerb, "barrier=entrance", ...). Tagging them on the footway segment doesn't show where they connect to (e.g. which side in complex situations) and where they exactly are.
- You would be able to draw the barrier explicitly like you describe (but you would not have to - at least not for routing) and simply add it into the relation as barrier together with the adjacent ways. This is maybe not so interesting for barrier=fence but gets more useful for barrier=bollard or barrier=kerb (or example, could be different: barrier=road_marking)
-- Dieterdreist 01:12, 18 May 2010 (UTC)