Hello Dirk, flabot@googlemail.com wrote
- try to calculate reasonable value for max-areas based on available heap, number of tiles and file size
Cant we use the size of the *.img in gmapsupp for finetune the splitting areas ? Depending on the kind of style-sheat and the data splitting areas with the same size of nodes is not perfect.
Hmm, this is a completely different problem. The default value 255 for the max-areas parameter is typically too small, as a result, the program reads the input file many times, even if heap would allow e.g. 1024 areas. You describe an algorithm that uses the result of mkgmap processing to "optimize" the position or size of the tiles. Can you describe more detailed what splitter should do with this information? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r239-tp5736433p5736447.html Sent from the Mkgmap Development mailing list archive at Nabble.com.