<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2012-11-21 21:26, Ben Laenen wrote :<br>
</div>
<blockquote cite="mid:201211212126.32795.benlaenen@gmail.com"
type="cite">
<pre wrap="">On Wednesday 21 November 2012 20:52:50 sly (sylvain letuffe) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">That's the current state of recommendation, but maybe we could start
discussing it to see if that's a good idea to apply speed limits on roads
inside a bounding polygon
</pre>
</blockquote>
<pre wrap="">
Polygons are a bad idea to map built-up areas. It's not uncommon that there's
a bridge where the road on top belongs to the built-up area, but the road
below does not. Or tunnels going under a built-up area, with the tunnel itself
not part of it.
Ben
</pre>
</blockquote>
I didn't speak of a polygon (closed ways) but of a relation (a set
of ways).<br>
A speed limit on the roads doesn't prevent you driving as fast as
you want in the meadows ;-)<br>
Look at multilinestring, which I see as a swiss-knife way assembly.<br>
<br>
In my mind, such a relation is the way to assign the same tags to a
collection of objects making a whole with regard to those tags. If
we add recursion (nesting), which is very easy to do, that's
powerful.<br>
<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div style="bottom: auto; left: 0px; right: auto; top: 120px;
display: none;" class="translator-theme-default"
id="translator-floating-panel">
<div title="Click to translate"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>