Hi, I have a question to the section in the doc of the new style system: --- Access restrictions of roads are now defined by setting special mkgmap:* access tags (mkgmap:car, mkgmap:foot, mkgmap:bicycle, mkgmap:truck, mkgmap:bus, mkgmap:taxi, mkgmap:emergency, mkgmap:delivery). Roads are blocked for a specific vehicle type if the mkgmap:<type> is set to the value no. The new addaccess and setaccess actions help to assign all values at once. --- Are other values than "no" being recognized? What about "private" and "destination"? Greetings Chris
Hi Chris, I think the idea of the change was that the java code should not interpret the meaning of osm tags like private. So, the style author has to decide what that means to him and set the mkgmap:xxx values accordingly. Gerd
To: mkgmap-dev@lists.mkgmap.org.uk From: chris66nrw@gmx.de Date: Sun, 19 Jan 2014 11:13:31 +0100 Subject: [mkgmap-dev] Access flag question
Hi,
I have a question to the section in the doc of the new style system:
--- Access restrictions of roads are now defined by setting special mkgmap:* access tags (mkgmap:car, mkgmap:foot, mkgmap:bicycle, mkgmap:truck, mkgmap:bus, mkgmap:taxi, mkgmap:emergency, mkgmap:delivery). Roads are blocked for a specific vehicle type if the mkgmap:<type> is set to the value no. The new addaccess and setaccess actions help to assign all values at once. ---
Are other values than "no" being recognized?
What about "private" and "destination"?
Greetings Chris
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 19.01.2014 11:18, schrieb Gerd Petermann:
I think the idea of the change was that the java code should not interpret the meaning of osm tags like private. So, the style author has to decide what that means to him and set the mkgmap:xxx values accordingly.
So, "destination" has to be mapped to "no"? But in this case a footway would (in the img file) have the same flags as a destination road. (car=no) Just want to make sure that this case: <http://up.picr.de/17095866ev.jpg> is handeled correctly.
Are other values than "no" being recognized?
What about "private" and "destination"?
Chris
Hi Chris, in styles\default\inc\compat_lines I see this rule: access=destination { set mkgmap:throughroute=no } If you don't use the compat_lines file, you should add something similar to your style file. Gerd
To: mkgmap-dev@lists.mkgmap.org.uk From: chris66nrw@gmx.de Date: Sun, 19 Jan 2014 11:50:31 +0100 Subject: Re: [mkgmap-dev] Access flag question
Am 19.01.2014 11:18, schrieb Gerd Petermann:
I think the idea of the change was that the java code should not interpret the meaning of osm tags like private. So, the style author has to decide what that means to him and set the mkgmap:xxx values accordingly.
So, "destination" has to be mapped to "no"?
But in this case a footway would (in the img file) have the same flags as a destination road. (car=no)
Just want to make sure that this case:
<http://up.picr.de/17095866ev.jpg>
is handeled correctly.
Are other values than "no" being recognized?
What about "private" and "destination"?
Chris
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 19.01.2014 11:54, schrieb Gerd Petermann:
in styles\default\inc\compat_lines I see this rule: access=destination { set mkgmap:throughroute=no }
If you don't use the compat_lines file, you should add something similar to your style file.
Thank's, this is what I was looking for. Chris
Hi Chris, as Gerd already explained, the new style system features give you the whole control over setting the access flags. For the access tags (mkgmap:car, mkgmap:foot etc.) only the value no is recognized. To use other value you can map these values: bicycle=no | bicycle=private | ... { add mkgmap:bicycle=no } or bicycle=* { add mkgmap:bicycle='${bicycle|subst:private=>no}' } On a first glimpse this sounds complicate because the style developer needs to care about all values. But this is the only way how style devs can have *full* control over the access handling. Please also have a look at the inc/access file of the default style to get an impression how the new system works. WanMil
Hi,
I have a question to the section in the doc of the new style system:
--- Access restrictions of roads are now defined by setting special mkgmap:* access tags (mkgmap:car, mkgmap:foot, mkgmap:bicycle, mkgmap:truck, mkgmap:bus, mkgmap:taxi, mkgmap:emergency, mkgmap:delivery). Roads are blocked for a specific vehicle type if the mkgmap:<type> is set to the value no. The new addaccess and setaccess actions help to assign all values at once. ---
Are other values than "no" being recognized?
What about "private" and "destination"?
Greetings Chris
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
chris66 -
Gerd Petermann -
WanMil