On Sun, Aug 30, 2009 at 12:20 AM, John Smith <[email protected]>wrote:
> 2009/8/30 Anthony <[email protected]>: > > <way id=....> > > <nd ref=.../> > > <tag .../> > > <tag .../> > > <tag k='lanes' v='2' /> > > <tag k='lanedirection' v='backward;forward'> > > <tag k='maxspeed' v='130;110' /> > > </way> > > That solution would fail to allow us to attach nodes to individual lanes. True but the example did not show why that was needed. Looking at commercial mapping software, the typical solution is to split the way. > Dual carriage ways are physically separated, regardless if that's a > strip of grass or by barriers so I don't see that as an issue in the > same context as being able to tag lanes individually. Or traffic cones, or a painted median. Should the ways model the physical or the logical? Again looking at commercial mapping software, the answer is logical. The question they ask is whether or not you're supposed to be able to make turns or change lanes, not what the physical road description is.
_______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
