[mkgmap-dev] How to track an error in OSM data ? (and style's behavior error)

Sun Jul 31 12:53:35 BST 2011

Am 31.07.2011 12:32, schrieb WanMil:

>> I also found an error in a style file for forest polygons. You have to
>> write the rules like this if you want the result expected :
>>
>> landuse=forest & wood=coniferous [0x54 resolution 18]
>> landuse=forest & wood=decideous [0x50 resolution 18]
>> landuse=forest & wood=mixed [0x55 resolution 18]
>> landuse=forest & wood !=* [0x50 resolution 18] /*this line is applied if
>> no data matches the ones above*/
>>
>> and not like that :
>>
>> landuse=forest & wood=coniferous [0x54 resolution 18]
>> landuse=forest & wood=decideous [0x50 resolution 18]
>> landuse=forest & wood=mixed [0x55 resolution 18]
>> landuse=forest [0x50 resolution 18]/*this line overrides the ones above*/

> As far as I know all rules after the first 
> matching line with a garmin id are skipped unless you add a continue 
> statement. So the default style should be correct.

Yes. mkgmap stops at the first matching rule.

Exeptions:

Action rules ( example : maxspeed=DE:urban {set maxspeed=50} )
and the continue-statement:

barrier=fence [0x34 resolution 24 continue]

Chris