Hi Franco, okay. Please try also if you can reproduce the problem with only one osm input file that contains Schwabmünchen, either produced by splitter or e.g. JOSM.
Gerd franco_bez wrote > Hi Gerd, > > I will try to start testing tonight. > > As the style I usually use is developped by Bernd, not myself, and had > several changes since my first post, I might just try to use the mkgmap > default stlye with the modified line for tracks instead. > > Ciao, > Franco > > Am 08.04.2013 09:07, schrieb Gerd Petermann: >> Hi Franco, >> >> I still don't know what's wrong, and I can't reproduce the problem on >> my Oregon :-( >> You say that r2460 is working , but r2544 is not. I compared the >> sources of these two releases and found two major changes which might >> have an influence on the index. One came with r2468, the other with >> r2481. >> I've compiled five versions 2460,2467,2468,2480, and 2481 : >> |http://files.mkgmap.org.uk/download/100/mkmap_versions.zip| >> Please use these binaries and try to reproduce the problem. Let me >> know the highest version that still worked. >> Always use the same input files, esp. your style file. If you think >> that the problem is not related to the x-housenumber option, please >> disable that for all versions. >> >> Gerd > > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- View this message in context: http://gis.19327.n5.nabble.com/No-roads-near-target-bug-in-Schwabmunchen-tp5753364p5756225.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
