<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
As I am against always changing the subject line of discussions, I
resent with the original one.<br>
<br>
But it's also to add that, in my opinion, the tagging must respect
the categories that the national law defines (our code de la
route). There is no point in trying to forcefully adapt foreign
concepts if they do not match.<br>
I don't think there's a concept of built-up area in the Belgian
law and I don't think there's a difference in the definition of an
agglomération whether it resides in a city or in a village (even
if rural sounds like village, this is not poetry).<br>
This all, obviously, doesn't prevent a specific tag like a lower
speed limit overriding the global one.<br>
<br>
(On 2012-11-26 18:21, A.Pirard.Papou wrote :)<br>
</div>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2012-11-23 22:58, Kytömaa Lauri
wrote :<br>
</div>
<blockquote
cite="mid:D312F9ED2DBBD8479518C8D52CD16973DD625498@EXMDB01.org.aalto.fi"
type="cite">
<pre wrap="">If it's just the traffic rules urban vs. rural, there's the tag (with 37 000+ uses)
zone:traffic=**:rural
zone:traffic=**:urban
where ** is the two letter country code.
</pre>
</blockquote>
On 2012-11-26 13:16, Marc Gemis wrote :
<blockquote
cite="mid:CAJKJX-RYrOrtALRr1DpmUw_jCjqrgwdP=c=YMG8vrxmues_Enw@mail.gmail.com"
type="cite">
<div class="gmail_extra"><country_code>:<context>
(where the speed limit is defined by a particular context, for
example urban/rural/motorway/etc.)<br>
</div>
</blockquote>
<br>
<div class="moz-cite-prefix">On 2012-11-26 16:41, Jo wrote :<br>
</div>
<blockquote
cite="mid:CAJ6DwMA662ruQOdNaOMyXWQDZPymmU-4UfyTYL0FZ+92tB3uBw@mail.gmail.com"
type="cite">One week ago I had never heard of the zone:traffic
tags. I didn't have a clue how one could tag streets as part of
built-up area/city limits or out of it. For many years this is
something I have been wanting to do though. So I was glad I
finally learned how it could/should be done in one of the many
discussions started by Papou.
<div> <br>
</div>
<div>zone30 are mostly within built-up area, zone50 and zone70
aren't. I think it's important to distinguish between zoneXX and
built-up area as they occur mostly independent from each other,
so the namespaces also ought to be independent.</div>
<div><br>
</div>
<div>We could use source:maxspeed=BE:zone30 instead of
source:maxspeed=zone30, but since a street already gets
zone:traffic=BE:urban/rural, the BE seems less important in the
source:maxspeed tags.</div>
</blockquote>
<br>
Great finding From Lauri indeed !!!<br>
<br>
But regarding this, where is the complete zone:traffic=BE:* list?
(just one example)<br>
<a moz-do-not-send="true"
href="http://www.code-de-la-route.be/textes-legaux/sections/ar/code-de-la-route/100-art2">In
Belgium, we have more than urban/rural/motorway/etc.</a><br>
<br>
default=<b>rural</b><br>
agglomération=<b>urban</b><br>
autoroute=<b>motorway</b><br>
route pour automobile=<b>?</b><br>
zone résidentielle=<b>?</b><br>
zone de rencontre=<b>?</b><br>
zone piétonne=<b>?</b><br>
chemin réservé à la circulation des piétons, cyclistes et cavaliers=<b>?</b><br>
rue réservée aux jeux=<b>?</b><br>
Abords d'école= Zone 30=<b>?</b><br>
Rue cyclable=<b>?</b><br>
<br>
Each with their regulations details.<br>
<br>
I was lately "sent" to map an alleged Zone30 area and there was no
Zone 30 but a <i><b>zone résidentielle</b></i> which is equivalent
maxspeed-wise but not other-wise (other-regulations-wise).<br>
<br>
If we had a tag such as <b>INCLUDE:BE:...:urban</b> etc. with which
the programs would fetch all the relevant tags like <b>maxspeed</b>
per zone type from a well known per country or WW (world wide)
database object (1) then we would have a clear list and we could
tell the government that they can change details any time without
sending us to work everywhere.<br>
<br>
How could otherwise programs that are supposed to use the OSM data
make sense of a such ever changing global notions without breaking
them down to well-defined concepts such as speed, bicycles, etc...<br>
<br>
That would please both the global view and the piecewise one.<br>
<br>
Wouldn't that stop the zonebabel?<br>
<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
(1) for example some well-known BE relation that would contain a
role=<b>zones</b> or <b>traffic</b> member to a relation that would
similarly contain rural, urban, etc. pointers to nodes that would
contain the tags<br>
<br>
</body>
</html>