<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
David Groom wrote:
<blockquote cite="mid:011d01c86a86$8265ca10$6475a8c0@xp1" type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I'll edit the wiki.
</pre>
</blockquote>
<pre wrap="">Could you put some visual examples, please?
</pre>
</blockquote>
<pre wrap=""><!---->
Artem, what i had in mind is now shown on
<a class="moz-txt-link-freetext" href="http://wiki.openstreetmap.org/index.php/Relations/Proposed/Rivers">http://wiki.openstreetmap.org/index.php/Relations/Proposed/Rivers</a>
David G
</pre>
</blockquote>
I'm a bit late in entering this discussion, but at the first glance I
see at least one problem with this proposal: representing tributaries
(<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Strahler_Stream_Order">http://en.wikipedia.org/wiki/Strahler_Stream_Order</a>), which must be
treated separately, since their usually have their own names. Either
you would have to define an OSM way splitting the main river and the
tributary (which in a sense defeats the idea of this proposal) or you
would let the renderer assume that it can draw such a segment by itself
(which can sometimes be problematic, I suppose).<br>
I'm not against letting renderers do their jobs, but I think we should
not presume that all devices will have CPUs powerful enough to provide
interactive maps by processing complex geometry algorithms. Drawing
something like this, for example:
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Image:Mouths_of_amazon_geocover_1990.png">http://en.wikipedia.org/wiki/Image:Mouths_of_amazon_geocover_1990.png</a> :)<br>
<br>
Igor<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://igorbrejc.net">http://igorbrejc.net</a></pre>
</body>
</html>