[mkgmap-dev] splitter: option for maximum tile area?

Thu Nov 1 11:02:34 GMT 2018

Hi Bernhard,

my understanding is that you should never see broken precompiled sea data, because the data source is not directly OSM
but http://openstreetmapdata.com/data/land-polygons where Jochen Topf invests time to check that the data is OK before updating it.
So, sea.zip might not be up to date but should always be OK.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Bernhard Hiller <bhil at gmx.de>
Gesendet: Donnerstag, 1. November 2018 11:23
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?

Hi Gerd,
thanks a lot for your many hints.
The file contains contour lines with ele=0, but I do not know how many.
Anyway, the style ignores contour lines at an elevation of 0.
Currently, I do not use the --precomp-sea option, but
"--generate-sea=multipolygon,extend-sea-sectors,floodblocker". Are the
precompiled coast line files OK again (I remember that they were broken
just recently)?
Changing the source code of splitter is not an option for me: I have no
Java IDE installed on my machine.
I'll try now with a severely reduced max-nodes value.
Kind regards,
Bernhard

Am 01.11.2018 um 09:32 schrieb Gerd Petermann:
> Hi Bernhard,
>
> I tried to reproduce the memory problems with tile 47120005. I don't think that the sea itself is a problem here, at least not when you use the --precomp-sea option. It took only 15 secs to process that tile with asia data from August with the default style and typical options for routing etc.
> My input file didn't contain SRTM data so I assume this is the reason. Maybe you have many contour lines with ele=in your data?
>
> Gerd
>
> ________________________________________
> Von: Gerd Petermann <gpetermann_muenchen at hotmail.com>
> Gesendet: Mittwoch, 31. Oktober 2018 22:49
> An: Gerd Petermann; Development list for mkgmap
> Betreff: AW: [mkgmap-dev] splitter: option for maximum tile area?
>
> Hi Bernhard,
>
> looked again at the splitter command in your last post. You also use a rather high max-nodes value.
> Such a high value means that you get rather large tiles and that mkgmap needs more memory for each tile
> compared to the default 1400000. Many users use a value near 1200000.
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen at hotmail.com>
> Gesendet: Mittwoch, 31. Oktober 2018 22:20
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] splitter: option for maximum tile area?
>
> Hi Bernhard,
> there is no option for this. Do you use option --precomp-sea in splitter? Maybe you use --no-trim ?
> If that doesn't help you can try to change the values for
> private static final int MAX_LAT_DEGREES =5;
> private static final int MAX_LON_DEGREES =0;
> in SplittableDensityArea.java and compile your own version of splitter.
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Bernhard Hiller <bhil at gmx.de>
> Gesendet: Mittwoch, 31. Oktober 2018 22:03
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: [mkgmap-dev] splitter: option for maximum tile area?
>
> Hi all,
> currently a Java OutOfMemory exception prevents me from creating a map.
> I already use option --max-jobs=(the machine has 4 physical cores) and
> -Xmx5G (of 8 GB installed). Beyond OSM data, the map contains DEM and
> elevation contour lines.
>   From the tiles finished and those with a new timestamp but about 0
> bytes length, I can see that mkgmap was rendering tiles 47120005,
> 47120006, 47120007 at the time of crash.
> Tile 47120005 is extremely large by physical area - some 6° x 5.5° (see
> attached file), covering a lot of the south chinese sea, i.e. there are
> not many actual data in that area.
> I guess that the problem arises with that tile. I remember some case in
> the past where a single tile covering such a large area of mainly sea
> caused mkgmap to take an enormous amount of time for rendering - also
> here, mkgmap already spent about 1 hour before crashing.
> So I'd like to ask: is there some possibility for limiting the area of a
> tile among the splitter options?
> Kind regards,
> Bernhard
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev