<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 Andrzej,<br>> <br><div>> Isn't a bigger problem there?<br>> <br>> The situation is that single OSM way creates multiple Garmin ways. This <br>> could be done by copying OSM way or by referencing OSM way for new <br>> Garmin object. Both variants can cause problems.<br>> <br>> If there is a copy, then it could be processed differently, for example <br>> when simplifying. And I think routable roads are processed different <br>> than non-routable. This would lead to misalignment for Garmin objects.<br>> <br>> If a new object uses a reference, then there will be problems like with <br>> reversing. And any other processing of OSM way can lead to some problems <br>> too.<br><br>since r2435 mkgmap always creates copies of the list with the point <br>references, so that reversing of one copy doesn't influence the other copies.<br><br>On the other hand, the routines that remove points (short-arc-removal with value<br>>0 or the wrong-angle-handling in the high-prec-branch)<br>make sure that the changes are applied to the copies as well,<br>and this is done by overwriting the list of points again.<br><br>> <br>> Multiplying of Garmin objects is done by "continue" statement in object <br>> definition. I'm not sure, how this is processed internally in mkgmap, <br>> probably it is using a reference. Maybe would be helpful if we could <br>> select if there should be copy or reference for Garmin object? For <br>> example there could be a statement like "continue_with_copy".<br>What problem do you want to solve with that? Should it reduce memory needs?<br><br>Gerd<br></div> </div></body>
</html>