
In the default style the access for a gate has this rule: barrier=gate { add mkgmap:bicycle=yes; add mkgmap:foot=yes; addaccess no; set mkgmap:road-speed=0; } In osm a gate can have this rule: foot=yes access=no To me it looks like mkgmap is giving bicycles by default access through this gate. Or is the rule addaccess no blocking this?

Hi Minko, these rules will match before: barrier=* & foot=* { set mkgmap:foot='${foot|subst:private=>no}' } barrier=* & access=* { addaccess '${access|subst:private=>no}' } If I got that right, the rule below should not allow bicycle. It's difficult to verify that in the map as we create a route restriction for this when --link-pois-to-ways is active. Do you have an example where this doesn't work? Gerd ligfietser wrote
In the default style the access for a gate has this rule:
barrier=gate { add mkgmap:bicycle=yes; add mkgmap:foot=yes; addaccess no; set mkgmap:road-speed=0; }
In osm a gate can have this rule: foot=yes access=no
To me it looks like mkgmap is giving bicycles by default access through this gate. Or is the rule addaccess no blocking this?
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/barrier-access-tp5801950p5801964.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Gerd For instance this node you can pass with bicycle http://www.openstreetmap.org/node/1258837342#map=17/52.05858/5.36603 But you can find more with http://overpass-turbo.eu/s/2VT What happens if you dont specify any rules after barrier=gate, given that link-pois-to-ways is active? Will it look at the tags that are specified on OSM and use the route restrictions accordingly that are hardcoded, or will it ignore those barriers in routing? Do I have to set motorcar=yes for my cycle map after barrier=bollard (because I dont use car navigation) if I want to use link-pois-to-ways?
Hi Minko,
these rules will match before: barrier=* & foot=* { set mkgmap:foot='${foot|subst:private=>no}' } barrier=* & access=* { addaccess '${access|subst:private=>no}' }
If I got that right, the rule below should not allow bicycle. It's difficult to verify that in the map as we create a route restriction for this when --link-pois-to-ways is active. Do you have an example where this doesn't work?
Gerd

Hi Minko,
For instance this node you can pass with bicycle http://www.openstreetmap.org/node/1258837342#map=17/52.05858/5.36603
I can't reproduce that in MapSource with r3160 and default style. I am always routed to the next junctions when using bicycle mode. In pedestrian mode I am routed through the barrier.
What happens if you dont specify any rules after barrier=gate, given that link-pois-to-ways is active? Will it look at the tags that are specified on OSM and use the route restrictions accordingly that are hardcoded, or will it ignore those barriers in routing? Do I have to set motorcar=yes for my cycle map after barrier=bollard (because I dont use car navigation) if I want to use link-pois-to-ways?
Well, for the link-pois-to-ways option mkgmap evaluates the access tags beginning with mkgmap: and the mkgmap:road-class and mkgmap:road-speed tags (including the min and max versions). If it finds an access tag, it checks if the POI is more restrictive than the way. If yes, a routing restriction is created. If it finds a tag like mkgmap:road-class or mkgmap:road-speed, it will use the corresponding values for a part of the way near the POI. OK? Gerd
Hi Minko,
these rules will match before: barrier=* & foot=* { set mkgmap:foot='${foot|subst:private=>no}' } barrier=* & access=* { addaccess '${access|subst:private=>no}' }
If I got that right, the rule below should not allow bicycle. It's difficult to verify that in the map as we create a route restriction for this when --link-pois-to-ways is active. Do you have an example where this doesn't work?
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd,
I can't reproduce that in MapSource with r3160 and default style. I am always routed to the next junctions when using bicycle mode. In pedestrian mode I am routed through the barrier.
I see, I tested it with Lambertus OSM generic, mkgmap-r3116. Now with r3160 it is working as expected, bicycles dont pass the gate, excellent.
Well, for the link-pois-to-ways option mkgmap evaluates the access tags beginning with mkgmap: and the mkgmap:road-class and mkgmap:road-speed tags (including the min and max versions). If it finds an access tag, it checks if the POI is more restrictive than the way. If yes, a routing restriction is created. If it finds a tag like mkgmap:road-class or mkgmap:road-speed, it will use the corresponding values for a part of the way near the POI.
OK?
I tried it now with my OFM styles and this works too, so I think I got it :)
participants (3)
-
Gerd Petermann
-
GerdP
-
Minko