interesting, I've just posted a possible explanation for this.
From: anorcarlos@hotmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Wed, 20 May 2015 10:38:06 -0300
Subject: Re: [mkgmap-dev] [mkgmap-svn] Commit: r3573: admin_centre-v1.patch: avoid to create duplicate POI
Hi Gerd
I see you have more case doubling the POI in admin_level 10 when have included place in the relationship. This makes 2 POI
_______________________________________________________________________________________________________
Anor C. A. de Souza Concórdia SC
> From: svn@mkgmap.org.uk
> To: mkgmap-svn@lists.mkgmap.org.uk
> Date: Sun, 10 May 2015 06:30:59 +0100
> Subject: [mkgmap-svn] Commit: r3573: admin_centre-v1.patch: avoid to create duplicate POI
>
>
> Version mkgmap-r3573 was committed by gerd on Sun, 10 May 2015
>
> admin_centre-v1.patch: avoid to create duplicate POI
>
> It implements the following:
> When POIGeneratorHook creates a POI for a type=boundary relation
> with boundary=administrative it searches for a role=admin_centre member
> in that relation.
> If one is found, the generated POI will use the coordinates of this member.
>
> I see no easy way to compare the tags of the existing
> node with those of the generated POI, so
> as a second step, StyledConverter detects when a POI
> with the same type and name (or empty name) is created at the
> same Garmin coordinates (after style processing)
> If that is true, the latter one is ignored and an info message is logged.
>
> Maybe for certain types this should be changed to check for a radius
> rather than equality, but that would require complex configuration.
> _______________________________________________
> mkgmap-svn mailing list
> To unsubscribe send an mail to mkgmap-svn-leave@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-svn
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev