> Next to that we already have this kind of issue with routes with ways > with backward/forward roles anyway. Furthermore, cycle lanes will > always be part of the road, which can also have this left/right > problem, so I don't think this is a specific problem for cycle tracks.
Why shall c/w suffer from the same limitation? Let's avoid this problem right from the beginning and just draw the c/w where it belongs. For sure, I do not want to store all the c/w characteristics within a single underscore connected attribute as subattributes. _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
