Please check the tags you added on all these gas stations.

You claim the source is "Official Ukrnafta data" - is this data available under a license that is compatible with ODbL and OSM?

These are not common addr tags:
addr:ISO3166-2-lvl4
addr:house_number
addr:municipality
addr:road

There's no need to have two phone tags:
contact:phone
contact:phone:UA
The number with international prefix should be in 'contact:phone' and nothing in a :UA tag.

Thanks! I just changed the conditional accordingly

Da habe ich auch keine gute Idee.

Ich hatte den Weg nur editiert weil er außerdem noch ein anderes Tag hatte, das da nicht hingehört:

"iD_validator_skip_to_allow_upload=yes"

Hi,
please watch out for the correct spelling of tags. Neither
Highway = residential
nor
hihgway = residential

are proper tags for streets in OSM. The only correct form is
highway = residential

If there is a consensus to add tags this way, it might be helpful. If only you use these tags its not: Others searching for this event will look for "Chido" in the value of a "damage:event" tag, which doesn't exist on these buildings.

Hi,
you added "Chido" to your damage* keys. That's not common for other events - usually the plain tags damage:event and damage:date are used. Could you check and maybe change the tagging?

Hi,
naptan tags with a suffix for station parts are not in use up to now. Would it be possible to add them to different objects instead? The main node could get both values as a list as well.

Da kann ich wenig dazu sagen, ich hatte hier nur einen Tippfehler korrigiert. Wenn sich Leute dafür interessieren könnten, kann man das Objekt sicher auch noch länger in OSM lassen damit es gefunden wird, inklusive dem Verweis auf den neuen Standort. Falsch ist das Löschen aber auch nicht.

Hi Simon,
could you check the boundaries you edited? Several of them got some strange tags on their new ways like this one
way/1355623169

Hi,
"landuse:use" gibt es nicht (weder dokumentiert noch irgendwo benutzt und damit nirgends unterstützt).

Wie das Wiki schreibt ist "greenland" etwas problematisch, weil es nicht die momentane Nutzung beschreibt wie ein übliches "landuse". Mit dem "planned" Prefix haben wir ein gängies Tagging, das sowohl den jetzigen als auch den zukünftigen Status erfasst.

The idea of the tag as I wrote it is that it is indeed open 24/7. The second part defines it do be "open" at any time, just with additional note that no staff is present.

If there is a larger interest in explicitly tagging "hours staff is present for any kind of help or consultation" we can think about properly defining the new tag, but as long as it is only this one station I would use the common opening_hours.

Right. I'll fix that later.

Hi,
Please check the name tags you added. You used the keys 'name-ar' and 'name-en' instead of the correct 'name:ar' and 'name:en'.

Hi,
left/right usually refers to a feature besides the main feature, e.g. a sidewalk on the side of the highway, but not to the left and right half of an object.

While the regulation obviously depends on the left/right half of the road, I think backward/forward is the closest we can get to in OSM using existing tags.

According to wikipedia the standard is
J563-B
https://en.wikipedia.org/wiki/Automobile_auxiliary_power_outlet

The spelling "socket:j563-B" with a minor letter fits to the other j-Standards we already have like socket:j3105-2

Reminder:
I found many keys like
correoelec =
telefono =
sitio web =

Please make sure you use the correct tags for these:
email
phone
website

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.

Could you check this way, it got two strange tags:
way/96007149

I don't see anything special on the (mostly English) signs the wiki article contains.

The destination:arrow tags in the wiki are only helpful if we know the orientation of the sign (unless you want to tag the sign only without relating it to any way close by)

What do you mean by "aren't oriented to cardinals directions"? They need to point in some direction to be useful, and the key we use is one of the eight cardinal directions that is closest to the direction the sign points to.

Hi,
"staffed_hours" is not used up to now. Is there any particular feature that is only available during these hours?

You could use opening_hours for this, like
Mo-Fr 10:00-20:00 || open "no staff present"

Hi,
you used destination:arrows tags here. On destination tags on ways the singular "arrow" is used.

I'd rather suggest to use the "direction_north" tagging scheme - Without the orientation of the sign it is difficult to correctly interpret the direction these arrows are pointing to.