
28 Aug
2011
28 Aug
'11
8:12 a.m.
Sounds terrible - devaluates *all* OSM garmin maps. Next week I will do further test on my Dakota-20 with Firm 4.30. Klaus PS: My workaround is to use the "toll and ferry" bits (toll for footways and ferry for cycleways). Yes I agree, it's a dirty workaround. And I hope that someone finds the reason for the new routing behavior. -- View this message in context: http://gis.638310.n2.nabble.com/Routing-Documentation-and-Best-Practice-tp67... Sent from the Mkgmap Development mailing list archive at Nabble.com.