Hi Marco, > Mark, I'd like to help but I've no way to build mkgmap. Could you please send > me a compiled mkgmap.jar to test the patch?
Wilco. But why can't you build mkgmap? I believe it can even be done on Windows boxes so it can't be that difficult. > Please, don't give up in searching for the BUG. I'm reading the code and I > suspect the error is in the NET/NOD info calculations. In fact the issue > appears when the 2 collapsing nodes has >= 3 arcs. Nodes with >= 3 arcs are > "route nodes" (nodes were routing decision has to be taken) and a NOD record > is to be calculated for each one. All NOD records are connected each other > with pointers to build the routing network. If two connected routing nodes > with 3 arcs each collapses into one with 4 arcs, I guess that all pointers > structure shall be recalculated to take care of the missing routing node, and > the fact the new node has now 4 arcs instead of 3 implies the NOD record is > different and has to be updated. Of course my are just assumptions. Actually, I am not searching for the bug because it doesn't have to be our code that's causing the problem. It could be a bug in the garminware. > Do you know who wrote the parts of the code that calculate the routing > structures (src\uk\me\parabola\imgfmt\app\net\...) and how to contact them? > In some file I read Robert Vollmert, Steve Ratcliffe,... No, I don't know who wrote that stuff but, surely, Steve will know. Cheers, Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
