<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Gerd, can you explain how addresses are stored in the Garmin maps? Are they millions of individual nodes, or "interpolation ways" with a start and an end? Are they just coordinates, or are they internally linked to a road in some way? Can it handle non-numeric house numbers? Understanding the "target data model" might help to assess all the possibilities we have in interpreting the data from OSM.</p>
<p>Colin</p>
<div> </div>
<p>On 2015-03-01 09:42, Gerd Petermann wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<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?<br /><br />Gerd<br /><br /></div>
<!-- html ignored --><br />
<pre>_______________________________________________
mkgmap-dev mailing list
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
</pre>
</blockquote>
</body></html>