hi, list I tried preprocessing the china.osm(http://downloads.cloudmade.com/asia/china#downloads_breadcrumbs) with Mapnike render plugin. The plugin is set to render to zoom level 13(the maximum zoom level is also 13, greater values will generate larger zoom level with most of the tiles being missed.) It seems that monav uses a direct index scheme, the length of index file is always fixed based on the zoom level (16 * 4^zoom (byte)). For example, zoom level 13 will generate a 1GB index file, while the tile file could be much smaller. Is it possible for monav to switch to some space partitioning algorithm based solution(e.g. quard tree). Since the index file contains too many redundant data. NaviComputer(http://navicomputer.com/index.php) is able to pack and use osm tiles of any selected levels from any specified area, while the file size is changed based on the area size and zoom levels. It will be great if monav can also generate and use tiles of specified zoom levels rather than begin with zoom level 0.
--Regards, zsj -- View this message in context: http://gis.638310.n2.nabble.com/Routing-monav-Mapnike-render-generates-huge-and-fixed-sized-index-file-tp5537643p5537643.html Sent from the Routing mailing list archive at Nabble.com. _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
