<br><br><div class="gmail_quote">On Sun, Mar 20, 2011 at 7:30 PM, Mike N <span dir="ltr"><<a href="mailto:niceman@att.net">niceman@att.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 3/20/2011 8:18 PM, Ian Dees wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There were several clients that did not attempt to connect the ways of<br>
each NHD linestring so there are duplicated nodes and ways that touch<br>
but aren't joined. Hopefully fixing this is what Paul was talking about.<br>
</blockquote>
<br></div>
Agreed - this is a safe case of duplicate node removal: when all items touching duplicate nodes are of type hydro - river, stream, lake, reservoir, etc (I forget the exact tag names).<br>
<br>
Just combining segments within the same reach code will frequently produce ways containing > 500 nodes, which makes editing more complicated, and does not make any improvement to the usability of the map data.<br>
<br></blockquote><div>The ways don't need to be *combined*, just *connected*. </div></div><br>