[mkgmap-dev] Final call for merging the mergeroads branch

Sun Dec 22 14:06:23 GMT 2013

Hi Minko,

> Question about the Finalize section:
>
> Actions in the finalize section modify only the element for the current executed element type
> definition. The
> continue
> or
> continue with_actions
> statements continue to work with the
> element but without any action of the finalize section applied.

Correct.

>
>
> What about continue for some lines that needs to be processed in the polygon style, like highway=* & area=yes (pedestrian, service etc). Are the finalize actions not applied?

The finalize actions are applied only the current executed element type 
definition. So if a polygon style rule with an element type defintition 
matches the finalize actions of the polygon style are applied.

I'll try an example:
highway=pedestrian, area=yes, name=Shopping street

lines:
highway=pedestrian [0x16 road_class=0 road_speed=0 resolution 22 continue]
<finalize>
name=* { name '${name}' }

polygons:
highway=pedestrian & area=yes [0x17 resolution 22]
<finalize>
name=* { name 'Polygon ${name}' }

There will be two objects in the Garmin map:
1: line 0x16, name 'Shopping street'
2: polygon 0x17, name 'Polygon Shopping street'

>
> Please note that in the default style pedestrian areas are not routable:
>
> highway=pedestrian & area!=yes [0x16 road_class=0 road_speed=0 resolution 22]

Yes, seems so.

>
> Is this intended? Shouldn't we remove area!=yes from this rule?
> Better would be this:
> highway=pedestrian [0x16 road_class=0 road_speed=0 resolution 22 continue]
>
> But then it conflicts with "statements continue to work with the
> element but without any action of the finalize section applied"?

I don't understand why it conflict with the continue handling of the 
finalize sections.
But I think the way is handled the same in trunk and in branch so I it's 
not a problem of the mergeroads branch.

After merging we might change the style so that pedestrian areas are 
routable.
@Others: what's your opinion?

WanMil