[mkgmap-dev] Problem with !(mkgmap:unpaved=1), found a line in 'line' that DOES NOT cause compile Error

Wed Feb 10 20:40:39 GMT 2016

Hi Greg

> I found this line that uses very similar !(unpaved) type command but
> does NOT CAUSE an error on mkgmap compile.
>
> highway=tertiary_link & !(mkgmap:unpaved=1) & bridge!=yes [0x08
> road_class=1 road_speed=1 resolution 20 continue]
>
> but I do have a complie error with :
>
> (highway=residential | highway=living_street | highway=minor |
> highway=unclassified) & !(mkgmap:unpaved=1) & bridge!=yes [0x06
> road_class=0 road_speed=2 resolution 22 continue]

Yes, you have found a bug.  I will try to fix it.

As a workaround you can add a highway=*
This doesn't change the result but it does allow it to compile
with the current version.

(highway=residential | highway=living_street | highway=minor | 
highway=unclassified)
& highway=*
& !(mkgmap:unpaved=1)
& bridge!=yes
        [0x06 road_class=0 road_speed=2 resolution 22 continue]

Thanks for reporting this problem.

..Steve