[mkgmap-dev] routing on new devices
From Minko ligfietser at online.nl on Mon Nov 21 18:30:54 GMT 2011
In Basecamp, I tested the routing on one highway=unclassified and added extra tags in my style file. Here are some test results: highway=unclassified { set motorcar=no; set motorcycle=no } or { set motorcar=no } or { set motorcycle=no } or { set access=no } - carpool avoidance NOT selected: Road routable for cars, bicycle, motorcycle, foot + carpool avoidance selected: Road NOT routable for cars, bicycle, motorcycle; routable for foot { set mkgmap:carpool=1 } or { set motorcar=no; set mkgmap:carpool=1 } - carpool avoidance NOT selected: Road not routable for cars! Road routable for bicycle, motorcycle, foot + carpool avoidance selected: Road not routable for cars, bicycle, motorcycle; routable for foot {set motorcar=destination } / {set motorcycle=destination } / {set access=destination } Both options are routable for all vehicles EXCEPT cars (not routable); same behaviour as in Mapsource NB motorcycle = destination doesnt block motorcycles! { set access=no; set motorcar=yes } both carpool options are routable for all vehicles { set bicycle=no } both options are routable for all vehicles {set bicycle=destination } both options are routable for all vehicles { set carpool=yes } both options are routable for all vehicles {set motor_vehicle=destination } both options are routable for all vehicles Conclusion - some access tags only work for all vehicles if carpool avoidance is used - mkgmap:carpool=1 can block the road for cars only - motorcar=destination/acces=destination can block the road for cars, for other vehicles carpool option must be used. Question: are those observations caused by parameters in the routing that is hardcoded by mkgmap?
- Previous message: [mkgmap-dev] routing on new devices
- Next message: [mkgmap-dev] routing on new devices
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list