That's still an import. Quoting osm.wiki/Import : "Importing is the process of uploading external data to OSM." And osm.wiki/Import/Guidelines clearly say you need to discuss before import.

There are two problems with that approach:
a) OpenStreetMap is not about official data. Especially when it is clearly wrong. Actually it might well be that it is not wrong, but the coordinate datum is different and you did not account for that.
b) You can not add date to OSM without conflating it with existing data. The situation now is much worse than before. If you add data you must make sure to improve the situation, not make it worse, before you add the data. We have had too many imports where people promised to fix the data but never did leaving a mess for the community to fix.

The other question is: Did you consult with the community about this import of data as required by the import guidelines?

I suggest you revert your changes and *after* you have consulted with others and found out how to solve the problems do it properly.

This changeset created several island that appear to be in the wrong position, overlapping existing islands. Please check and fix!

Can you please check this changset. It adds 10000 orphan nodes, i.e. nodes without tags and there are no ways or relations referencing these nodes. This is not the only changeset with problems, there are currently over 270,000 orphan nodes in the database created by you. It seems something in your workflow tends to create those orphan nodes!

First, we should discuss this in English. Second, it doesn't matter what other maps do, we have our own rules in OSM.

If there is a difference in opinion of how something is to be mapped, that's okay, then we should discuss that. But a change of this magnitude isn't something that you can just do without discussion.

As a side effect of this change the coastline processing is currently stalled which means that most OSM maps worldwide will not get updates to any coastline worldwide until this is resolved. That is not a good situation. So please revert this change and then start a discussion on the community forum about the different interpretation of where the coastline should be.

This changesets moves the coastline in a huge area away from the original coast to the wrong place. Looking at the aerial images this looks to me like a marshy area affected by tides and therefore part of the ocean.

See https://osmdata.openstreetmap.de/internal/coastline/ and https://tools.geofabrik.de/osmi/?view=coastline&lon=67.81567&lat=24.12069&zoom=9&overlays=coastline for the affected area.

Please revert this change.

The problem is that while you are working on this coastline processing for the whole world is stopped. So most maps are not updated with current coastlines until this is resolved. This does not affect only your coastline changes but all coastline changes anywhere.

I am not sure I am on the right changeset here, but there were several problematic changes to the coastline in northern Russia around this area. The coastline moved quite a lot, you can see that here https://osmdata.openstreetmap.de/internal/coastline/ . I am not familiar with that area but just looking at it it seems that that large river delta is at least partially tidal and should therefore be classified as ocean water, not inland water as it was before. For the time being coastline processing is halted until this issue is resolved.

OSM ist keine Werbeplattform, insbesondere ist die "description" nicht für Werbenachrichten gedacht. Bitte beschränke Dich beim Eintragen auf Fakten.

These changes totally broke the coastline. The coastline must always be a continuous line, but your coastline isn't and it is not connected properly to the one that was there before. Please fix this.

Please don't add bogus coastlines in the middle of nowhere. I am going to revert this.

I am not happy with this change turning the whole atoll of Tikehau into an island. There is not one massive island here, but many islands. Each of those islands has its coastline tagged already, so tagging natural=coastline in way/1276228955 is wrong in my opinion.

Bei OSM sammeln wir Fakten über die Welt, es ist keine Reklame-Plattform für SEO. Daher habe ich die Beschreibung wieder gelöscht.

I am reverting your change here. The coastline must always be mapped as one continous line everwhere, this small piece is not connected to the rest of the coastline which breaks coastline processing.

See https://tools.geofabrik.de/osmi/?view=coastline&lon=3.32393&lat=6.42702&zoom=13

Das ist 15 Jahre her, so genau weiß ich das auch nicht mehr. Aber wir hatten damals eine Liste von Brunnen von der Stadt irgendwie bekommen (daher auch dieser Tag karlsruhe_brunnen_ref). Ich nehme an, dass der Name da so drin stand. Aber ich muss Dir recht geben, so wie wir in OSM den name verwenden, passt das da nicht rein. Ich nehme den mal raus.

Thanks! Looks good.

I don't care about water=lagoon, I care about natural=coastline. That has to be tagged around the ocean, and the lagoon is part of the ocean. You can see the current situation when you look here:
https://tools.geofabrik.de/osmi/?view=coastline&lon=-97.45166&lat=21.61045&zoom=10
As you see, the lagoon is not part of the ocean any more. (Instead the island are now ocean...) Only because part of the ocean is also something else doesn't mean that it isn't part of the ocean any more.

You changed the Laguna from part of the ocean to inland waters. But the Laguna is clearly part of the ocean by all definitions that we have. Please revert your change.

You can see the problem here for instance: https://tools.geofabrik.de/osmi/?view=coastline&lon=9.66776&lat=58.99048&zoom=18

It looks like you imported some coastlines which now overlap with pre-existing coastlines creating a big mess. Please clean up your import!