<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/05/2015 09:42, André Pirard
wrote:<br>
</div>
<blockquote cite="mid:55506B72.9090209@gmail.com" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<br>
The problem is that if you don't find a phone number you may miss
a phone call but that if you use wrong access or routing tags you
will instantly have GPSes send cars, bikes or pedestrian on the
wrong road.<br>
It's really difficult to have it understood that GPS software
blindly obeys rules and that tags must also strictly obey the same
rules for the GPSes to work. The many many routing tags errors
are a real PITA. Even wrong instructions in the documentation
causing contributors to be misinformed. Is OSM suitable for GPS
????<br>
</blockquote>
<br>
Hell yes* :)<br>
<br>
Seriously, I presume that's a rhetorical question. I've been using
OSM data in a car satnav (in the UK) for years, and when in someone
else's car sometimes end up playing the
"BMW-vs-Google-vs-OSM-on-an-eTrex" game, and (apart from postcodes,
which is a different issue to access tags) OSM pretty much always
wins. I suspect that that might not be the case in e.g. raw
TIGER-infested areas of the US, but in the UK and in Australia I
genuinely haven't had a problem.<br>
<br>
Cheers,<br>
<br>
Andy<br>
<br>
* Sorry, I've been been watching far too much general election
coverage over the last few weeks.<br>
<br>
</body>
</html>