[mkgmap-dev] Norway not buildable with the no-trim option

Tue Jan 8 11:56:16 GMT 2013

Felix Hartmann-2 wrote
> with new splitter, no problems with the bay of biscay anymore. But I 
> don't really understand what that bug has to do with "not enough room in 
> osm file" problem - which is a problem about too few interaction between 
> mkgmap and splitter.... (integrated fallback by mkgmap calling splitter 
> and splitting the file into two parts would be best IMHO).

OK, I try to explain. The new split algo tries to fill each tile 
with at least max-nodes/3  nodes. For a coast like that of
Norway it is likely that you have a very large tile that covers
the baltic sea. If mkgmap is used with  --generate-sea in combination with
precomp-sea, mkgmap adds a lot of coastline data to that tile.
This results in the "There is not enough room ..." message.
No matter how small the max-nodes value is, splitter will always
generate this big tile if --no-trim is active. So, I've added the parm
--precomp-sea to splitter to allow it to count the coastline nodes as well.
Now, it generates smaller tiles, but some of them might contain nothing but
coastline data. The question is if that will cause the crash again.

Gerd


--
View this message in context: http://gis.19327.n5.nabble.com/Norway-not-buildable-with-the-no-trim-option-tp5741482p5743383.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.