[Talk-us] Best practice in Lane Editing 2

[m at rtijn.org]

For the ‘dashed line’ center turn lanes: what you do makes sense to me too. I have used center_turn_lane=yes in the past, but that is not documented and I wouldn’t encourage it. This way it fits nicely into the lanes schema.

The turn lanes plugin seems to support this nicely: https://www.dropbox.com/s/8wmp5h2cn931pic/Screenshot%202017-06-19%2014.33.40.jpg?dl=0 — even though the center lane is rarely marked with left turn arrows, as suggested by the turn lane style.

Martijn

> On Jun 19, 2017, at 5:20 AM, Paul Johnson <baloo at ursamundi.org> wrote:
> 
> In this case, with the dual-direction turn lane, I would label that with lanes:both_ways=1 and turn:lanes:both_ways=left.  If the center lane has two solid lines (making it a flush median), then lanes:both_ways=1 and access:lanes:both_ways=no
> 
> On Mon, Jun 19, 2017 at 6:17 AM, Horea Meleg <horea.meleg at telenav.com <mailto:horea.meleg at telenav.com>> wrote:
> Hello all,
> 
> Me and my Telenav colleagues are editing lane numbers in Detroit area. We found some cases that looks like this (42.43651692568901, -83.51102781049859):
> 
> <image001.jpg>
> 
> Our question is: what is the central lane used for and how do we map it?
> 
> Should we count it as a separate lane and have 3 lanes in this case (one for each direction and one for both directions)
> 
> <image002.png>
> 
> or have only 2, one for each direction?
> 
> <image003.png>
> 
>  
> 
> Thank you,
> 
> Horea Meleg
> 
> 
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org <mailto:Talk-us at openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/talk-us <https://lists.openstreetmap.org/listinfo/talk-us>
> 
> 
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20170619/bd6555c5/attachment.html>