Hi Andrzej, attached is version 7 of the patch. A wrong placed braket ... I think was also wrong with the default style. Gerd cycleway-v7.patch <http://gis.19327.n5.nabble.com/file/n5801219/cycleway-v7.patch> popej wrote
Hi Gerd,
You should not get them without any option unless you modify the style.
I can't trace what is the primary cause of the problem.
I have removed "make-opposite-cycleway" from options and added following lines to default style:
highway=* & ( cycleway=opposite | cycleway=opposite_lane | cycleway=opposite_track | oneway:bicycle=no | bicycle:oneway=no ) { set oppoway=yes } highway=* & ( oneway=yes | oneway=1 | oneway=true | oneway=-1 ) & oppoway=yes {set oneway=no; set access=no; set bicycle=yes; name '${name} (rower)' } [0x10 road_speed=1 road_class=1 resolution 24 continue]
If I compile map with trunk r3129 then I get additional cycleway with name including "(rower)".
If I compile with patched mkgmap, I get two additional cycleways, one with "(rower)" in name, second with "(Cycleway)", exactly like when I use option "make-opposite-cycleway".
No problem with default style - no additional cycleway, when no changes in style.
I have attached modified style, a data sample and a batch for mkgmap. Watch the way: http://www.openstreetmap.org/way/226392273
what about keeping only the make-opposite-cycleway option?
That is the only option, which I use. I don't see advantages of other cycleways options. But maybe there are some?
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
test.7z (68K) <http://gis.19327.n5.nabble.com/attachment/5801217/0/test.7z>;
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v5-correct-make-cycleways-tp5800981p580... Sent from the Mkgmap Development mailing list archive at Nabble.com.