Note that “unusual and not documented” does not mean “wrong” - many should be simply documented.
Changing unusual fitting value to common not fitting value is not helpful at all.
Some may be fixable remotely:
clear typos (shop=suupermarket)
written in language other than English but with clear mapping to local language (for example shop selling meat in Polish is “mięsny”, so shop=mięsny is clearly shop=butcher)
too specialized tags (shop=coal is better tagged as shop=fuel fuel=coal, shop=office_furniture as shop=furniture furniture=office, shop=indian_spices as shop=spicescuisine=indian)
very clear duplicates (hair_salon vs hairdresser)
shop with website, maybe even linked in OSM object, that allows establishing proper value of shop tag - it is also worth adding website tag
in some cases something is clearly not a shop (shop=factory_producing_widgets is likely man_made=works)
needed and valid shop value that should be documented at OSM wiki
Some may require resurvey, if one is luckily in your area you can check it. Or you can create a note and wait for local mapper to resurvey it.
Contacting original mapper may make sense.
Remember, it is better to not edit than break data in case of tagflidling - create note if unclear or unsure.
Let me know if this list is useful but outdated (I will setup refreshing it in such case) or pointless/problematic (I can delete it if it is causing more problems than benefits).
Some improvements can be made to this list… Mayvbe mark cases with nearby notes opened already so these can be skipped for now? And mark cases where website link is available so these can be processed first?
Cases on "entries from list of suspicious ones: " list can get explanations why this values are treated as invalid. Maybe more.
(helping here is useful as it allows to reduce number of not needed and pointless top-level shop values, on 2023-08-14 we had 11 215 distinct shop values, vast majority bogus, broken or not needed. Reviewing such lists also allows us to spot missing shop values, problems with documentation and presets. Repeated appearance of shop value may indicate that wiki or presets should be improved. Maybe iD translation is bad or requires additional aliases for easier search? Maybe OSM wiki would benefit from translating it to local language or being more clear?)
(I can also generate such listing for other areas, let me know if someone is interested)
A bunch of these values, like shop=implement and shop=farm_machinery, sound like candidates for shop=tradetrade=*.
A hypermarket is not quite the same thing as a supermarket: a hypermarket is significantly larger than a supermarket, carrying a wide variety of items besides food, but most of the departments don’t have their own checkout counter as you’d find in a traditional department store.
What tools did you use to generate this? Can you run it for Colorado?
@Minh_Nguyen, I don’t think shop=trade works for farm machinery dealers. I think either farm_machinery or farm_implement works. The wiki suggests agrarian, but that lumps feed/seed/equipment in the same tag & they are rarely in the same place.
I am not entirely sure about exact intended and real use of shop=trade but both shop=trade trade=farm_machinery and shop=agrarianagrarian=farm_machinery and shop=farm_machinery seems reasonable. No idea which one is better.
For some related shop values across world, I have also seen:
shop=trade is a very generic tag, not ideal but at least somewhat well supported in software. The name suggestion index currently has John Deere as shop=tradetrade=agricultural_equipment. The trade=* key is definitely important for anything that gets tagged as shop=trade, since it’s such a catch-all.
As I watch this thread (and there are others similar to it, appropriately, for other regions / countries / languages / cultures / circumstances), I agree with everything Minh has said.
Yes, hypermarket needs its own distinct value (and wiki documentation, to “formalilze” this) distinct from supermarket, they really are different concepts and should be tagged differently. Yes, some Walmarts are smaller neighborhood markets and some Walmarts are more appropriately tagged as a department store. Target stores can also differ similarly (or be both a supermarket and a department store — tag two nodes if so), and I would expect that if OSM wants such differences to be properly reflected in our data, we should have clear tagging documented so it is clear how we best capture them. Yes, a greengrocer is not a grocery store; OSM should distinguish these.
OSM: we started out as blank, became a rough sketch, improve in breadth, depth and sophistication, and should continue to do so! This shop=* topic is a good start at further extensions and refinements.
I will change to this example in new pages, let me know if it is clearly better and I will change it also for several already posted ones in different communities (I intended to have only very clear cases here…)
(change from supermarkethypermarket - in my experience it was used as synonym as supermarket, it was not appearing in OSM tagging on a large scale and in a few cases it existed local mappers considered supermarket as preferable, but maybe it has some distinct use elsewhere or I missed systematic difference)