Hi With these default rules, my device (Etrex Legend HCx) renders roundabouts nicely (dark medium line, looks same as 0x04/0x05 line) and has a suitable 'hover' label. No typ file. Ticker On Sun, 2017-02-12 at 11:39 +0000, Gerd Petermann wrote:
Hi all,
the default style contains these rules for roundabouts: # Roundabouts junction=roundabout & (highway=trunk | highway=trunk_link) [0x0c road_class=3 road_speed=2 resolution 18] junction=roundabout & (highway=primary | highway=primary_link) [0x0c road_class=3 road_speed=2 resolution 19] junction=roundabout & (highway=secondary | highway=secondary_link) [0x0c road_class=2 road_speed=2 resolution 20] junction=roundabout & (highway=tertiary | highway=tertiary_link) [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=unclassified [0x0c road_class=1 road_speed=1 resolution 21] junction=roundabout & highway=* [0x0c road_class=0 road_speed=1 resolution 22]
The wanted effect is that the Garmin device/software produces hints like "enter roundabout" or "Take the 2nd right onto" ... The disadvantage is that the roundabout is not rendered.
I replaced all the above rules by junction=roundabout & highway=* [0x0c road_class=0 road_speed=0 resolution 24 continue]
I tried this with car + bicycle routing and it seems to give the expected results (routing hints and rendered roads). Also the --check-roundabouts option doesn't complain.
Alternative might be to keep the distinction of road types for better time estimation, important point is that "resoltion 24 continue " is used.
Comments?
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev