Hi, okay, I think I understand now better. mkgmap r2889 writes all route restrictions so that they prohibit pedestrians and emergency vehicles. RouteRestriction contains this: HEADER = 0x004005; If I change that to 0x004605 (as the wiki suggests) routing is allowed for pedestrians and emergency. So, we can control whether restrictions apply to pedestrians and emergency. Now I wonder if the old behaviour was intended? I think no. Both emergency and pedestrians can ignore signs like "no left turn", can't they? Gerd GerdP wrote
Hi Steve,
I'd like to change the code for the --link-pois-to-ways option so that POI with access restrictions (e.g. barriers or gates) are converted to route restrictions instead of short way segments with limited access as this doesn't represent the real meaning of the POI.
My problem: Current implementation doesn't support route restrictions that apply to pedestrians or emergency. On the other hand I found this link: wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/NOD_Subfile_Format#Table_C
It claims that the exceptions for pedestrian and emergency is stored in the header bytes. On the other hand, it also claims that this header contains a number of ways, and I don't see that we write this.
I guess mkgmap writes another format of the table C. Do you think this can be changed without much work?
Gerd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Route-Restrictions-tp5790369p5790416.html Sent from the Mkgmap Development mailing list archive at Nabble.com.