[mkgmap-dev] Problems with sea in overview map

Fri May 21 10:33:13 BST 2021

Hi Ticker,

yes, I think it should be enough to replace the boundary nodes, the others are already unique.
It might even be a good idea to merge all sea (and if needed also land) in SeaGenerator.

I'm about to commit a big change which implements full merge and remove small holes before MapSplitter is called, but that is done again for each level.
I see nice improvements with complex sea.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Freitag, 21. Mai 2021 11:26
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problems with sea in overview map

Hi Gerd

When loading precomp sea tiles, shouldn't SeaGenerator should replace
all nodes on the edges of all the precomp tiles used with nodes from a
shared coordPool. Maybe it needs to replace even more to cover the cut
lines.

Ticker

On Thu, 2021-05-20 at 14:09 +0000, Gerd Petermann wrote:
> Hi Ticker,
>
> reg. Also thinking that shapeMerge might need to operate at
> highPrecision :
> ShapeMerger doesn't compare positions, it checks for identical
> Coords.
>
> For the overview map the ovm_* data is read and
> MapBuilder.prepShapesForMerge() is used to make equal Coord instances
> identical. This is not 100% safe, no matter what precision we use,
> when the original data has touching rings with equal, but different
> Coords the OverviewBuilder can see identical ones.
>
> Gerd

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