Hi Felix, it seems that we write invalid or wrong turn restriction in the branch. I can't say much more until now, but maybe a restriction is simply used at the wrong crossing. This can cause all kinds weird results. I am also not sure if this branch works as well with styles like yours which creates multiple routable ways for one street, as this is not used in the Garmin maps that I know. Gerd Felix Hartmann-2 wrote
I have generated a map using NOD127 branch - for me the routing results are about the same, if not slightly worse. Using shorter distance option, there seems to be a bit higher focus on using fast roads. Also there are more turns than on trunk in the routes - and more often little detours to get on a "better" road.
But well, my styles are anything but standard.
Else I couldn't notice anything. Just like using trunk - Mapsource produced some crashes - this didn't hapen for me using mkgmap as of mid December (didn't update since then till now). It's not crashing Mapsource fully, but Error Code 3 and go again... I cannot find out any reason for it however (happens about 1 in 10 long distance routes. If I change the split or something in the style, then it will happen somewhere else). _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/new-branch-NOD127-tp5798806p5799018.html Sent from the Mkgmap Development mailing list archive at Nabble.com.