Re: [mkgmap-dev] [PATCH] default style: make highway=path equivalent to footway and cycleway
Hi there! Greg Troxel schrieb:
-highway=path {add access = no; add bicycle = yes; add foot = yes} [0x16 road_class=0 road_speed=0 resolution 20] +highway=path & bicycle=designated {add access = no; add foot = yes} [0x16 road_class=0 road_speed=1 resolution 23] +highway=path {add access = no; add bicycle = yes; add foot = yes} [0x16 road_class=0 road_speed=0 resolution 23]
Don't you want a bicyle=yes on the second line, or is that added from a bicycle=designated line elsewhere?
No, I don't think this would help. The "add" keyword means only adding the tag if it wasn't present before, right? So before my change, an already existing bicycle=designated wasn't change to bicycle=yes - so my patch shouldn't change behavior here regarding tags. Or am I getting something wrong now? -- Gernot
Gernot Hillier <gernot@hillier.de> writes:
Hi there!
Greg Troxel schrieb:
-highway=path {add access = no; add bicycle = yes; add foot = yes} [0x16 road_class=0 road_speed=0 resolution 20] +highway=path & bicycle=designated {add access = no; add foot = yes} [0x16 road_class=0 road_speed=1 resolution 23] +highway=path {add access = no; add bicycle = yes; add foot = yes} [0x16 road_class=0 road_speed=0 resolution 23]
Don't you want a bicyle=yes on the second line, or is that added from a bicycle=designated line elsewhere?
No, I don't think this would help.
The "add" keyword means only adding the tag if it wasn't present before, right?
So before my change, an already existing bicycle=designated wasn't change to bicycle=yes - so my patch shouldn't change behavior here regarding tags.
Or am I getting something wrong now?
I don't really understand things yet - I would expect that a "highway=path bicycle=designated" way would end up in the Garmin receiver being coded as acceptable for bicycles. I can imagine bicycle=designated and foot=no, and not wanting to enable foot=yes.
participants (2)
-
Gernot Hillier -
Greg Troxel