<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Gerd,<br>
</p>
<p>I have used such approach for my bicycle maps and received quite a few negative reports with two routable lines on top of each other, especially near and at roundabouts. A lot of devices will crash (completely shut down) so I'd not recommend this. In Lambertus'
generic new we use an invisible 0x0c line in the typ file and after the roundabout rules the junctions are made unroutable so we don't have two routable lines on top of each other.</p>
<p><br>
</p>
<p></p>
<div><a href="https://github.com/ligfietser/mkgmap-style-sheets/blob/master/styles/generic%20new/lines" class="x_OWAAutoLink" id="LPlnk649124">https://github.com/ligfietser/mkgmap-style-sheets/blob/master/styles/generic%20new/lines</a></div>
<br>
<p></p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Van:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> namens Gerd Petermann <GPetermann_muenchen@hotmail.com><br>
<b>Verzonden:</b> zondag 12 februari 2017 03:39:45<br>
<b>Aan:</b> mkgmap-dev@lists.mkgmap.org.uk<br>
<b>Onderwerp:</b> [mkgmap-dev] roundabouts</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi all,<br>
<br>
the default style contains these rules for roundabouts:<br>
# Roundabouts<br>
junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18]<br>
junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19]<br>
junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20]<br>
junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21]<br>
junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21]<br>
junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22]<br>
<br>
The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ...<br>
The disadvantage is that the roundabout is not rendered.<br>
<br>
I replaced all the above rules by <br>
junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue]<br>
<br>
I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads).<br>
Also the --check-roundabouts option doesn't complain. <br>
<br>
Alternative might be to keep the distinction of road types for better time estimation, important point is that<br>
"resoltion 24 continue "<br>
is used.<br>
<br>
Comments?<br>
<br>
Gerd<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font>
</body>
</html>