Hi Thorsten,

good points. When the tags like population are different the style may produce
different POI (different type, same label), so my solution
would not help in all cases.
I also see the problem that we can
have duplicates which are really different, e.g. two small hamlets
with the same name (like Holzhausen which appears often in Germany).

So, maybe a less general approach:
Treat type=boundary relations special and detect the case
that a node member with role=admin_centre is present.
If that is the case, don't generate a POI.
I fear that will also cause trouble in some cases,
e.g. when the node with role=admin_centre doesn't have
the wanted tags :-(

Gerd

> Date: Mon, 4 May 2015 08:46:15 +0200
> From: kukuk@suse.de
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Fw: Help
>
> On Mon, May 04, Gerd Petermann wrote:
>
> > Hi Thorsten,
> >
> > thanks for the feedback. What do you think about my proposed
> > solution?
>
> I like the idea. But I'm currently still thinking, if this really
> works.
> For something like "place=city", the place tag and the name are the
> most important thing mostly used. But what about population? What
> to do if only one of the "two" POI has full informations?
>
> Even more complicated would be something like amenity=restaurant, if
> somebody adds a POI and adds all tags to the building, too (I think
> this is bad tagging and the POI should be removed from the OSM data,
> but that's another problem.
> When are this two POIs really the same? And what if the tags sligthly
> differ?
>
> Thorsten