I think the idea of the iD developers was to add "not:brand=XXX" when a mapper selects "this is not that brand" in the editor.
This would then make it clear that the feature had already been checked and noted to be different than the expected brand based on the name. But wisely, they decided not to do that right away, since the tag had not been documented and discussed. - Joseph On 9/19/19, Jmapb via Tagging <tagging@openstreetmap.org> wrote: > On 9/14/2019 10:53 AM, Tim Magee wrote: >> I would absolutely agree with this use case. Especially for cases such as >> the >> regularly mentioned Burger King. If somebody from out of town is either >> traveling through or armchair mapping they could be confused. If they are >> using the ID editor, it suggests that you "upgrade the tags" which could >> lead >> to a "Burger King" that is not part of the international Burger King tag >> having the same brand:wikidata tag. > > Personally I have a problem with the asymmetry of work that this > requires from mappers who need to protect their work from iD versus > mappers who blindly "upgrade" using iD. > > The first mapper has to 1) be familiar with all possible brands (Burger > King is a brand most mappers know, but take a look at all the brands in > this list: > https://github.com/osmlab/name-suggestion-index/blob/master/brands/amenity/fast_food.json > ...and that's just the fast food!) 2) recognize when a feature might > have a brand conflict 3) look up the brand in question and 4) correctly > tag the "not:" prefix for brand in question. The second mapper simply > has to hit the "upgrade" button when prompted. > > I certainly have no problem with the idea that iD and other editors > would respect the "not:brand" tag when applying brand info to a feature. > But I'm not buying the idea that these "not:" tags are the solution to > the increasing problem of brand tags being incorrectly applied by iD > (sometimes along with incorrect corrections to name, cuisine, etc.) > > The simple truth is that automatically adding these brand tags is a > mechanical bot edit, and the fact that the bot in question is triggered > by a user clicking an ambiguous "upgrade" button doesn't change that. > These edits should be subject to peer review here on the tagging list, > and the iD branding bot should behave according to the automated edits > code of conduct. Yes, this is slower, but it's the right way. Putting > the onus on the original correct mapper to prevent iD's incorrect tags > seems backward. > > Jason > > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
