<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>see first <br><a href="http://gis.19327.n5.nabble.com/Possible-problem-with-adjust-turn-headings-tp5851790.html" target="_blank">http://gis.19327.n5.nabble.com/Possible-problem-with-adjust-turn-headings-tp5851790.html</a><br>and the discussion starting at<br><a href="http://gis.19327.n5.nabble.com/What-is-the-idea-behind-adjust-turn-headings-tp5851885.html" target="_blank">http://gis.19327.n5.nabble.com/What-is-the-idea-behind-adjust-turn-headings-tp5851885.html</a><br><br>I'd like to remove the code and the option, I think it produces more or less unpredictable results<br>and I found no problems with maps created without the option. I also plan to add a new option,<br>maybe "--fix-sharp-angles", and it might cause trouble if we support both options.<br><br>My understanding is that the --adjust-turn-headings option was created before we <br>merged the "high-prec" branch and before the img format regarding routing info was fully <br>understood. I guess it helped back in 2010 when it was coded but today it just seems <br>to modify some heading values, sometimes creating really wrong routing info when<br>a rather harmless heading change is "amplified" so that Garmin tries to avoid it.<br><br>If you have examples which show that --adjust-turn-headings is needed, please post<br>the OSM ids of the ways, so that I can add the behaviour to the new code for the <br>"--fix-sharp-angles" option. <br><br>Gerd<br> </div></body>
</html>