
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.