On 4/16/07, <b class="gmail_sendername">Artem Pavlenko</b> <<a href="mailto:artem@mapnik.org">artem@mapnik.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><br><div><span class="q"><div>On 16 Apr 2007, at 12:00, 80n wrote:</div><br><blockquote type="cite">On 4/16/07, <b class="gmail_sendername">Robert (Jamie) Munro</b> <<a href="mailto:rjmunro@arjam.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
rjmunro@arjam.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> -----BEGIN PGP SIGNED MESSAGE-----
<br>Hash: SHA1<br><br>Artem Pavlenko wrote:<br>><br>> 80n,<br>> We don't really need all this crossing segments.<br>> Please, could you explain to me what's wrong with representing features <br>> like 'river with islands' as proper polygons (one exterior and
<br>> n-interior rings) ? If you want just a small part of a bigger polygon<br>> for rendering use _clipping_.<br><br>The problem is that none of our existing editors can cope well with <br>editing a way that is big and complicated
e.g. the whole river Thames as<br>a single polygon. If it's multiple polygons, we need a way to join them,<br>which is the crossing segments. It's a similar problem to coastlines. </blockquote><div><br><br>No you don't need to join them. You can use the feature/bug that ways do not require segments to be contiguous. You can hop from one side of the river to the other and you can hop from the riverbank to an island without needing segments to connect them together.
<br><br>Logically a way is made up of one or more sub-paths. Each non-contiguous segment implicitly defines the start of a new sub-path.<br><br>If we ever get rid of segments then, in this scenario, the way would become a super-way and each sub-path would become a way.
<br><br>The concept of a path comprising of sub-paths is well defined in the W3C specifications and the rendering behaviour of such a path is also well defined. It seems like a good model to use and is better than re-inventing the wheel (unless someone invents a better wheel).
<br><br>80n<br><br></div></div></blockquote><div><br></div></span><div>Well, I'm not with you on this one! Rendering is only one aspect of using OSM data. What about spatial analysis? Do you really suggesting to re-invent in that area?
</div></div></div></blockquote><div><br>Artem<br>Rendering is only one aspect of using OSM data. What are the requirements for spatial anaysis? What needs to be represented in the OSM schema and what is currently lacking? What are you trying to achieve?
<br><br>80n<br><br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div>Cheers,</div><span class="sg"><div>
Artem </div></span><span class="q"><br><blockquote type="cite"><div><div><br><br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Robert (Jamie) Munro<br>-----BEGIN PGP SIGNATURE----- <br>Version: GnuPG v1.4.6 (Darwin)<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://enigmail.mozdev.org</a><br><br>iD8DBQFGI1USz+aYVHdncI0RAlVMAJ9+gFeB0q23jLQFlyBHhXfZVod5ygCdGj9F<br>r9qMkGs42vUjaOTn7zJsS6k= <br>=fMVf<br>-----END PGP SIGNATURE-----<br></blockquote></div><br></blockquote></span></div>
<br><div> <span class="q"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<div>Artem Pavlenko</div><div><a href="http://mapnik.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://mapnik.org</a></div><div><br></div><br></span> </span></div><br></div></blockquote></div>
<br>