<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 all,<br><br>I think the branch is ready as it is. Steve and I are still working on a new <br>algo to calculate the NOD data (routing information), but this doesn't<br>depend on high precision and should be done in a different branch.<br>In short, the branch produces smaller img files with nicer looking<br>lines and shapes and slightly improved routing and requires around 10% more<br>cpu time.<br><br>If I hear no complains I'll merge on March 6.<br><br>Gerd<br>P.S.<br>The more detailed changes in the branch compared to trunk r3072 are:<br>1) the program keeps the higher precision of OSM data ( precision ~ 5 cm, <br>presuming that OSM data is precise) and tries to detect situations<br>where the rounding to Garmin map units (precision ~ 2.4 m)<br>causes distorted lines. The effects are "rounder" roundabouts<br>and "straigter" straight roads. A nice side effect is<br>that the algo drops a lot of points which makes img size smaller.<br>2) polygons with equal attributes are merged and the remaining<br>points are filtered to also remove distortions. The positive effects<br>are <br>- smaller img size<br>- nicer looking buildings, see previous post<br>http://gis.19327.n5.nabble.com/shape-merger-in-high-prec-coord-branch-tp5793093.html<br><br>A negative effect of the current implementation is that two different algos<br>are used for lines and shapes, e.g. coastlines may differ from the sea shapes.<br>It is planned to correct that in the near future .<br><br>3) Restriction relations are no longer written in a format that prohibits pedestrians <br>and emergency (unless the style requests that)<br>4) the code for the option --link-pois-to-ways was rewritten, see<br><a href="http://gis.19327.n5.nabble.com/Patch-v2-link-pois-to-ways-and-restrictions-tp5791299.html" target="_blank">http://gis.19327.n5.nabble.com/Patch-v2-link-pois-to-ways-and-restrictions-tp5791299.html</a><br><br>5) a few optimizations and corrections in the NOD data reduce the size<br>of the NOD file and seem to correct some routing problems. <br>This is not related to high-precision.<br><br>6) Precompiled boundary and sea data is ~30% larger as it contains more points,<br>and also calculaion time for them increased (this is related to higher precision). <br>It is probably possible to change that also, for now that means larger downloads.<br><br><br><br> </div></body>
</html>