I was thinking this exact same thing... all that needs to be done is to add shapepoints to segments. Then explicitly allow ways to contain segments with loops, spurs etc.<br><br>Surely what the renderers can or can't currently cope with should not affect development of the underlying data model - in fact would it be better to have some kind of abstraction layer between the raw data and the renderer, because an exact representation of the data is usually the wrong thing to do. (For example, rendering roundabouts as small solid circles, moving roads apart so they do not overlap in the rendering, showing dual carriageways as a single line, etc)
<br><br>Aled<br><br><br><br><div><span class="gmail_quote">On 3/16/07, <b class="gmail_sendername"><a href="mailto:email@example.com">firstname.lastname@example.org</a></b> <<a href="mailto:email@example.com">
firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br><br>On Fri, Mar 16, 2007 at 04:31:59PM -0000, David Earl wrote:
<br>> talked about it in passing in Oxford a couple of weeks ago. I think making<br>> this change this would be unproductive.<br>><br>> However, the concept of adding a higher level structure on top of ways is, I
<br>> think, still desirable; at the same time requiring that Ways are what we<br>> all, I think, now believe they should be and do conventionally, i.e.<br>> contiguous, ordered, unidirectional, non-branching sets of segments.
<br><br>I suggested to the list a while ago the following plan that would not require<br>all editors to be immediately updated. The idea is to extend segments to be<br>paths. This means that an existing editor will not break until a segment with >2
<br>nodes is downloaded. A way then becomes the "superway" or "group".<br><br>i.e.<br><br> Node stays as node<br> Segment becomes an ordered list of two or more nodes<br> Way stays as an unordered collection of segments (now paths).
<br><br>Then, push data from ways back down on to the "segments" again. This can be<br>automated (in fact, I've just written a ruby script that pretty much does that -<br>ways are fairly useless in their current form of not being paths, so it pushes
<br>the data to the segments and then builds paths up from them).<br><br>I think this is the simplest method of updating, without breaking lots of<br>existing stuff.<br><br>> There are then lots of advantages to grouping such ways.
<br><br>Yes.<br><br>> Not much new in this message, but I want to light the match again.<br><br>Totally agree. I also appreciate that it is not an easy thing to be done<br>quickly, so accept that it may take a while to actually happen.
<br><br>Thanks,<br><br>--<br>Matthew<br><br>_______________________________________________<br>talk mailing list<br><a href="mailto:email@example.com">firstname.lastname@example.org</a><br><a href="http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk">