Finally I found a solution that works:
highway=* & ( oneway=yes | oneway=1 | oneway=true | oneway=-1) &
(cycleway=opposite | cycleway=opposite_lane)
{set oneway=no; set access=no; set bicycle=yes} [0x?? road_speed=? road_class=?
continue]
The navigation was messed up by setting the direction to oneway=-1 or
oneway=yes, routing works perfect now if setting oneway to NO, like Felix
already suggested.
To make the rules more compact, you can think of setting this rule at the
beginning of the line style:
( oneway=yes | oneway=1 | oneway=true | oneway=-1) &
(cycleway=opposite | cycleway=opposite_lane | cycleway=opposite_track |
oneway:bicycle=no | bicycle:oneway=no)
{add cycling=twoway}
And then for each road type, for example:
highway=unclassified & cycling=twoway {set oneway=no; set access=no; set
bicycle=yes } [0x06 road_class=3 road_speed=5 resolution 22 continue]
highway=unclassified [0x06 road_class=3 road_speed=5 resolution 22]
If bike navigation is chosen, the first rule applies. Bicycles can route
through the opposite direction, no matter if oneway=yes or oneway=-1 (of course
only in the case of cycleway=opposite, opposite_lane or whatever).
If the navigation is set to cars, routing is following the normal oneway rules.
Cheers,
Minko
----------
Henning wrote:
Hi,
all you need is:
highway=* & ( oneway=yes | oneway=1 | oneway=true ) & cycleway=opposite
{set oneway=-1; set access=no; set bicycle=yes} [0x?? road_speed=?
road_class=? continue]
and
highway=* & oneway=-1 & cycleway=opposite {set oneway=yes; set
access=no; set bicycle=yes} [0x?? road_speed=? road_class=? continue]
Henning
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
