Hi Minko, sorry for the delay. The statement "setaccess no" sets the access tags with prefix mkgmap: to no, e.g. mkgmap:bicycle, mkgmap:taxi, mkgmap:car etc. I think that works okay. I guess you expected that it sets the similar values without the prefix? Or do you think that the finalize section should not override any value prefixed with mkgmap: ? Anyhow, I am not really happy with your solution. I have the feeling that these rules should be placed in inc/access, but it seems that one cannot override the road_class in the finalize section. @WanMil: Do you see a better solution? Gerd
Date: Wed, 22 Oct 2014 16:04:30 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Problematic routing on road_class=3 ferry routes for hikers
More improvements: It seems setaccess=no is not the correct command (?), so I changed it into setaccess no Then it turns out that in the finalize section mkgmap notice the tag bicycle=yes and converts it into mkgmap:bicycle=yes, so it somehow switches the bicycle access flag back off (means access allowed), what I dont understand because I use 'setaccess no'. This is either a bug or I don't understand the working of the finalize section.
Anyway, as workaround I have to delete also bicycle and motorcar tags in the last step (for simplicity, other vehicles like taxi, bus etc are ignored):
route=ferry & foot!=no {set foot_ferry=yes} route=ferry {set foot=no; add mkgmap:ferry=1} [0x1b road_class=3 road_speed=0 resolution 19 continue with_actions] route=ferry & foot_ferry=yes {setaccess no; set foot=yes; delete bicycle; delete motorcar} [0x1b road_class=0 road_speed=0 resolution 23] _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev