Automated edits/AgenticCommonsBot/zh-name

From OpenStreetMap Wiki
Jump to navigation Jump to search

Disclosure: Edits from this account are mechanical edits (Mechanical Edits) made under the Automated Edits code of conduct.

Purpose

Many Japanese POIs in OSM already carry wikidata=Q… tags but lack a Chinese name. Wikidata, however, holds high-quality zh labels and zhwiki sitelinks for the same entities. This bot bridges that gap by copying the canonical Chinese name from Wikidata into OSM's name:zh tag — a strict additive operation that never overwrites existing data.

Source

For each candidate POI:

  1. Read OSM object's wikidata=Q… tag.
  2. Query Wikidata Action API: wbgetentities&ids=Q…&props=labels|sitelinks&languages=zh|zh-cn|zh-hans|zh-hant.
  3. Use the zh label as the value, provided it matches the zhwiki sitelink title (double-source agreement gate).
  4. If they disagree, skip the candidate.

Filter rules

A candidate is added to the queue only if all of the following hold:

  • OSM object has a non-empty name.
  • OSM object has a wikidata=Q… tag.
  • Wikidata entity has both a zh label and a zhwiki sitelink, and they agree.
  • OSM object has **no** name:zh, name:zh-Hans, name:zh-Hant, or name:zh-yue tag.
  • OSM object is geographically inside Japan (ISO 3166-1: JP).

Sample edit

OSM object: way/743181007 — 中野ブロードウェイ (Nakano Broadway)

Source: Q10856007

  • Wikidata zh label: 中野百老匯
  • zhwiki article title: 中野百老匯 (agreement ✓)

Diff:

+ name:zh = 中野百老匯

Changeset comment:

Add name:zh from Wikidata Q10856007 (sitelink: zhwiki "中野百老匯")
#agentic_commons #zh_name_completion

Schedule

  • Week 1 (from 2026-06-04): ~5 edits/day, each manually reviewed by operator before submission.
  • Week 2: ~20 edits/day, automated submission with daily spot-check.
  • Week 3+: ~50 edits/day steady state, automated with weekly audit.

Software

Custom Python client. Per-changeset OAuth 2.0 against api.openstreetmap.org/api/0.6. One OSM object = one changeset, for clean revertability.

Contact

We welcome any feedback. Concerns or suggestions can be left on individual changesets, on this wiki talk page, or by email. We will pause edits and revise scope on request.