> Date: Tue, 25 Mar 2014 13:50:33 +0100
> From: ligfietser@online.nl
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] [Patch v4] distorted lines with make-opposite-cycleways
>
> Maybe you can have a look at the OSM Generic new style maps from garmin.openstreetmap.nl
> We dont use the option make-opposite-cycleways but process it in the style file:
>
> # 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}
>
>
> Gerd wrote:
> > maybe the order is important, but if that is the case,
> > we would have the same problem for cars if I change the order.
> > I also tested routes starting at normal ways, still sometimes
> > MapSource and Basecamp avoid the cylceway and calculate
> > detours.
> > It would be interesting to know how Garmin maps look
> > like in this region. An alternative to the
> > additional way for bikes would be a route restriction
> > for the wrong direction of the oneway
> > with an exception for bikes and pedestrians,
> > but that would be quite complex.
> >
> > Gerd
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev