HI Gerd, I don't have a build that includes the PrecompSeaGenerator, but I would expect the impact to be the same as for in-line sea generation: an increase in execution time if /check is specified with a reduction if it is not specified.
I'm not quite clear what happens if you specify --precomp-sea, but don't specify --generate-sea. The help only says that --precomp-sea can be combined with --generate-sea but doesn't say what happens if you don't. (Does it switch on --generate-sea=multipolygon?) I think the order of the options in the documentation is not ideal either - I would think --generate-sea should come first, followed by --coastline-file and that followed by --precomp-sea. Happy to tweak this. Cheers, Mike -----Original Message----- From: Gerd Petermann [mailto:[email protected]] Sent: 07 February 2021 17:36 To: Development list for mkgmap <[email protected]> Subject: Re: [mkgmap-dev] Fix Sea Patch Hi Mike and Ticker, do you expect an impact on the PrecompSeaGenerator? Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Sonntag, 7. Februar 2021 18:16 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Fix Sea Patch Hi Mike / Gerd This patch seems fine to me. Ticker _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
