<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi all,<br><br>I see some cases where the automatic naming of "service roads" causes<br>problems.<br>Maybe you can help me to find better heuristics.<br><br>The target is to produce data that enables Garmin software to <br>find an address / a house when OSM data shows an address.<br>Now, often houses have a tag addr:street=xyz, but the closest<br>road(s) don't have the name xyz.<br>This happens when<br>1) an unnamed service road or footway is connecting the house with a road named xyz<br>2) unnamed cylceways / footways are between the house and the named road<br>3) typos in the addr:street tag or the mkgmap:street tag prevent a clear match,<br>e.g. the road is named "Alte Chausseestraße" and the houses have <br>(probably wrong) "Alte Chaussestraße" (single e),<br>or the addr:street tag is completely wrong, means, no street with a name like<br>that is close.<br>4) a named road is close to one side of the house but an unnamed track/footway<br>is closer on an other side.<br><br><br>I think 1) is clear, we want that Garmin address search points us to a point on the service road.<br>In case 2) I would prefer to find the named road, but it seems to cause no problems<br>when mkgmap uses the closer way and gives it the name of the named road,<br>at least as long as both roads are more or less parallel lines.<br>Case 3) is a bit funny. The unnamed road will be used and address search will<br>find the address as long as you type the (probably) wrong name.<br>In trunk, these houses are ignored, which is sometimes better, sometimes not.<br><br>Case 4) is causing real trouble. We don't want to be routed to the these roads,<br>but up to now I found no rule(s) to distinguish them from 1) or 2)<br>besides the tag mkgmap:numbers=false . <br><br>Any ideas ?<br><br>Gerd<br><br><br><br> </div></body>
</html>