<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 01/16/2013 10:04 PM, A.Pirard.Papou
wrote:<br>
</div>
<blockquote cite="mid:50F715F9.3010800@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi,<br>
<br>
The "Mandatory to follow the direction indicated by the arrow"
description for <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Road_signs_in_Belgium">the
down sloping D1 signals here</a> is (fortunately) incorrect. It
should be "Drive around the obstacle on the side indicated by the
arrow".<br>
<blockquote type="cite">Si le signal présentant une flèche non
coudée, est placé sur un obstacle, il signifie obligation de
passer du côté indiqué par la flèche.<br>
</blockquote>
It's a real blunder of the Belgian highway code to make no
distinction between the horizontal (turn) and down sloping (drive
around) arrow so that very little people know the difference. The
roadworks personnel know it very well, but yet I once saw such an
arrow pointing to the hole they were digging. Plonk.<br>
<br>
Cheers, <br>
</blockquote>
<br>
C3 is also wrong(and incomplete). The sub-sign(onderbord) that
defines the exception on the sign above it has a separate
designation in the traffic code, see:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://verkeerweb.be/verk_Tekns-Borden/onderbord.html#type4bijl2">http://verkeerweb.be/verk_Tekns-Borden/onderbord.html#type4bijl2</a>
but better is
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://www.wegcode.be/wetteksten/secties/kb/wegcode/251-art68">http://www.wegcode.be/wetteksten/secties/kb/wegcode/251-art68</a><br>
<br>
According to the Wiki on road signs, and looking at how they work in
Germany using road-signs plugin in JOSM (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://wiki.openstreetmap.org/wiki/JOSM/Plugins/RoadSigns">http://wiki.openstreetmap.org/wiki/JOSM/Plugins/RoadSigns</a>
) It should be marked as such I think:<br>
<br>
traffic_sign=BE:C3,BE:Type-IV<br>
<br>
This should be done on a way, not a node next to the road(which
marks the physical), when you do this on a way , then it is known
what it applies to on that way, e.g the start and is known like
this. They come in pairs usually (but more is possible) marking a
street(~=way) limits, there can be like 3 streets around a square
regulating access to it of course.<br>
<br>
Information gets lost as those different sub-signs are all the
same. No distinction is made. Note, these are not the
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
'M' ones (white) (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://www.wegcode.be/wetteksten/secties/kb/wegcode/248-art65#65.2">http://www.wegcode.be/wetteksten/secties/kb/wegcode/248-art65#65.2</a>
) . Signs like 'Uitgezonderd plaatselijk verkeer', probably the
most common. So, the blue ones.<br>
<br>
So they seem to make no distinction between an possible other blue
subsign, marking an exception. Tagging the way 'access=destination'
is still fine of course, but when you want some meaningful road
signs data -used in routing software and other customer- the ones
put on a way are far more useful. A separate node (away from the
way) marking the physical location of such a sign is of less value
IMHO.<br>
<br>
So Type-IV can be 'uitgz. bus' or 'uitgz. plaatselijk verkeer',
etc. you don't know when parsing this OSM data, as there is no
official distinction.<br>
<br>
Glenn<br>
<br>
Note, I'm using Type-IV out of sheer lack of precedents. It could
be T-IV, all lowercase, uppercase, no dash, whatever we agree on is
fine. I'm probably did like 4 ways like that around the corner
here, primarily to port the XML road sign definitions from the
German implementation to a Belgian one, which is painstakingly
progressing slow.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>