<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 2014-03-10 13:37, Marc Gemis wrote :<br>
</div>
<blockquote
cite="mid:CAJKJX-TTU1YLfpGMi_Y5NBzLGjgYm=SnALY-XOPLe1F=ASY+4w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>The Humbeeksesteenweg (N211a) was tagged as a tertiary
road.</div>
<div>Recently OsmAnd_pieter changed this to secondary.</div>
<div><br>
</div>
<a moz-do-not-send="true"
href="http://www.openstreetmap.org/way/144119601/history">http://www.openstreetmap.org/way/144119601/history</a><br>
<div><br>
</div>
<div>Is this correct ?</div>
<br>
</div>
</blockquote>
<br>
According to IGN/NGI and the reasoning below, Benedestraat N211a is
(officially) a secondary road.<br>
<br>
The first question is; what is a "primary/secondary/tertiary road?".<br>
And why is it useful to know? To make better GPS routing?<br>
<br>
Tertiary roads are smaller roads used to reach villages or small
towns but not go through them.<br>
Secondary roads are used to go through them, that is, to travel
across the country.<br>
In theory, national roads have a N... number, but their primary
status is often very debatable...<br>
<br>
Belgian national is an administrative classification, but...<br>
There is a national->normally primary road nearby.<br>
Lorries cannot pass (cross) each other without overlapping on the
verge.<br>
There's an alternative wider, officially secondary road: no lorry
problem.<br>
<br>
The IGN/NGI maps (<a href="http://www.ngi.be/testbed/pages">viewable
on their browser</a>) legend (see below) uses a "status" and a
"profile" (width) classification. The width seems to be used for
local roads only. The tentative correspondence with OSM is as
follows:<br>
<br>
<table cellpadding="2" cellspacing="2" align="center">
<tbody>
<tr>
<th valign="top" align="center">IGN/NGI<br>
</th>
<th valign="top" align="center">OSM<br>
</th>
</tr>
<tr>
<td valign="top" bgcolor="#993399">motorway<br>
</td>
<td valign="top">motorway<br>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#ff0000">national<br>
</td>
<td valign="top">primary<br>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#cc9933">link<br>
</td>
<td valign="top">secondary<br>
</td>
</tr>
<tr>
<td valign="top" bgcolor="#ffff00">local<br>
</td>
<td valign="top">tertiary or residential<br>
</td>
</tr>
</tbody>
</table>
<br>
Can you please see if this correspondence makes sense in your
neighborhood?<br>
<br>
But the real "best GPS route" information in my eyes is <b>to map
the width</b> of the road.<br>
(and to use the administrative classification only for the number
and adorning).<br>
<br>
<b> </b>So, what about, in addition to using this correspondence,<b>
measuring and starting tagging all road widths exactly in Belgium</b>,
and not only local roads?<br>
It's really easy to do, it would be original work, reliable data,
it's very useful and it would give Julien Fastré something to trade
for using the Wallonia data!!! For if we cannot sell OSM data, we
can say that we will do something only if we get that data (to map
the roads we measure) ;-)<br>
<br>
<img alt="IGN legend"
src="http://www.ngi.be/Common/leg10/images/leg1n_10.gif"
moz-do-not-send="true" width="600" height="1118"><br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
</body>
</html>