<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="font-size: 14px; "><div><div><br class="Apple-interchange-newline">Some very good points here. . .</div></div></span></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Feb 9, 2014, at 10:47 AM, André Pirard wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
I left this unsent for some time, so it may duplicate what has
already been said.<br>
But it's uttermost important.<br>
<snip></div>
<br>
There doesn't seem to be routing quality assurance tools, not even
Osmose detecting detectable mistakes, and I've corrected quite a
number of bad tagging mistakes that I found with Osmand.<br></div></blockquote><div><br></div><div>Osmand is definitely a quality assurance tool for me. I have taken to using its routing facility at every opportunity. When it comes up with a route that makes no sense to me I go back to look at the OSM tagging to look for clues as to why the route was selected. Usually it is bad or missing tagging. In the western U.S. there is still a lot of old Tiger imported data that has not been corrected or added to. Sometimes it is incorrect topology, but often it is simply the lack of speed information as well as the location of stop signs and traffic signals that cause the routing issues.</div><div><br></div><div>Since I'm not willing to setup for generating my own OBF files it takes a couple of weeks for me to see if the fixes I add make any difference.</div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
Many people appear confused with the restriction rules.<br>
There should be a wiki page listing exactly what tags mappers and
routers must use.<br></div></blockquote><div><br></div>That would be very helpful.</div><div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
There should be <a href="http://www.yournavigation.org/index.php">a
tool like this</a> implementing exactly those rules and using an
up to date map, at least daily or almost life (for example on demand
according to the requests) so that mappers can check their doings on
short distances.<br></div></blockquote><div><br></div>Yet another useful web site that I was not aware of until just now. Thanks for the link! And, yes, having a site or tool that can show the routing results on very current OSM data would help a lot.</div><div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
AFAICS, OSM routing is not reliable. It does make useful routes on
the large scale but it makes many errors when coming down to the
details and one may be booked for trusting it too much.<br>
<br></div></blockquote><div><br></div>In the business sector I was in until recently, the phrase "eating your own dog food" seems to apply. That is, use your own products in your production environment to be really sure they are ready for market. I strongly suggest that anyone doing tagging on highways use the OSM based routing tools and when the results don't match expectations find and fix the tagging problem.</div><div><br><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF">
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br></div></blockquote></div><br><div>-Tod</div><div><br></div></body></html>