> , but it is also not worse than before.

untrue.

A new "shop=yes" will just get lost in the other 180k "shop=yes". We know they won't get spotted because the other 180k of them have not been.

Updating something that you do not even know exists with a "new" value means something that looks at the last modified date might think that it has been verified recently when it has not.

Your actions here are making it harder for local mappers to improve the quality of data in OSM. You should stop now.

Hello,
I can probably guess "SAU" (Saudi Arabia) and "YEM" (Yemen) here, but what are "GHSL" and "EC" here? "add villages and details" is of course perfectly descriptive.
Best Regards,
Andy

(although how "Egypt" is relevant to a change in Oman I have no idea)

Please, using meaningful changeset comments. Assuming that "#EGY" here actually means "Egypt", why not use that one extra character and have people understand what you mean, as opposed to not doing and leaving them guessing?

Are you sure that node/2361007180/history is still a shop at all? What action did you take to verify it?
If none, how does what you have done here improve the quality of OSM?

Clearly the change to e.g. way/353944525 is causing information to be lost here (not much information, but still something).
The correct tag here would be "shop=charity".

With node/6813245577/history it might make sense to talk to the original contributor. Clearly shop=yes is not a good replacement here.

You've replaced a few like node/6590059464/history , but is the replacement here perhaps less precise?

A heads-up might have been nice here. Do the subtags need on node/1178915529/history need to be changed or discussed anywhere?

See osm.org/user_blocks/7131 .

Oh dear. See See osm.org/user_blocks/7131 . .

Thanks

Alas, the "East Riding" added as a subarea to the traditional county of Yorkshire here is the wrong one, it's the modern unitary authority relation/88083 , noth the old Riding which way/56150279 would be on the boundary of.

Thanks!

Just to note another issue with this data, node/501242848/history shows "very rounded" and likely inaccurate coordinates: 7.5833330, 11.2500000 .

Also, the ways that have been added to the superrelation relation/1992599 need removing.

OK, so it looks like all of the bits of relation 9579 that go from Hessle into Hull and out again (roughly here relation/9579#map=12/53.7471/-0.3904 ) need removing from that relation, and ways that form the new route of that relation between Hessle and Cottingham need adding to 9579.

I'll revert this, but where data has been edited, I'll leave the edits.

I'll revert this, but where data has been edited, I'll leave the edits.

I'll revert this, but where data has been edited, I'll leave the edits.