Skip to content

replace broken wikidata.org integration#266

Open
k-yle wants to merge 1 commit intotaginfo:masterfrom
k-yle:patch-1
Open

replace broken wikidata.org integration#266
k-yle wants to merge 1 commit intotaginfo:masterfrom
k-yle:patch-1

Conversation

@k-yle
Copy link
Copy Markdown
Contributor

@k-yle k-yle commented Apr 30, 2026

The existing URL for wikidata.org has been broken for several months, see taginfo/taginfo#480 for background info. "Broken" meaning that only the 3787 tags are included in the taginfo project file, but all 846 keys are missing (example), since keys use the new property P13786.

Most tools that rely on these wikidata properties have already updated their code. However, this https://tools.wmflabs.org/wp-world/wikidata/tags.php script is still broken, and I did not get a reply from the maintainer, who seems to be less active on wikipedia these days. The php code also appears to be closed source, and I can't find where/how/who could help to update it.

As a (temporary?) solution, I've created a new script at k-yle/wikidata-taginfo-link and updated the URL to point to this script... i'm not sure how else to solve this problem...

@joto
Copy link
Copy Markdown
Member

joto commented Apr 30, 2026

First, I don't think it is great to redirect an existing project to a new project. Even if the original project is defunct. It would be better to have this as an extract project maybe?

That being said, taginfo has been scraping wikidata for a while, see
https://taginfo.openstreetmap.org/sources/wikidata . So taginfo has all this information available internally already and I don't think we actually need a project that does that. What we could need is surfacing this information already available in taginfo some more.

@k-yle
Copy link
Copy Markdown
Contributor Author

k-yle commented Apr 30, 2026

okay, I'm happy to attempt a PR for taginfo itself. do you have a specific technical solution in mind? For example,

  • should the /keys/{key}#projects page make an extra API request to /api/4/wikidata/keys?query={key}?
  • or should the /api/4/key/projects API add a special extra row using the same data source as /api/4/wikidata/keys?
  • or something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants