@Marc Mongenet - you clearly still have a problem with this, but perhaps a discussion on one changeset and a talk page on the wiki (where almost no-one will see it) probably aren't the best way to win people over to your point of view? I suspect that some of the language used here and there ("Laziness", "Dogmatism", "Short-sightedness") won't persuade many people either.
Maybe a breath of fresh air followed by a discussion at https://community.openstreetmap.org would be better? Explain what you believe is the problem and why it is a problem, and explain the approaches that various OSM communities have taken.
Regards,
Andy

Please use better changeset descriptions than just "fix".

Thanks!

（上記コメントを日本語に自動翻訳）

JaLooooNz さん、こんにちは。

このタグは削除すべきだというコミュニティの合意にもかかわらず、service=driveway2 が増殖し続けているようですね。 このタグをデータベースから一括で削除するつもりです。 次のメインディスカッションスレッドを参照してください。

https://community.openstreetmap.org/t/proused-bulk-removal-of-service-driveway2/100549

I agree that "historic=bridge_site" makes more sense than "historic=bridge site", but when you're changing tags like this it would make sense to contact people who are actually consuming the data.
In this case, if you go to https://taginfo.openstreetmap.org/tags/historic=bridge%20site#projects you'll see a link to https://taginfo.openstreetmap.org/projects/someoneelse_style and from there to a github project where you can create an issue.

"Lebeneat" was definitely there on 4th June. I haven't checked since - turnover in these places is high, but not _that_ high. Branding does not match https://lebaneat.co.uk/restaurants/ so may not be associated with that chain.

Thanks - one more question. Clearly OSM failed to make it clear that there even were import guidelines, despite you contributing to the project off and on for a year or so. What bits of documentation were you aware of, and what would have helped avoid this problem in the first place?

Just to mention one other thing - after you have sorted out the licence issues, as you discuss this potential import with the community, please do read osm.wiki/Import/Guidelines again, especially osm.wiki/Import/Guidelines#Using_a_dedicated_user_account . Had you done that it would have saved most of my weekend.

I've no idea how you'd do this in JOSM.
I've undeleted the old nodes, ways and relations that were deleted in error and redeleted a couple of ways in changeset/137766612 . I think that's everything now; although some of the objects referenced in changeset/137720979 perhaps could do with another pair of eyes.

Following on from changeset/137757624, this reverts some older erroneous deletions (incomplete).

The first revert changeset in the sequence that deleted some older items was changeset/137720979 . Subsequent changesets in the same sequence have exactly the same comment. Nodes with ids below 10992910905 that were deleted in that sequence can be undeleted, and also deleted ways with those nodes as members with similarly early ids, and also deleted relations with those ways as members with similarly early ids. See changeset/137757884 as an example.

@josail by all means do help delete the nodes that are left (I suspect that there are only nodes left). I'm going through deleting them with the revert scripts, but if you've beaten me to it that won't cause a problem.
After that I'll recheck some earlier edits (I believe I need to re-add some of the earlier non-import edits that you did - the changeset comments were very similar and some earlier things got deleted by mistake).

Actually, revert still in progress - some were missed in my attempt to revert "only this latest import".

Revert in progress at changeset/137720979 . @josail, please don't attempt to change any of these objects until the revert/redact is completed (might take a couple of days).

Re " The source is neither Google nor Landsat but a completed and stand-alone scientific work published here https://www.seanoe.org/data/00765/87740/ , which in itself among many other sources used also Google and Landsat", I don't believe that you can "licence-wash" data in this way.

There are clearly numerous problems with this data. I'll revert and if necessary redact.

Please follow osm.wiki/Automated_Edits_code_of_conduct to discuss the potential addition of this data to OSM.

Hello,

I hope you don't mind me asking about an edit from 8 years ago. On this changeset you added a "source=Google" tag on node/3670239133 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Hello,

I hope you don't mind me asking about an edit from 10 years ago. On this changeset you added a "source=Google" tag on node/1937435625 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Hello,

I hope you don't mind me asking about an edit from 6 years ago. On this changeset you added a "source=Google" tag on node/4585200897 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used here - it would cause real problems for the project if we were found to be using Google Maps as a source.
If this is somewhere that you are familiar with, then "source=local_knowledge" would be perfectly OK.

Best Regards
Andy Townsend, on behalf of OSM's Data Working Group

Cześć,

Mam nadzieję, że nie masz nic przeciwko, że zapytam o edit sprzed kilku lat. W tym zestawie zmian dodałeś tag „source=Google” na node/686399412 tutaj. W rzeczywistości nie możemy użyć tego jako źródła w OSM, ponieważ licencja Google na to nie pozwala - spowodowałoby to poważne problemy dla projektu, gdybyśmy odkryli, że używamy Google Maps jako źródła.
Z wyrazami szacunku,
Andy Townsend z grupy roboczej ds. danych OSM

Hello,

I hope you don't mind me asking about an edit from a fews years ago. On this changeset you added a "source=Google" tag on node/686399412 here. We can't actually use that as a source in OSM because the Google's licence doesn't allow it to be used - it would cause real problems for the project if we were found to be using Google Maps as a source.
Best Regards,
Andy Townsend, from OSM's Data Working Group