> Therefore I > thought it might rather be a splitting / merging problem, than an > originally broken coastline. I use --ignore-osm-bounds, could that > mangle things? I also lately experience routing failure over tile > boundaries, and trying with mkgmap 1243 my map failed to make last > night.
I distinctly recall that you should not use --ignore-osm-bounds if you want to route between tiles. Regarding the sea polygons, I get the same problem on the Cloudmade extract of Ontario, Canada, when it is split but compiled without --ignore-osm-bounds. So this parameter is most likely the cause of your routing problems, but not your sea polygon problems. Cheers. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
