<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2013-01-04 13:35, Julien Fastré
wrote :<br>
</div>
<blockquote cite="mid:50E6CC7F.20604@fastre.info" type="cite">Hi,
<br>
<br>
The guy split a outer-way into two parts, convert one parts to a
road, and did not add the old part to the multipolygon. So, this
was not closed any more.
<br>
</blockquote>
That's what must happen when one uses the same way for different
kinds of objects.<br>
A change to one of the object destroys the other object
unintentionally.<br>
Either carelessly or by ignorance.<br>
This should be explained to newer taggers.<br>
That's why I carefully detached administrative boundaries from the
Meuse in that neighborhood.<br>
<br>
The same kind of problems often occur with landuse.<br>
I often make corrections to roads that are 10 to 50 m off course,
and even more.<br>
And I find that landuse often attach to everything they can.<br>
Even when crossing a road at 90° will some landuses have a dot in
common with the road.<br>
Consequently, when one segment of the road is moved to the correct
place, the whole landuse moves too.<br>
Well, I'd prefer not to have to cope with landuse too when I'm
correcting roads.<br>
In theory, if they attach landuse to a road, they want the landuse
moved with the road, don't they.<br>
But in doing so, the other attached roads at the other far away side
move too.<br>
In practice, I detach the whole landuse from everything.<br>
<br>
Could this landuse supergluing please stop?<br>
Could their taggers be called back to correct their mistakes?<br>
<br>
Cordialement,<br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>