Suggested Wikidata edits

Subjects (cities, organisations) that have a flag image attached via P41 on their main Wikidata entity, but no dedicated "flag of X" entity exists for the flag itself. Until someone creates one, OSM mappers have nowhere correct to point flag:wikidata= at, and this site can't include the flag. Open the subject to see what's already there, then create a new Wikidata item with instance of: flag (Q14660) and flag of: <subject>. Use the batch creation page to review the auto-tagged rows and generate a QuickStatements batch.

OSM mappers tag flag:wikidata=Qxxx, but Wikidata's entity has no P31/P279* link to flag (Q14660), flag design (Q69506823), or flag or coat of arms (Q17335294). The fix could go either way: if the QID really does describe a flag, add the right P31 statement on Wikidata. If the QID describes something else (a country, an organisation, a building) and was tagged in error, open the OSM elements in overpass-turbo and retag them to point at the correct flag entity.

Note: the main identifier hides records that fail this check so mappers don't accidentally reinforce a bad tag. Records still appear in all back office pages for cleanup.

Wikidata's flag entity has no P18 image, so this site shows a placeholder. If a flag image exists on Wikimedia Commons, add it on Wikidata to populate the grid here and on every other site that reads from Wikidata.

Flag entities whose Commons image was set on Wikidata's P41 (image of flag) property instead of P18 (image). P41 belongs on a subject entity (a city, organisation, etc.) pointing at the image of its flag — not on the flag entity itself. When set here by mistake, mainstream Wikidata consumers miss the image entirely.

Fix on Wikidata: move the value from P41 to P18 on the flag entity (cut-and-paste is fine; the statement is identical, just on the right property). Our build falls back to P41 so the flag still renders in the meantime — you can see the thumbnail in the row below.

Flags this site believes have distinct front/back sides but whose Wikidata entity has no P7417 (image of back side) statement. Source list seeded from the English Wikipedia article; add to data/known-reverses.json by PR when you find another.

Modern rows: the listed QID is the current flag and it really does have a distinct reverse. Pick a Commons candidate and paste the filename into P7417 on Wikidata. Once the statement lands, the reverse image flows in on the next npm run refresh:wikidata and the site's flip-to-reverse button lights up.
Historical rows (amber badge): the Wikipedia list flagged a historical variant, but our QID is the modern flag entity — whose obverse hasn't changed and whose reverse hasn't either. The right fix is a brand-new Wikidata item for the historical flag, with its own P18 (obverse) and P7417 (reverse) statements, then link it to the modern entity via P155 (follows) / P156 (followed by). The candidate column lists both sides so you have everything ready when creating the new item.

Wikidata stores a flag's colors as P462 statements. We compare what Wikidata has against the curated palette this site uses (Wikidata + manual overrides). Adding missing P462 on Wikidata makes flags more searchable across every tool that reads from Wikidata.