setting it to something however means it is set.
So the result of
& access!=*
will of course return a different result compared to the tag not
existing. Quite often in styles the nonexistance of access tags, or the
existence of "yes" is needed to be checked.
E.g.
highway=footway & bicycle=yes
On 09.09.2013 20:47, WanMil wrote:
>>
>>
>
> The goal of the branch is to give complete control to the style
> implementor. So we need the new tags mkgmap:access:bike,
> mkgmap:access:foot etc.
>
> As a style developer you can decide to use the new tags directly or
> you can still use the OSM a
I didn't use it yet - need to find enough time to adapt my style - but I
find the access handling a bit clumsy on the last step:
bicycle=*{ set mkgmap:access:bike='${bicycle}' }
carpool=*{ set mkgmap:access:carpool='${carpool}' }
foot=* { set mkgmap:access:foot='${foot}' }
hgv=*
Maybe it's easier for you if you know that only the value no is
evaluated for the mkgmap:access:* tags. So setting them to yes or
designated or whatever is the same like not setting the tag.
Good hint.
Shall I put this into the wiki?
http://wiki.openstreetmap.org/wiki/Mkgmap/help/Tag
> Maybe it's easier for you if you know that only the value no is
> evaluated for the mkgmap:access:* tags. So setting them to yes or
> designated or whatever is the same like not setting the tag.
> Good hint.
> Shall I put this into the wiki?
> http://wiki.openstreetmap.org/wiki/Mkgmap/help/Tags
>
> I didn't use it yet - need to find enough time to adapt my style - but I
> find the access handling a bit clumsy on the last step:
>
> bicycle=*{ set mkgmap:access:bike='${bicycle}' }
> carpool=*{ set mkgmap:access:carpool='${carpool}' }
> foot=* { set mkgmap:access:foot='${foot}' }
hi!
Former version was 2606. Map is compiled from scratch.
best regards
Michal
2013/9/8 Steve Ratcliffe
>
> Hi
>
> > After upgrading to the release 2679 i get such exception during map
> > compilation:
>
> Can I ask which version you were using before? (or if you don't know
> exactly, the ro
