<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>attached is a first working version of the patch, please test it with your style.<br><br>I've also uploaded a binary:<br><code><a href="http://files.mkgmap.org.uk/download/277/mkgmap.jar" target="_blank">http://files.mkgmap.org.uk/download/277/mkgmap.jar</a><br><br></code>It implements two new options:<br>--x-fix-sharp-angles <br>(I plan to remove this option when the code is ready, I now think<br>the fixing should always be enabled)<br><br>Is needed to activate the new code.<br>--x-cycle-map<br>Should be used when the map is only usable for cycling and <br>walking, means, all vehicles (except foot) are treated like bicycles.<br>(like with styles from Minko or Felix)<br><br>The patch also removes the code for the option --adjust-turn-headings.<br><br>The important code is in a new class AngleChecker, when you want to see what<br>it does you should enable logging on info level like this:<br>uk.me.parabola.imgfmt.app.net.AngleChecker.level=INFO<br><br>When you find a message like <br>... sharp angle 28° at 38.343434,-0.770673 headings 40° 68° speeds 2 2 dest nodes 311 2103<br>followed by <br>... sharp angle 28° at 38.343434,-0.770673 changing arc with heading 68° -> 85° angle is now 45°<br>you may want to compare the routing results for that location,<br>once with and once without the option. <br>(In Basecamp and Mapsource you can use Ctrl+T to jump to the location<br>printed in the msg)<br><br>While testing the code I found one problem in OSM data:<br>Sometimes roads are duplicated, means, one road (or a part of it) <br>hides the other. I consider this as a potential error in the OSM data,<br>so a warning like this is produced:<br>WARN: uk.me.parabola.imgfmt.app.net.AngleChecker 63240007.o5m: sharp angle < 1° at 38.355308,-0.483420 ,maybe duplicated OSM way with bearing 359°<br>The message doesn't contain any OSM Id because often the<br>available Ids are missleading due to the merging of roads.<br>I use JOSM to fix these errors:<br>Use Ctrl+J to jump to the given position (38.355308,-0.483420) and <br>download a small area around the point. Next, use Alt+left mouse click <br>multiple times on the node to see the connected roads.<br><br>Gerd<br><br><br><br><br><br> </div></body>
</html>