<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> Usually there will be ~100mtres for this where you can<br>
> change at any time, but in OSM you have to decide on one merging<br>
> point.<br> </div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
</div>I haven't seen a proposed scheme yet that really deals with this<br>
properly, they pretty much all pretend that a lane starts at a point.<br>
Personally I don't think that figuring this out is necessary for<br>
having multiple lanes, as we could continue the fiction that they<br>
start at a point. It'd be nice, but not necessary.</blockquote><div><br></div><div>You can usually be accurate if you're not afraid of having overlapping ways. Lanes do start at a point, they just commonly overlap with another lane at that point.</div>
<div><br></div><div>But yeah, even if you get down to the lane level, you're still mapping logically and not physically. If you want to map the physical, I think you've gotta go with a boundary relation: landuse=right_of_way, surface=*. Hopefully you can keep the ways for routing purposes, though.</div>
</div>