Logo OpenStreetMap OpenStreetMap

traffic_calming and lanes key tag

Diposkan oleh Super-Map pada 22 Febuari 2015 dalam English Last updated on 23 Febuari 2015.

This is an example of traffic calming = island, we need only to draw one way and not two with several tag one it.

osm.org/go/0BOmSL3lB-?m=

On this picture (the link below), you can see the lanes (numbers of lanes forward/backward and turn lanes) the result in the software and the mark on the real road (it isn’t a trunk and motorway), so in the middle it’ isn’t a “guard_rail” so we can considered that like a “traffic_calming = island” (the road in the bottom is a bus way and we can’t turn on it probably we can use a relation with “no turn” on it)

http://i.imgur.com/qDHDy6b.png?1

Before changeset: http://imgur.com/d8bPCdY

After changeset http://imgur.com/aM64YF4

Lokasi: Lieusaint, Melun, Seine-et-Marne, Ile-de-France, Metropolitan France, 77127, France
Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Ulasan RobJN terhadap 23 Febuari 2015 pada 00:34

I don’t agree with this change. A traffic island is a very small area, whereas this example is along the entire road. In my opinion it should be mapped as two ways (like it was before).

Also worth noting that the road no longer properly connects at it’s southern end.

Ulasan Super-Map terhadap 23 Febuari 2015 pada 07:04

I’m sorry but some time a traffic calming is a little bit more broad, in this case, it’s not a trunk or motorway…

Ulasan StephaneP terhadap 23 Febuari 2015 pada 09:47

I agree with RobJN, in this case it’s not a traffic calming because this separator is not here to “calm” the traffic.

Ulasan RobJN terhadap 23 Febuari 2015 pada 16:13

It doesn’t have to be a trunk or a motorway. The point is that there is a strip of land between the lanes and as such you cannot make a u-turn. For reference both Google Maps and Bing Maps show this as two ways (I’m not copying here as that is how we had it in OpenStreetMap until a few days ago). I would recommend a revert, or at least discussing on the mailing lists before making changes like this.

Log masuk untuk meninggalkan komen