Hi Steve,
I think I found a very old bug in mkgmap, it seems to exist since at least
r2210.
I found it while testing a patch for r2914 and found it in all older versions
that I tried.
Attached are two test files and a gdb for MapSource.
The command that I use:
java -jar d:\mkgmap\dist\mkgmap_r2
Hi,
I have commited the new (undocumented) option --x-no-mergeroads to
disable merging of roads. I think this is useful for chasing problems.
WanMil
Hi Steve,
I think I found a very old bug in mkgmap, it seems to exist since at
least r2210.
I found it while testing a patch for r2914 and fou
Hi all,
really confusing...
The strange bug disappears in MapSource (6.16.3) when I (re-)activate option
"Try to avoid.."
"U-turns"
In Basecamp (4.25) , the bug appears as well when I deactivate "Feature type
avoidance"
"U-Turns".
Regarding the order of the ways in the OSM file:
It seems that th
Hi,
> I have no idea how to find the "right" order in a network.
> In NOD3, we sort the nodes "lexicographically by longitude, then latitude".
> Maybe we should do the same for NOD1?
Tried that. It fixes the problems in my test case, but creates similar problems
in other cases, so sorting see
Hi Gerd,
Nice simple test case. I can reproduce on a similar version of mapsource
that you used, but not on an older version.
I hope you can reproduce the problem and find out what goes wrong...
Interestingly if set to shortest time and avoid u-turns, then it goes
straight down w1, w2 and th
Hi Steve,
> Nice simple test case. I can reproduce on a similar version of mapsource
> that you used, but not on an older version.
>
> > I hope you can reproduce the problem and find out what goes wrong...
>
> Interestingly if set to shortest time and avoid u-turns, then it goes
> straight down w
