On 16.02.2011 14:37, Marko Mäkelä wrote:

On Wed, Feb 16, 2011 at 11:31:26AM +0100, Minko wrote:

...

If I use the option --make-opposite-cycleways or --make-all-cycleways, an extra label is placed with "street (cycleway)". Is it possible to turn this label off or make it invisible in the style line file and how? I believe that you could imitate --make-opposite-cycleways in the style file, by using the continue or continue_with_actions action. Perhaps we should introduce a opposite_cycleways style as a substyle of the default style?

I think this option should be removed. It does far less than what one can do using continue / continue with_actions (note not continue_with_actions sic!) and does less than what one would expect to be done (think of all the possible variations to indicate cycling allowed against the opposite flow of traffic like bicycle:oneway=no; oneway:bicycle=no; whereas cycleway=opposite does not actually indicate that one may cycle against the flow of traffic, could be just on the wrong side - better would be bicycle:oneway=no/yes plus cycleway:right and cycleway:left or cycleway:both (which all again do not tell their direction of traffic).

On 16.02.2011 15:19, Minko wrote:

Can you give an example how this can be done in the style file:

A street with oneway=yes& cycleway=opposite

-If the navigation is set to cars, routing is only possible in one way -If navigation is set to bicycle, routing is possible in two ways

As far as I know this cannot be controlled in the style file. It is either oneway=yes or oneway=no

Is bicycle:oneway=no (or yes) an option I can use in the lines style? You introduce the rule

highway=* & oneway=yes & cycleway=opposite {set oneway=-1; set access=no; set bicycle=yes} [0x?? road_speed=? road_class=? continue] This rule of course has to be at the beginning. You do not need to care about foot=yes as for pedestrian Garmin disrespects the oneway atribute. Mind depending on the layout of your map - you may have to introduce this rule several times each with according highway=residential and so on. Everything else stays unchanged. You could also set to oneway=no... It has the advantage that one can pick lower priority for going against the general flow of traffic dependant on the highway type (or whatever else). Basically this is exactly what the option is doing, with the difference that you cannot influence road_class and road_speed )

Op 16-2-2011 15:46, Felix Hartmann schreef:

On 16.02.2011 15:19, Minko wrote:

...

Can you give an example how this can be done in the style file:

A street with oneway=yes& cycleway=opposite

-If the navigation is set to cars, routing is only possible in one way -If navigation is set to bicycle, routing is possible in two ways

As far as I know this cannot be controlled in the style file. It is either oneway=yes or oneway=no

Is bicycle:oneway=no (or yes) an option I can use in the lines style? You introduce the rule

highway=*& oneway=yes& cycleway=opposite {set oneway=-1; set access=no; set bicycle=yes} [0x?? road_speed=? road_class=? continue] This rule of course has to be at the beginning. You do not need to care about foot=yes as for pedestrian Garmin disrespects the oneway atribute.

Mind depending on the layout of your map - you may have to introduce this rule several times each with according highway=residential and so on. Everything else stays unchanged. You could also set to oneway=no... It has the advantage that one can pick lower priority for going against the general flow of traffic dependant on the highway type (or whatever else). Basically this is exactly what the option is doing, with the difference that you cannot influence road_class and road_speed )

Thank you, this is what I've been looking for... As soon as I have time I'll try and use it! J-----.

On 16.02.2011 21:50, Minko wrote:

Thanks Felix, But how about situations with highway=*& oneway=-1?

Does this work too?

highway=*& oneway=-1& cycleway=opposite {set oneway=yes; set access=no; set bicycle=yes}

Yes of course. That's what you need to do (assuming that cycleway=opposite really means that the way is against the flow of traffic and not only on the opposite side...)

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

Am 17.02.2011 00:01, schrieb Minko:

It's still a bit confusing to me. Does ?? in [0x?? road_speed=? road_class=? continue] mean that you can use wildcards?

Or is it just an example and you need to fill it in for every road type, like Felix already mentioned?

And I suppose you need to add cycleway=opposite_lane as well. And maybe bicycle:oneway=no or oneway:bicycle=no since some will use these tags instead of cycleway=opposite You have to use a routable Garmin-way-ID instead of ?? and for ? you have to insert a numeric value (as normal). If you need several pairs of these rules depends on your generel style. If you want to distinguish eg. a tertiary oneway from a track oneway you need for each highway a pair of rules.

Henning

I have tested this in the style file: highway=unclassified & oneway=yes & (cycleway=opposite | cycleway=opposite_lane) {set oneway=-1; set access=no; set bicycle=yes } [0x06 road_class=3 road_speed=5 resolution 22 continue ] highway=unclassified & oneway=-1 & opposite-cycleway!=yes & (cycleway=opposite | cycleway=opposite_lane) {set oneway=yes; 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] This is not working. Routing is messed up terribly, especially it goes wrong where several oneway streets with "cycleway=opposite" cross each other. Often oneway streets are routable in the opposite direction, but not in the "oneway" direction anymore. I tried "continue with_actions" instead of "continue" too but it doesnt seem to help. I tried it without the oneway=-1 rule too but it still didn't work. It would be great if someone can provide me with a style file where this should work, I'm willing to test it out on this area: http://www.openstreetmap.org/?lat=52.157498&lon=5.394098&zoom=18&layers=M Regards, Minko

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