[mkgmap-dev] [PATCH] Bicycle routing opposite to oneways for cycleways tagged as "opposite_*"
From Stefan Wenk stefan.wenk at gmx.at on Sun Feb 22 06:40:46 GMT 2009
Hello Christian, thanks for your suggestion: > I think the problem is that there is no rule which makes a cycleway a > cycleway in the default style. What about changing > highway=cycleway [0x16 road_class=0 road_speed=1 resolution 23] > into > highway=cycleway { add motorcar=no; add hgv=no; add motorcycle=no } > [0x16 road_class=0 road_speed=1 resolution 23] I have tested your suggestion and it does not make a difference. I think that the device does not accept any of these tags if the destination is located at that specific way. Even with the commercial card the device directs a car into a track in a forest if the destination is in the forest located at that track and cannot be reached via an "official" car road. I think the problem is that the device is searching for a destination located at the cycleway, and not at the original oneway. Grüße Stefan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090222/aa7221f5/attachment.html
- Previous message: [mkgmap-dev] [PATCH] Bicycle routing opposite to oneways for cycleways tagged as "opposite_*"
- Next message: [mkgmap-dev] [PATCH] Bicycle routing opposite to oneways for cycleways tagged as "opposite_*"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list