<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 Steve,<br><br>some styles assign create multiple routable lines for the same OSM way,<br>e.g. to set different road-class or speed values for bike and car.<br>This seems to work, but reg. performanc I see two points:<br>1) We do all kinds of calculations multiple times, e.g. all the bearing<br>calculations and (Douglas-Peucker) filters.<br>2) We save the points for the same line multiple times in the img file.<br><br>A possible alternative would be to have a class that stores<br>the list of points and a list of assigned types, but that would involve<br>a lot of changes.<br>I wonder if the img format allows to store the points only once,<br>means, can we store one NET entry and multiple NOD entries<br>referring to the same NET entry?<br><br>Another point that I don't fully understand:<br>In RoadNetwork.addRoad() we always add the reverse arc for each <br>arc. I wonder why oneway roads are not treated different here,<br>esp. if they have foot=no?<br><br>Gerd<br><br>P.S. A while ago I tried to find out the meaning of the curve data<br>encoded with two bytes. I failed because I was not able to change<br>display tool to read my Garmin map NOD file. I saw too many "sync lost" <br>messages. I guess the format is too different, e.g. NOD header length is<br>0x3f.<br>I have created a local copy of NodConvert that is more up to date. Should<br>I commit that? <br> </div></body>
</html>