<html>
<head>
</head>
<body class='hmmessage'><div dir='ltr'>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Hi all,<br><br>I've reviewed the problem reported by Stephen:<br>http://gis.19327.n5.nabble.com/ontario-canada-maps-tp5798080.html<br><br>The error message is:<br>There is not enough room in a single garmin map for all the input data<br> The .osm file should be split into smaller pieces first.<br><br>The problem has at least two reasons:<br>1) A mapper in that area prefers to create extremely detailed ways like this<br><a href="http://www.openstreetmap.org/way/188276794" target="_blank">http://www.openstreetmap.org/way/188276794</a><br>(the river is ~ 181m long and has 166 points, and many roads in that area are alike)<br><br>2) Stephen uses a style that adds more or less each generated POI to the map.<br><br>With r3128 I've committed a patch that detects duplicate points (in Garmin precision),<br>but that doesn't solve the problem completely, and it only works when --preserve-element-order is <br>active.<br><br>I don't know why Stephen wants all these POI, so maybe <br>the tags like mkgmap:line2poitype=start, mkgmap:line2poitype=end, and mkgmap:line2poitype=mid<br>are not helping him.<br><br>I think a better solution would be to change the POIGeneratorHook so that it generates <br>POI with a minimum distance of e.g. 5m, or at least no equal points.<br>I remember that this was discussed before, but couldn't find it in the archives.<br><br>Gerd<br><br><br><br><br></div>
</div></body>
</html>