Is it only much slower because of not using precomp sea? Or will it be much slower in general? And what is much slower for say Europe continent map? If a modern 4core/8thread processor needs 30 minutes more I would prefer the old way knowing it is worse (if the time difference is negligible with precomp-sea then that would be great).
On Mon, 7 Jun 2021 at 12:26, Ticker Berkin <[email protected]> wrote: > Hi Gerd > > This is going to take some studying to work out the implications. Can't > do much for the next few days however, but will look carefully at the > end of the week. > > Ticker > > On Sun, 2021-06-06 at 14:02 +0000, Gerd Petermann wrote: > > Hi, > > > > the attached patch improves the overview map, but so far only when > > precomp-sea is NOT used. > > I tested it with --generate-sea=multipolygon,floodblocker so that > > mkgmap really has a multipolygon with the natual=sea data. > > > > For each level in the overview map it uses the original multipolygon > > data to compute the rings which will might visible at the given > > resolution. This requires more time compared to the current code but > > the result is much better and some fine tuning is possible. > > > > To be able to use this also with --precomp-sea we need some changes > > in the code which generates sea.zip so that one multipolygon relation > > for each tile is stored. > > > > I've uploaded the results here: > > https://files.mkgmap.org.uk/download/511/compare.7z > > What do you think? > > > > Gerd > > > > > > _______________________________________________ > > mkgmap-dev mailing list > > [email protected] > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > [email protected] > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -- Felix Hartman - Openmtbmap.org & VeloMap.org
_______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
