<div dir="ltr">compilation time includes splitting, and some other stuff. Loads of countries (9:34 / 9:21 (sorry dumb error 9:19) for all european single countries and a few continents (but not Europe continent) in hours.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 11 Jun 2021 at 11:08, Felix Hartmann <<a href="mailto:extremecarver@gmail.com">extremecarver@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr">I just compiled the australia-oceania map with that option, and I think I must be missing something. It got substantially worse (it is identical until the overview map kicks in) - then I get some huge squares of sea missing. Compile time for all maps until that point before<br>Compilation time is not up a lot:<div>0:12 - 9:46 = 9:34</div><div>one week before (except older mapdata no changes in compilation procedure and older mkgmap) 20:17 - 5:38 = 9:19</div><div><br></div><div>Anything I could be missing? I use the newest low-res branch build and added --improve-overview to the compilation process.</div><div><br></div><div>in my polygons file I have: </div><div>natural=sea { add mkgmap:skipSizeFilter=true; set mkgmap:drawLevel=2 } [0x10f1d resolution 10]</div><div> </div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 11 Jun 2021 at 07:12, Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I hoped for some positive feedback on this but got none so far. Did I miss something important?<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>><br>
Gesendet: Montag, 7. Juni 2021 21:05<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] Proof of concept for better sea in overview map<br>
<br>
Hi Felix,<br>
<br>
the map contained was without routing or index, so for a normal map the difference should be even smaller.<br>
There is no need to change sea.zip. You just have to use --improve-overview for now.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Felix Hartmann <<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a>><br>
Gesendet: Montag, 7. Juni 2021 21:02<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] Proof of concept for better sea in overview map<br>
<br>
I guess that is a time for a full Norway map based on default style - so that is quite okay. Not a sea only Norway map... Well I hope that Thorsten Kukuk can adapt his sea files in the near future then...<br>
<br>
On Mon, 7 Jun 2021 at 19:37, Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a><mailto:<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>>> wrote:<br>
OK, I think found a good solution. Speed is quite OK, I see 9 min 48 secs for map of norway and instead of 8 min 44 secs with r4756, and I consider Norway to be a worst case.<br>
<br>
See <a href="https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4761" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4761</a> for the details.<br>
<br>
Gerd<br>
<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>>> im Auftrag von Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a><mailto:<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>>><br>
Gesendet: Montag, 7. Juni 2021 12:11<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] Proof of concept for better sea in overview map<br>
<br>
With the provided patch the speed is very poor for areas like Norway, probably twice the time.<br>
It is much slower because it does the complex multipolygon cutting for each level in the overview map. Probably too slow for complex coastal areas.<br>
This time will be the same for precomp-sea unless we can store sea polygons for each resolution.<br>
<br>
Performance will be no problem if I find a way to use Douglas-Peucker or similar before cutting. That was my original idea but DP produces self intersecting polygons and the MultipolygonCutter cannot cope with that.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>>> im Auftrag von Felix Hartmann <<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a><mailto:<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a>>><br>
Gesendet: Montag, 7. Juni 2021 11:55<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] Proof of concept for better sea in overview map<br>
<br>
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).<br>
<br>
On Mon, 7 Jun 2021 at 12:26, Ticker Berkin <<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a><mailto:<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a>><mailto:<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a><mailto:<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a>>>> wrote:<br>
Hi Gerd<br>
<br>
This is going to take some studying to work out the implications. Can't<br>
do much for the next few days however, but will look carefully at the<br>
end of the week.<br>
<br>
Ticker<br>
<br>
On Sun, 2021-06-06 at 14:02 +0000, Gerd Petermann wrote:<br>
> Hi,<br>
><br>
> the attached patch improves the overview map, but so far only when<br>
> precomp-sea is NOT used.<br>
> I tested it with --generate-sea=multipolygon,floodblocker so that<br>
> mkgmap really has a multipolygon with the natual=sea data.<br>
><br>
> For each level in the overview map it uses the original multipolygon<br>
> data to compute the rings which will might visible at the given<br>
> resolution. This requires more time compared to the current code but<br>
> the result is much better and some fine tuning is possible.<br>
><br>
> To be able to use this also with --precomp-sea we need some changes<br>
> in the code which generates sea.zip so that one multipolygon relation<br>
> for each tile is stored.<br>
><br>
> I've uploaded the results here:<br>
> <a href="https://files.mkgmap.org.uk/download/511/compare.7z" rel="noreferrer" target="_blank">https://files.mkgmap.org.uk/download/511/compare.7z</a><br>
> What do you think?<br>
><br>
> Gerd<br>
><br>
><br>
> _______________________________________________<br>
> mkgmap-dev mailing list<br>
> <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>>><br>
> <a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>>><br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
<br>
<br>
--<br>
Felix Hartman - Openmtbmap.org & VeloMap.org<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
<br>
<br>
--<br>
Felix Hartman - Openmtbmap.org & VeloMap.org<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Felix Hartman - Openmtbmap.org & VeloMap.org<br></div><br></div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Felix Hartman - Openmtbmap.org & VeloMap.org<br></div><br></div></div></div></div></div></div>