Hi Ticker, that's an interesting idea. Did you try that? My results are even worse, but maybe I changed the wrong places. For sure the ovm* files are much larger. I guess there will also be problems with memory when you try to combine many tiles.
Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Montag, 24. Mai 2021 18:00 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problems with sea in overview map Hi Gerd This seems to be false when combining the ovm_, rather than when generating them! It suppresses RoundCoords but maybe shouldn't. Not sure why RoundCoords should ever be suppressed when res < 24? It doesn't suppress removeObsolete, which removes points in any straight line. I suppose the simpler way to view this is that unique points per element on the tile boundary should be kept; making the job of the overview combiner mergeShape possible. Ticker On Mon, 2021-05-24 at 15:35 +0000, Gerd Petermann wrote: > Hi Ticker, > > yes, it is. See usage of enableLineCleanFilters > > Gerd > > ________________________________________ > Von: mkgmap-dev <[email protected]> im Auftrag > von Ticker Berkin <[email protected]> > Gesendet: Montag, 24. Mai 2021 17:33 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] Problems with sea in overview map > > Hi Gerd > > Not quite related, but if merging the shapes from all ovm_ imgs, then > maybe some types of filtering should be turned off when the contents > for these is being generated; esp DP, and probably straigh-line > removal > in removeObsolete > > Ticker > > On Mon, 2021-05-24 at 15:21 +0000, Gerd Petermann wrote: > > Hi Ticker, > > > > sorry, I can't follow. The old code only preserved points on the > > boundary of the merged shape, but the outer ring can be far from > > rectangular. > > This way some important points on outer ring were not preserved. > > > > There's still a possible problem with large white area in sea which > > seems to depend on the order in which shapes are merged. Sill > > trying > > to understand what goes, but at least I can reproduce it... > > > > Gerd > > > > > > ________________________________________ > > Von: mkgmap-dev <[email protected]> im Auftrag > > von Ticker Berkin <[email protected]> > > Gesendet: Montag, 24. Mai 2021 17:11 > > An: Development list for mkgmap > > Betreff: Re: [mkgmap-dev] Problems with sea in overview map > > > > Hi Gerd > > > > Re. last commit: preserve all horizontal and vertical lines in > > shapes. > > > > Do the cut lines go right across the outer polygon or just in from > > one > > side to the hole? If all the way across, might this change inhibit > > the > > merging to one side of the hole, or, if divided for some other > > reason > > in the other direction, merging across the now unneeded cut line. > > > > Ticker > > > > _______________________________________________ > > 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 > _______________________________________________ > 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 _______________________________________________ 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
