Hi WanMil, WanMil wrote
Any idea?
Another (small) idea would be to improve the raster of the precompiled bounds. At the moment a bounds tile is 50000x50000 Garmin units big (BoundaryUtil.RASTER). I broadly remember that splitter uses a 2^n raster (?). Maybe it's beneficial to change the boundary raster to the splitter raster?
I think it is not needed to change the RASTER constant. Splitter calculates the tile size depending on the max-nodes parameter. It doesn't use fixed tile sizes. You can use --write-kml=xyz.kml to create a kml file which can be displayed in google earth. Gerd -- View this message in context: http://gis.638310.n2.nabble.com/Bug-in-LocationHook-tp7157897p7167197.html Sent from the Mkgmap Development mailing list archive at Nabble.com.