4
1

There is a road near me, which is permanently blocked off by a fence (see picture).

Picture of a road with a fence across it.

I'm wondering if this should be mapped as a single way with a barrier as that is physically what is present on the ground, or with two ways as there is no join for any type of traffic.

I'd prefer the first option because it physically is a single road but I can't find an appropriate barrier type. I don't want to use a gate barrier (which you can tag a node to be) because that would imply the possibility of opening it.

Currently, I have gone for the second option of splitting the way into two that don't quite meet and putting a fence barrier between them.

asked 13 Sep '12, 21:36

Dominic%20Hosler's gravatar image

Dominic Hosler
111248
accept rate: 0%


While the second option makes a lot of sense, there's nothing wrong with a barrier=fence on a node. You can add an access=no for good measure, but it's not strictly necessary.

permanent link

answered 14 Sep '12, 09:49

Vincent%20de%20Phily's gravatar image

Vincent de P... ♦
17.0k15147243
accept rate: 19%

This is of course correct, but unfortunately most routers just ignore barrier and access tags on nodes.

(14 Sep '12, 09:59) scai ♦

I'm not sure that "most" routers do this - by volume I'd expect that most users are using the Garmin / mkgmap combination which as I understand it can be made to support barrier access.

(14 Sep '12, 11:05) SomeoneElse ♦
3

If that's the case then most routers need to be fixed ? Barriers on nodes are common (bollards for example), and access should obviously be heeded.

It's as basic as oneway streets, so I would expect it to be supported.

(14 Sep '12, 15:18) Vincent de P... ♦
1

That's completely true, Vincent. SomeoneElse: As far as I know most online routers ignore barrier nodes as long as there is no access tag at all, only OSRM treats an absent access tag as access=no.

(14 Sep '12, 17:27) scai ♦

I have accepted this answer because the principle of OSM (and I agree) is to map what is there as correctly as possible. It is up to the renderers and navigators to use the information to their liking. If it takes a while for "most" routers to catch up and stop ignoring barrier and access tags on nodes, then people should use a better router / improve the router. This way when the routers do improve, people have accurate mapping data to rely on.

(16 Nov '12, 14:43) Dominic Hosler

That particular barrier basically represents a road cut, thus option number two would be the perfect thing to do.

permanent link

answered 13 Sep '12, 23:46

JCsM's gravatar image

JCsM
101349
accept rate: 0%

I think your second option - unconnected ways, linear fence barrier between them - is the better choice because it is likely to produce more desirable results in mainstream applications. From a theoretical point of view it can be justified by interpreting this situation as a road cut, rather than a barrier.

It's still a tradeoff, though, rather than either solution being a "perfect" choice with no drawbacks: A few use cases will be negatively affected by the second option, realistic rendering being one of them. But these effects are likely relatively minor.

permanent link

answered 14 Sep '12, 06:26

Tordanik's gravatar image

Tordanik
10.6k1294131
accept rate: 34%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×819
×157
×139
×44

question asked: 13 Sep '12, 21:36

question was seen: 4,521 times

last updated: 16 Nov '12, 14:43

powered by OSQA