> Do you still consider this idea?
>
> I have experimenting a bit with MAX_DIVISION_SIZE in mkgmap. I have
> observed increase in file size, when using small value, but no increase
> in processing speed. I think this discussion gives some explanations. As
> I understand, mkgmap doesn't split map objects to fit subdivisions. So
> there is no gain from using smaller subdivisions, because there is no
> reduction in processed objects size.

Tried the same with the same result some time ago.

>
> I would expect that proper truncating objects to subdivisions could be
> another big improvement for mkgmap. Please, don't abandon this idea.
I agree, but it requires a redesign of the MapSplit algo, which is complex.
I don't want to start complex changes before autumn, but if anybody else
wants to start, that would be great.

Gerd