Hi Chris, If you use the style files instead of the mkgmap parameter, it is possible (if taxi=yes is supported, I'm not sure). For the world routable 'Lambertus' style file I've tested to get rid of the option 'make-opposite cycleways' and put the following code in the line style, which works well: # make opposite cycleways highway=* & ( oneway=yes | oneway=1 | oneway=true ) & ( cycleway=opposite | cycleway=opposite_lane | cycleway=opposite_track | oneway:bicycle=no | bicycle:oneway=no ) {set oneway=no; set access=no; set bicycle=yes; set 2cycleway=1} [0x10 road_speed=1 road_class=1 continue with_actions] highway=* & oneway=-1 & 2cycleway!=1 & ( cycleway=opposite | cycleway=opposite_lane | cycleway=opposite_track | oneway:bicycle=no | bicycle:oneway=no ) {set oneway=no; set access=no; set bicycle=yes; set 2cycleway=-1} [0x10 road_speed=1 road_class=1 continue with_actions] highway=* & 2cycleway=1 {set access=yes; set oneway=1; set bicycle=no} highway=* & 2cycleway=-1 {set access=yes; set oneway=-1; set bicycle=no} You can add taxi=yes to the first two lines. The line type 0x10 corresponds to cycleways which gets the same line. The last two lines are there to reset the normal situation for other traffic. Bicycles (and taxis=racing bikes) can route only on the first two ways and can access it in both directions. Other traffic will be handled in the lines that are handled later in the line styles (so you need to put this block somewhere at the beginning of your style). Chris wrote: Hi, when using Garmin modes like "Taxi" for special routing (like race-bicycle routing) is there a trick to make "make-opposite-cycleways" working? So that the artifical created way doesn't gets the bicycle but the taxi flags? Chris