[Tagging] Admin Boundary admin_centre or label roles

[Jeroen Hoek]

On 01-10-2021 10:20, tguen--- via Tagging wrote:
> To me this is the whole point of the label role in boundary
> relations. If renderers used it, tagging the nodes would not be
> needed.

So you are mostly concerned with deduplication of tagging?

Then ideally, from a tagging perspective, a place node with a label role
would not duplicate all the name tags present on the boundary. So you
would get either:

* No boundary, all information (name-tags etc.) on the place-node;
* A boundary, all information (name-tags etc.) on the relation,
automatic placement of label;
* A boundary, all information (name-tags etc.) on the relation, a node
tagged only with place=* or some other agreed upon tagging marks the
label location and has role 'label' in the boundary relation.

> Sounds like we tolerate a worse way of mapping to avoid breaking
> renderers. Renderers probably refuse to change because it works the
> way it is. So the situation will not improve unless we decide to set
> a cutoff date when we no longer guarantee that a place node will
> exist, and notify renderers. It sounds like a proposal is needed to
> get this process started.

I do wonder if just the deduplication of tags is of sufficient benefit
to introduce breakage at such a large scale though. An alternative might
be to consider the place node, when present and marked as 'label', to
always hold the identity tags like the various (and sometimes many) name
tags (and wikidata, website, wikipedia, etc.), instead of the relation.
That would prevent forcing every consumer of OSM data out there to also
process boundary relations for something as basic as place names. The
downside is that it does mandate having a place node. Not sure if that
is a bad thing though.

Keeping all of the name:* tags in sync between nodes and relation is a
bit of bother sometimes (although that could be semi-automated).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211001/2624a674/attachment-0001.sig>