Hi! How to make a restriction of access on the road if it contains a point with "barrier=bollard" or "barrier=gate"? I mean are the same as the turn restrictions with relations "type=restriction". -- View this message in context: http://gis.638310.n2.nabble.com/Routing-restriction-points-tp6449115p6449115... Sent from the Mkgmap Development mailing list archive at Nabble.com.
On Tue, Jun 07, 2011 at 04:28:28AM -0700, ValentinAK wrote:
Hi! How to make a restriction of access on the road if it contains a point with "barrier=bollard" or "barrier=gate"? I mean are the same as the turn restrictions with relations "type=restriction".
As far as I understand, --link-pois-to-ways does this. I have not tested if it actually works. I am not aware of a style rule that would allow you to propagate node attributes to way attributes. The "apply" action can only copy attributes from relations to relation members. Best regards, Marko
This restriction is not the property of ways. This is a property of point. But this is not POI! -- View this message in context: http://gis.638310.n2.nabble.com/Routing-restriction-points-tp6449115p6449705... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Am 07.06.2011 15:40, schrieb Marko Mäkelä:
How to make a restriction of access on the road if it contains a point with "barrier=bollard" or "barrier=gate"? I mean are the same as the turn restrictions with relations "type=restriction".
As far as I understand, --link-pois-to-ways does this. I have not tested if it actually works.
Yes, this works. It is triggered by the access tag, if this is missing you can add it in the stylefile. example: barrier=bollard {add access=yes; add motorcar=no} [0x7001 resolution 24] To stop cars from bollards, but allow bikes and foot. Chris
On 07/06/2011 13:28, ValentinAK wrote:
Hi! How to make a restriction of access on the road if it contains a point with "barrier=bollard" or "barrier=gate"? I mean are the same as the turn restrictions with relations "type=restriction". In my experience these barrier nodes are effectively ignored, leading to sometimes being routed into a dead-end street. I always break the way and insert a short section (with the barrier node in the middle) with access=no or whatever is appropriate to the traffic which CAN pass the barrier.
Wouldn't it be nice if we could distinguish between barriers which are 'always closed', ones which are 'always open' and ones which are 'user-openable'... Garmins are (AFAIK) not clever enough to say "stop at the gate and open it". Mkgmap could possibly benefit with an option to choose between assuming barriers can be routed through (e.g. gates which are chained open), and barriers which actually block your path (e.g. fixed bollards). The next point is of course how to tag that explicitly in OSM, but some kind of support in mkgmap might be quicker than getting the world to update the map. Colin
I'm talking about restrictions contained in routing parameters of some points. Not all the points but only some of which specifies the possibility of a turn or reversal. Usually this points located at the intersection of of ways. This is an example of routing parameters of the barrier point in the GPSMapEdit program: http://gis.638310.n2.nabble.com/file/n6450139/routing.png The same must be with maps made by the Mkgmap. Cutting the road and add to its part of "access=no" is not a good idea because at this moment the points with the tag "barrier=bollard" about 90.000! Redo all of them? And this method is unnecessary add 2 points with routing parameters - it may slow down route calculations. ----- http://maptourist.org/ -- View this message in context: http://gis.638310.n2.nabble.com/Routing-restriction-points-tp6449115p6450139... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (4)
-
Chris66 -
Colin Smale -
Marko Mäkelä -
ValentinAK