Hi,
I found about 20 damage-related keys with various spelling mistakes, wrong key/value combinations and so on.

I changed them to the documented use of damage / damage:event / damage:type that have been used for dozens of disasters since at least 15 years:
damage:=**

Hi,
what does 'name:yandex' mean? This tag isn't used in any other place.

Oh, I just opened the last changeset of one of the ways and saw the usual inconsistent map where some tiles were updated and some outdated. Then it was obvious that one version had 'unpaved' surface rendering and the other one not.

I found the edits due to the new tag "name:yandex".
There's a list using Taginfo with new keys which are mainly tagging or spelling mistakes:
https://osm.janmichel.eu/taginfo/newkeys.htm

Ah right, I didn't check careful enough. There were some 'surface' tags that are missing now.

These imported objects have many tags that are not used in any other place. What is the source of all this data?

Please make sure to read and follow the OSM import guidelines before any import of data:
osm.wiki/Import/Guidelines

Hi,
why did you delete so many roads here? You replaced them by new ones, but some of the new ones are missing information that was there before.

When adding new data please make sure to always edit the existing object and don't delete old data.

Hier sind zwei Bänke mit "bind=yes", das sieht nach einem Fehler aus:

node/13276435441

Hi,
the parking tags you used here are outdated. Since a few years there is a new, more detailed scheme:
osm.wiki/Street_parking

Hi,
you added a new tag "diameter:trunk:range" here. The common tag for the size of a trees trunk is 'circumference'. Could you adapt these measurements?

All of these buildings have tags like "area_in_me", 'cat' or coordinates which shouldn't be in OSM.

Please read and follow our import guidelines before importing data!
osm.wiki/Import/Guidelines

Hi,
could you explain what this "waterworks = water_control" is? This tag isn't used in other places.

Thanks!

A building needs to have a tag describing it is a building.

There shouldn't be any tags like "are_in_me" or coordinates like in your changeset.
I also noticed that the alignment of buildings is very bad - buildings overlap in many places which clearly can't be right.

I reverted this upload for now, please start with documenting the planned import according to the Import Guidelines.

There is no requirement to have a source tag for every tag. E.g. imagery is the same throughout a changeset and should be added to the changeset itself, but not to every individual object.

If my edit to "source:geometry" made it too short, please feel free to add the year back to the tag.

It's "source_ref": "Used to link external source of information"
source_ref=*
I used the key "source_ref:name" - the reference to the source of the 'name' tag.

23 source tags for the name of a minor residential road is too much.

It's not meant to provide a full bibliography with author, title, isbn and year of publication. As the tags are now one can still identify the place you got the information from.

At the very most it would be sufficient to have title and isbn in a single tag, all other information and tags are not necessary.

Was ich gesehen habe sieht gut aus.

Hi,
"hazard:flammable_gas" is not a common tag. Is there a ban for gas-fueled vehicles here? That's often tagged as "access:fuel:lpg=no"
node/13257381979

Hi,
which language is "name:au"? That's not a defined language code.

Something went very wrong with this import - all the objects don't have valid tags, they are overlapping with existing buildings and roads.

I recommend reverting this edit, and starting fresh after reading our import guidelines:

osm.wiki/Import/Guidelines

z.B. bei Taginfo nach dem richtigen Wort suchen und ähnliche Tags anzeigen lassen.
https://taginfo.openstreetmap.org/keys/separation#similar

Dann einen auswählen und rechts oben auf Overpass Turbo klicken.