<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 Alexandre,<br><br>thanks. <br><br>Maybe I should point out in what case the complex case is better:<br>1) assume a second road also named ABC and very close to the first one contains<br>numbers 13, 5,15 in that order. This is what I call the "random number" case<br>for which mkgmap has to produce many small intervals in both roads,<br>else Garmin software will show multiple possible places for each number.<br>2) assume there is no other road named ABC in the near, but the numbers<br>1 to 11 are all at the beginning of the road (say first 50 m) while 17 is 500m away<br>on the very end of the road. This is the case where I think mkgmap should<br>add a number node so that the interpolated positions are closer to the houses.<br><br>Gerd<br><br><div><hr id="stopSpelling">Date: Sun, 1 Mar 2015 07:03:22 -0300<br>From: alexandre.loss@gmail.com<br>To: mkgmap-dev@lists.mkgmap.org.uk<br>Subject: Re: [mkgmap-dev] open issues in the housenumber2 branch<br><br><div dir="ltr">Hi Gerd,<div><br></div><div>I agree with you that the trunk approach is the better solution. I think that the second case is difficult to develop and maintain and adds little value in terms of navigation.</div><div><br></div><div>Alexandre</div></div><div class="ecxgmail_extra"><br><div class="ecxgmail_quote">2015-03-01 5:42 GMT-03:00 Gerd Petermann <span dir="ltr"><<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>></span>:<br><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">Hi all,<br><br>during the last days I've analysed the reasons for the error messages reported<br>by some of you. I came to the conclusion that I have to <br>- change the handling of addr:interpolation ways completely<br>- add code to detect the "random number" case earlier and - if detected - <br>use different methods to split the number intervals<br><br>Both are rather complex changes, so I'll need a few days to code this.<br><br>One open question for you:<br>How should we handle "missing" information?<br>If mkgmap finds the numbers 1,3,9,11,17 in that order on the left side<br>of a road called ABC, it can create different housenumber informations.<br>One could be like "odd numbers from 1 to 17 on the left",<br>another could be a more complex sequence <br>1) "odd numbers from 1 to 3 on the left",<br>2)"odd numbers from 9 to 11 on the left",<br>3) "odd number 17 on the left"<br>A search for ABC 5 would either show a point between 3 and 9<br>or two entries with the numbers 3 and 9.<br>The latter tells you that OSM probably doesn't contain the <br>exact information and let's you decide where to search for ABC 5.<br><br>The trunk version tends to the simple info, while r3486 <br>is more likely to produce the complex one.<br>I think trunk is better here, the complex case should only<br>occur if the "random number" case was detected.<br><br>Do you agree?<span class="ecxHOEnZb"><font color="#888888"><br><br>Gerd<br><br> </font></span></div></div>
<br>_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br></blockquote></div><br></div>
<br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>