<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2013-08-21 17:50, fly wrote :<br>
</div>
<blockquote cite="mid:5214E1DA.6040604@googlemail.com" type="cite">Am
21.08.2013 15:13, schrieb Martin Koppenhoefer:
<blockquote type="cite">
Il giorno 21/ago/2013, alle ore 13:35, fly
<a class="moz-txt-link-rfc2396E" href="mailto:lowflight66@googlemail.com"><lowflight66@googlemail.com></a> ha scritto:
<blockquote type="cite">Pleas, do not start to tag these small
areas as closedways/multipolygon.
</blockquote>
reasoning?
</blockquote>
It is clustering the map, hard to split and all editors I know do
better work with lines than with areas and I am not taking about
several
overlapping lines which is another point.
The more essential problem is the visualization of lanes, width
and the
:lanes extension<br>
</blockquote>
It's not a matter of making areas. They just are there.<br>
Are you saying that we should make buildings or properties larger
than they are to avoid the space in between?<br>
Are you saying that we should not describe what's in between to
avoid adding one or two lines to close the area?<br>
Are parkings going to be removed? Or put on a line because editors
prefer lines?<br>
<br>
Strangely enough, the last time I was here, I was almost unanimously
advised to use an area instead of a line for a dam.<br>
And, likely, if you want to avoid splitting, use such small areas
for bridges and the roads will run uninterrupted through it.<br>
That's not the good way to do it, though, look at my SEGMENT
proposition. It would avoid unnecessary relations too.<br>
I have no personal taste about splitting, I just notice that it's
THE perfect nuisance.<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>