Hi,
please explain the meaning of "maxspeed:left:conditional" - "left" is not used in combination with maxspeeds and there is no conditional statement in the value.

Hi,
you used the tags "name:vlce" and "name:vlca". These are not valid language codes. Could you check and fix this?

There's already some discussion ongoing:
osm.wiki/Talk:Key:traffic_signals:countdown

Hi,
you added some climbing:grade tags here. Please check these - the tag needs to specify the scheme of grading, like
climbing:grade:uiaa:max

Hi,
could you explain the meaning of "loculi"? This tag is not used in any other place.

Hi,
you added > 25,000 objects that are plain duplicates of existing objects, but with all tags deleted and replaced by "GPX" tags.

I reverted this changeset and the preceding ones.

It seems something went wrong here - all these nodes got tags like "PTETICHETT = 706468.48,5119460.50,0.00"

Hi,
I noticed that you're adding monoglian names to many objects. Could you check the spelling of keys? I found many keys like with wrong spelling like these:
namr
name-mn-Cyrl
nam:mn:Cyrl

I fixed several, but I might have missed some.

Hi,
could you explain the meaning of the new access tags on some these ways?
E.g. way/892945339/history

I think it might be favorable to use the common "traffic_sign" tag to explicitly state which signs are present.

I think you're reading the Wiki way too literally. I don't see a need for a new tag here - note that even the majority of example images show a countdown for the "green" phase!

Thanks!
I suggest to use a "conditional" tag instead of a new tag.

boat:conditional = no @ (power > 35 hp)

This is not used yet, but it follows a defined syntax and can at least be displayed to the user by tools that support conditional restrictions.

I don't think that OSM is the right place for reviews, ratings and images of containing offers from stores. There are dedicated platforms for this, but a geo-database like OSM is not.

If you plan to introduce such features, the OSM community should be involved in the process. You could write a description of the project on the forums and ask for opinions.

This project might also be subject to our "organised editing" guidelines: osm.wiki/Organised_Editing/Activities

The import guidelines might be applicable as well:
osm.wiki/Import/Guidelines

Hi,
welcome to OSM.
You used many uncommon tags here like these:
becknified
category
image 1
image 2
image 3
image 4 providerId

In OSM we have to use a well-defined set of tags to allow all the software tools to understand the data and e.g. show it on maps.
In OSM we have to use a well-defined set of tags to allow all the software tools to understand the data and e.g. show it on maps.
Please use only keys that are documented in the Wiki or are available as presets in your editor.
Thanks!

Hi,
there's no "gray_water" tag in OSM, it's the BE spelling "grey_water". I just fixed a couple of them.

Hi,
please check all the relations you created here - many of them have keys with a space in them like
"restriction: conditional" or "restriction :conditional".
Please fix these keys.

Hi,
you used tags like "contact:addr:housenumber" on several POIs. The common version does not have a "addr:" part, it's just "contact:housenumber". Could you have a look?

Hi,
it seems something went wrong here - you uploaded hundreds of nodes that look like a todo-list copied from maproulette?

Hi,
you added several "name:t" tags - which language was that supposed to be?

Hi,
you uploaded a couple of ways with a "OSM=false" tag - this seems to be a mistake, could you check that?

Hi,
the new parking tagging scheme doesn't have a tag "parking:condition". Instead of e.g.
parking:right:condition = free
the tag should be
parking:right:fee = no