@SwiftFast, thanks for the thorough message! I will be happy to fix those objects, and I agree that it should have been brand, not operator, as was suggested to me via another channel. Also, thanks for the great forum discussion. I hope we can move forward on some proposals to standardize wd/wp tag usage.

I have been actively adding "wikidata" tags to those entries that already have "wikipedia" tags, which allowed community to perform a lot of cleanups, like fixing incorrect or stale wikipedia tags. I also built a service similar to Overpass that contains combined data from both the OSM and Wikidata databases. This allowed very sophisticated data quality control. Those QA queries are now in the "examples" page, accessible either from wiki or directly from the tool's "examples" button. Moreover, I am very hopeful that your bots can use this service directly, and help with cleaning up and maintain objects everywhere.

Once I tagged substantial number of wikipedia-only objects with wikidata, I started analyzing them all to find places of business that were clearly in large numbers - in other words, those whose wikidata represented a chain rather than a specific place. I believe that I have made a mistake with that edit - they should have been tagged as brands, not operators. My understanding was initially based on how many operator:wp/wd tags there are. I already started reversing this after some conversations, but perhaps a wider discussion should take place before the global cleanup.

I hope we can standardize on wp/wd tags being a 1:1 representation of the object, not its brand/operator/artist/subject/... This will allow a more precise info.

* QA queries osm.wiki/SPARQL_examples
* osm.wiki/Proposed_features/Wikidata
* related, with good discussion on talk page: osm.wiki/Proposed_features/Wikipedia_tag_types
* New page (WIP) - osm.wiki/Wikidata_Classification_Guide

P.S. btw, "ele" was a short departure from my main activity at the moment - fixing all the Wikipedia & Wikidata tags. I am using a mechanical approach with that (I posted and written about it a while ago), after which I use the SPARQL service to find any incorrectly labeled objects. This allows substantial improvement to the quality of OSM data. Please take a look at all the quality control queries available in the examples at http://88.99.164.208/wikidata/ (or see the link above)

Hi Michael, my apologies if it appeared mechanical - I have reviewed every replacement value. I was simply converting "124m" -> "124" per wiki description of the "ele" field and JOSM's autofix suggestion.
I also reviewed the number of ele tags as pure numbers vs those with "m" symbol - looked like a small percentage. I will be happy to create a page on the wiki - what content should it have? Thanks for your vigilance! :)

Hi @naoliv, I renamed it to subject:wikipedia because the wikipedia article is not about this specific OSM object, but instead describes a concept - e.g. an article about McDonalds, should not be used on a specific McDonalds, but instead be set as the subject per wikipedia=* . Same applies to a statue - it shouldn't link to WP about the person who is portrayed in the statue. Keeping wikipedia & wikidata tags in sync is a good indicator of this approach.

hi, thanks for contributing, but the wikipedia link is broken. Please find a wikipedia article and link to it. Thanks!

Hi, you imported wikipedia tags incorrectly. Please fix - they should not have url encoding. Instead, they should appear exactly as shown in Wikipedia with the language: prefix.

Hi, it seems like the data for node/4943267293 is a duplicate and incomplete. Similar one is node/4724280996
I'm deleting it.

The wikipedia article is about a place in Antarctica. I will remove the WP/WD entry, as it seems to be misplaced. Let me know if it should be adjusted. Thx!

Доброго времени. Я переименовал wikipedia & wikidata -> operator:wikipedia & operator:wikidata, согласно описанию в вики. По описанию, wikipedia/wikidata лучше подходят для ссылок по поводу конкретного объекта - музей ссылается на статью про этот музей. Получается 1:1. А в случае когда статья про группу тип объекта, например McDonalds, надо использовать operator:* таги.

Hi, I found a number of duplicate items (mostly stores). I have been deleting them, but you might want to check your script - seems like it creates dups. Also, I am moving wikidata -> operator:wikidata (per wiki). It makes tags much easier to process later. Thanks!

Are you sure the point is correct? Wikipedia point is 150km away from osm's.

I'm assuming the McDonald's operator should be McDonalds, no?

The wikipedia link was pointing to ru:Хребет Черского -- a disambiguation page. I removed it. Are you sure the location is correct? Please fix. Thanks!

@paul, I simply added wikidata tag for the corresponding wikipedia tag. Are there any problems with the data? https://overpass-api.de/achavi/?changeset=48386392

Hi, i have been trying to open that history link, but it keeps giving me timeout errors. Looking at the way object itself, the wikidata item seems to be set correctly, and that's the only thing I was doing.

@samely, hi, specifically which object are you referring to?

thanks, silly mistake, i looked at them but my mind didn't register the weirdness. Thanks for catching it!

hi, thanks for adding wikipedia tags! Please use the Wikipedia plugin to also fetch the corresponding Wikidata tags - makes it very useful for many quality and usecases. Thanks!

Spasibo za wikipedia links. Please use Wikipedia plugin to fetch corresponding wikidata tags too - very useful in many ways.

That's a good question. While my database side tells me to normalize data, and never have any dups (e.g. have a "river master relation" that includes the river names in every language, wikipedia, wikidata, and any other shared tags that apply to the whole river), I understand there are problems with many data consumers to process super relations, so data needs to be duplicated. So I think the wp/wd tags should be on both rels (sadly), and maybe an automation rule should be set up to verify that the wikidata tag is the same. It is not as critical to have WP tag identical - most data consumers should translate the wikipedia tag to their user's primary language using wikidata (I actually think that at some point we should get rid of wikipedia tag outright, if it represents the whole object and not a part of it. See osm.wiki/Proposed_features/Wikipedia_tag_types