logo separator

[mkgmap-dev] garmin directives in different blocks?

From Felix Hartmann extremecarver at googlemail.com on Fri Apr 16 08:34:38 BST 2010


On 16.04.2010 06:53, Valentijn Sessink wrote:
> Hello list,
>
> As far as I understand, if I wanted to make, let's say, a hypothetical
> interstate cycleway from any OSM motorway with the mkgmap, I'd have a
> line in my style like:
>
> highway=motorway  {add access = no; add bicycle = yes; add foot = yes}
> [0x16 road_class=4 road_speed=1 resolution 14]
>
> (Or something alike). Now I'm wondering, shouldn't this be something like:
>
> highway=motorway  [0x16 road_class=4 road_speed=1 access=XYZ resolution 14]
>
> i.e. have the Garmin controls really in the Garmin action block and not
> in the mkgmap-block? Because the stuff between the curly brackets has
> effects on the following Garmin actions, i.e. if I wanted to make both a
> cycleway and a motorway, as far as I understand, I can't do:
>
> highway=motorway  {add bicycle = no; add foot = no} [0x16 road_class=4
> road_speed=1 resolution 14 continue]
> highway=motorway  {add access = no; add bicycle = yes; add foot = yes}
> [0x16 road_class=4 road_speed=1 resolution 14]
>
> ... because now my cycleway will be inaccessible to bicycles. And if I
> use "set" instead of "add", I can't know if foot should be yes or no, as
> the motorway added it.
>
> Now I'm not completely sure my remarks are true, as I've only started
> building styles, but maybe someone could comment? How should I make the
> above cycleway plus motorway?
>
>    
Well you have continue vs continue_with_actions, I don't see where your 
problem is. If you use continue, nothing of the action block is carried 
forward to other rules. That's what continue_with_actions is used for 
and what you mistake with continue.
> Best regards,
>
> Valentijn
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>    



More information about the mkgmap-dev mailing list