[mkgmap-dev] [Patch v5] correct make-cycleways

Wed Mar 26 19:24:32 GMT 2014

Andrzej wrote:
> Version with cycleway created after original road would be quite
> complex, I have dropped this idea.

Here is an example how to do that:

1) block the original highway for cycling:
oneway=* & (cycleway=opposite | cycleway=opposite_lane | cycleway=opposite_track | oneway:bicycle=no | bicycle:oneway=no) {set bicycle=no; set mkgmap:cycleway=yes}

2) use continue with_actions for some roads where we can expect opposite cycleways
highway=unclassified [0x06 road_class=0 road_speed=3 resolution 21 continue with_actions]
continue with_actions also for highway=tertiary, residential, living_street, service

3) create an opposite cycleway, remove the oneway tags and set access open only for bicycle:
mkgmap:cycleway=yes {set access=no; set oneway=no; set bicycle=yes} [0x10 road_speed=1 road_class=1]

4) stop continue processing for those highways without mkgmap:cycleway
(highway=tertiary|highway=unclassified|highway=residential|highway=living_street|highway=service) & mkgmap:cycleway!=yes {delete 'highway'}

The only problem is that when someone starts routing for cycling in a opposite cycleway street, Garmin first thinks it is oneway (doesnt see the underlying mkgmap:cycleway) and at the end of the street, the routing makes a u-turn. See https://www.dropbox.com/s/xikkso92iaszkdb/opposite_cycleway.jpg
Blue arrow: oneway for cars, green for cycling.