logo separator

[mkgmap-dev] Problems with generate-sea

From aighes osm at aighes.de on Thu Feb 16 11:29:01 GMT 2012

Am 15.02.2012 23:05, schrieb RheinSkipper:
>>>> to avoid these holes, you should use --no-trim if you split your
>>>> europe-file with splitter.jar.
>>>>  From my own experience: you should not use --no-trim for sea tiles.
>>> Reason: since there are only very few nodes in the sea, the tiles can
>>> become very big and mkgmap will fail to generate a img from it.
>> Maybe it  could happen, if there is very much sea in a tile. This is my
> largest
>> sea-tile: 2772992,-1259520 to 3336192,71680 (Garmin-units) and it works
>> without problems. Maybe it depends on memory.
>> So there are two solutions: generate it with --no-trim and manually tweak
> in
>> area.list some tiles or tweak many sea-tiles with holes. I would prefer
> the
>> first one ;-)
>> Henning
> Thank you for your help.
> With the --no-trim option there are no holes in the black sea or in the
> Baltic anymore. But I have still some holes in the Mediterranean and in the
> Atlantic.
> There are still about 20.000 lines of severe errors resulting from sea
> generation similar to this:
My guess is, that these errors are caused by using europe.osm.pbf. Your 
map will be rectangular but input-data is smaler and coastlines wont be 
complete. Solutions would be a global coastline-file or using 
planet.osm.pbf and cut a rectangular out of it.


More information about the mkgmap-dev mailing list