On Sun, Sep 27, 2009 at 2:09 PM, Russ Nelson <span dir="ltr"><<a href="mailto:nelson@crynwr.com">nelson@crynwr.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Ruben Wisniewski writes:<br>
> No I'm not only touching this buildings, I tried to fix every doubled<br>
> node. It's the same thing a user would do with a josm validator.<br>
<br>
</div>What is a "doubled node"? Any node which has the same lat/lon as<br>
another node? The US TIGER import created just one node where<br>
limited-access highways crossed local roads at a bridge. Sometimes<br>
I've separated them by selecting the node, and asking JOSM to create<br>
another node. Now, maybe JOSM should move the nodes ever so slightly<br>
apart from each other, but that's in the nature of an improvement to<br>
JOSM.<br>
<br>
It's definitely NOT correct to take two nodes which are at the same<br>
location and merge them, particularly if they're part of two different<br>
ways tagged with different layer= values.</blockquote><div><br></div><div>Right on. Most of the mistakenly doubled nodes probably can't be solved automatically. If the two nodes are contained in more than one way, you don't know if you should merge them or not. If the two nodes are listed more than once, non-consecutively, in a single way, you don't know if you should merge them or not. This latter situation is almost surely a mistake, but the fix may or may not be to merge the nodes. The fix might be to split the way, turn one section of it into a bridge, and add a layer tag, for instance.</div>
<div><br></div><div>If one of the two nodes is contained exactly once in exactly one way, directly consecutive to the other node which is in the exact same location, I guess it's safe to automatically remove the former node. But I'm not sure, so even if you just want to do that I'd suggest writing up a proposal and giving people time to come up with objections first.</div>
</div>