[mkgmap-dev] Routing - Documentation and Best Practice

Sun Aug 28 11:44:18 BST 2011

this might be slightly off-topic, but still: why not avoid the whole 
problem altogether?

i use a non-routable base map containing everything you see on the 
screen, on top of that 2 transparent routable maps, one for car, one for 
bicycle, switched on/off according to the vehicle used.

this has at least 3 major advantages:

  * the whole access issue is handled by mkgmap - if you don't wanna 
ride a cycle along a motorway, don't render it in the 1st place

  * it let's you assign different road_speeds/road_classes for different 
vehicles - i want a good speed/class for primary highways if i drive a 
car, but on a cycle i'd prefer better class and speed for smaller roads

  * last but not least: the styles are a lot less complicated and easier 
to maintain

Am 27.08.2011 19:32, schrieb toc-rox:
> Further investigation has shown a significant difference (concerning routing)
> between MapSource (Windows, 6.16.3) and BaseCamp (Windows, OS X, 3.2.2).
> It seems that the access bits (e.g. access=no; bicycle=yes; ...) in BaseCamp
> are not working as expected.
>
> Could someone verify my observation?
>
> Thanks - Klaus
>
> --
> View this message in context: http://gis.638310.n2.nabble.com/Routing-Documentation-and-Best-Practice-tp6710634p6732637.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20110828/7122116d/attachment.html 