Hi all, I am working on a better split algorithm. Now I wonder why the split algorithm in r202 makes sure that tiles are aligned in a special way. A comment in main says: // The maximum resolution of the map to be produced by mkgmap. This is a value in the range // 0-24. Higher numbers mean higher detail. The resolution determines how the tiles must // be aligned. Eg a resolution of 13 means the tiles need to have their edges aligned to // multiples of 2 ^ (24 - 13) = 2048 map units, and their widths and heights must be a multiple // of 2 * 2 ^ (24 - 13) = 4096 units. The tile widths and height multiples are double the tile // alignment *because the center point of the tile is stored, *and that must be aligned the // same as the tile edges are. private int resolution; I think this is no longer true. Would it be okay to split tiles to single alignment (e.g. 2048 for resolution 13) or does something in mkgmap rely on these doubled values? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Question-regarding-alignment-of-tiles-in-spli... Sent from the Mkgmap Development mailing list archive at Nabble.com.