osm.org/note/3652104
osm.org/note/3425483
osm.org/note/3580622
osm.org/note/3580624

Okay! I didn't think it could have been from a survey because of the huge area covered. So I had thought maybe it was random items traced from aerial imagery but you obviously could not have seen a bench that way. And I had also thought it might have been an import because so many of the items were about railways.

If you had a three week long railway themed trip that explains everything! Hope it was a good trip. You visited a few places I know well :)

Hi IIVQ. This change and osm.org/changeset/136694495 are very odd. Most of your changes are in Europe but then you made two changesets of 300 random objects across several states and provinces in the US and Canada. Most seem to be tiny geometry updates but some of them look problematic, like
osm.org/way/1177288580 or osm.org/node/10937226756

What is going on with this change and did you import any data?

Most were about 10m off and in different directions from each other. So likely not just an offset error. I am using the (0.60;-1.54) offset for Bing in Montreal.

I was unable to determine what the correct boundary should be here. It would likely take some pretty deep research, or may not be knowable at all.

Is it worth guessing in order to silence the errors?

Hi bhietsch, same question about the segment in Granby, VT.
osm.org/way/1077477141
osm.org/way/1077477036
osm.org/way/1077477156

J'ai pas changé le nom d'aucun autre MRC.

Je voudrais discuter avec la communauté sur community.openstreetmap.org mais il y a pas de catégorie.

You've added the name "D'Auria Street" to a segment of the East River as part of this change. Is that a mistake?

osm.org/changeset/134187294

Désolé. Je suivais les noms écrit sur le site web de MAMH, comme ça: https://www.mamh.gouv.qc.ca/repertoire-des-municipalites/fiche/mrc/140/

Je vais remplacer les noms de tous les comtés qui partagent un nom avec une ville.

A little more information: Usage was about 2/3 cookies, 1/3 cookie before my cleanup, which is why I had picked cookies originally. But after more thought, cookie is the better value because it matches other singular values. Also, it looks like "cookie" was used more for places that serve specifically cookies and "cookies" was used a lot in long lists where mappers added everything on the menu.

For almost all of these choices between spellings I changed them to the most common spelling at the time. For example:
salvadorian(16), salvadorean(14), Salvadoran(10) -> salvadoran(69)
taco(152) -> tacos(972)
hot_pot(198) -> hotpot(687)
sandwiches(566) -> sandwich(60440)

For something like pupusa, where there were a lot of different spellings (pupusa, pupusas, pupuseria, etc), but none had more than a handful of uses I moved them all to the singular term.

On Korean barbecue: The korean_bbq tag only had 11 uses, not enough to be supported by any consumer, and it has an abbreviation which we would like to avoid in tag values. Changing these to korean;barbecue allows the data to be used by consumers since both values are common. And, unlike Mongolian barbecue, the cuisine both is Korean and is barbecue. I suspect there are hundreds of Korean barbecue restaurants currently tagged as "korean", "korean;barbecue", or just "barbecue". In order for a korean_barbecue tag to be useful someone would have to go through and tag them. Leaving 11 restaurants as "korean_bbq" wouldn't have made that easier.

(Also I fixed that mistake you found, thanks for pointing it out.)

@willkmis the name of it is pretty clearly "California cuisine", the Wikipedia article is titled that and the restaurants say it like that on their websites. So I think that's what the tag should be. IMO it's less important that the cuisine titles all look the same and more important that they actually describe the cuisine and that future mappers will use the same spelling.

I did the mongolian grill work. At the end, my changeset had 156 mongolian_grill restaurants and only 3 true mongolian cuisine restaurants. This was for US+Canada.

I didn't know about the difference between California and Californian cuisine. You're right that they should be tagged separately. This affects 26 restaurants in the US (40 worldwide), that are currently tagged with california or californian. I checked the 16 US restaurants with websites, and 7 of them did say "california cuisine", but four of those were originally "cuisine=californian" and not changed in this changeset. I set those seven to california in osm.org/changeset/131741561. Going over the other restaurants or finding more restaurants to tag would require more work, but could be worth it if you want to promote cuisine=california as a recommended tag.

I also did not realize Mongolian barbecue is not actually Mongolian. However, it seems I am not the only one. Before my cleanup started, there were 183 uses of "mongolian" and only 15 uses of "mongolian_bbq" plus a few with other spellings. Most of the restaurants currently tagged mongolian, at least in the US, seem to actually serve Mongolian barbecue. Given the number of uses of the tag and the fact that these restaurants are not really Mongolian or even barbecue, it would definitely be a good project to go back over them all, start using a "mongolian_barbecue" tag, and add notes to "mongolian" and "barbecue" in the wiki.

These kinds of projects should be much easier now that misspellings and incorrect delimiters have been corrected.

Caused by osm.org/changeset/131520276

Fixed in osm.org/changeset/131522973. I found the restaurant that should have gotten the tag, it was Wing's 'N More in College Station. I spot checked the others and it looks like the cuisines and other tags were not affected.

Oops that was a mistake. There was one restaurant with a cuisine along the lines of "cusine=burger;happy_hour" so I changed it to "cuisine=burger" and "happy_hours=yes". It appears that I accidentally had many restaurants selected and applied the change to all of them. I still have the data downloaded in JOSM so it will be an easy fix. Thank you for noticing it and letting me know.

Hi ChaireMobiliteKaligrafy, I used the offset for the change and for all my other changes in the area. I'm the same one who added the buildings here last month, I just changed my display name recently.

Okay I fixed it!