The reason for such a warning is likely that there are 3 tags that are not common / misspelled / not used anywhere else:

conservation = yes
flood control = yes
water = intermittant

Hi,
could you check this building, it got a strange "infraction" tag:
way/977167609#map=19/35.86182/7.13142

You're right, I just copied the original tag to the value.

I just changed it.

Hi,
you added several "socket:sec1011_t23" tags. There's a small mistake though, the socket is called 'sev', not 'sec'. Could you check and fix this?

Hallo,
warum hast du hier bei einigen Relation vor die Tags ein "+" eingefügt?

Hi,
you used the tag "wheelchair_access" here. This is not used in other places.
The common tag is just "wheelchair".

Could you check & fix that?

Thanks!
For this I'd recommend:
man_made=monitoring_station
monitoring:weather = yes
weather:lightning_detector = yes

This combination is already used a dozen times.

Hi,
what is this POI? Communication via lightning seems strange.
node/9041316684

I also wonder about these tags on bus stops:
network = 4801
operator = 4801
ref = 4801

This seems to be the number of the bus service, i.e. it should be tagged as 'route_ref'.

Hi,
please check these edits - there are several objects with many foreign tags that look like they shouldn't appear in OSM.

Hi,
what does "centre_no" mean? This tag isn't used in any other place.

Hi,
tags like destination:left or destination:straight are not common and undocumented. Could you check the established tagging methods and use one of those?

There are three different ones:
osm.wiki/User:Mueschel/DestinationTagging

You can use the destination_sign relation in combination with sign nodes or put the destination on the road leading away from the intersection

Hi,
could you check this node, it got a strange (name?) tag:
node/331902167

Hi,
please watch out for the correct spelling of keys. It's "name:sr-Latn", not "name:sr-lat". I just corrected a couple of them.

I reverted this changeset. All of the objects are duplicates of other nodes with the same "information" on them.

This import of data went wrong.

- there are foreign tags on every object
- there are misspelled 'farmeland' tags on every area
- the geometry of areas can't be right
- the areas overlap with already mapped farmlands
- all the nodes got the same tags as the areas.

I think this import should be reverted and then can be done again, fixing the data and following the Import Guidelines.

There was a 'widthcycle=0' tag added 6 years ago by a user active for only a month. I don't think it helps to copy this tag to another spelling and keep it. It's neither defined anywhere nor does it make sense in any way.

Defined keys are cycleway:width or maxwidth:bicycle, but both should not be added without checking the situation on the ground.

Hi,
thanks for the reply.

So, this is yet another approach to tag how a bicyclist might feel. There are already several approaches by local communities. For some reason they all claim their own approach is incompatible with existing tagging, use it in a very small area and don't write documentation.

There is at least the documented
class:bicycle=*

There is someone in Minnesota advocating "LOS" and "LOS2" tags.

There is a larger group in Berlin who developed a scheme to describe physical features of bicycle lanes in great detail (unfortunately in German only)
osm.wiki/Berlin/Verkehrswende/Radwege#Tagging-Beispiele

... and I think I remember at least 2 more "bicycle experience" schemes, which I can't find now because of the obscure keys they used.
I think it would be beneficial to start a discussion about a tagging scheme and involve all these groups in it.

Hi,
what do these tags mean? They are not used in any other place.

minwidthcycle = 0

Hi,
could you check these waterways? There are 14 with a strange 'navn_1_skr' tag.