Hi,
you added about 30 tags that are not used in any other place - this is (in general) too much for a simple shop.

Usually we don't map all the different services and products of a shop in detail - that is just too much information for a geo-database like OSM.

For some other tags, check the wiki for

min_age
surveillance
contact:instagram
language:*

Hi,
ich habe ein paar "authentification" Tags korrigiert - korrekt heißt es "authentication".

Seems fine to me. I think we should have it documented on the Street_Parking wiki page.

Hi,
you started to use the tag
parking:both:ticket:zone

I'm aware the Wiki lags a way to distinguish ticket and resident zones.

There's already
parking:both:zone:residents in use.
I therefore suggest to use the same order in the key here:

parking:both:zone:ticket

I reverted these changes.

If only residents have access using an QR code, you can tag this as

authentication:qrcode=yes
access = residents

I would not add a payment tag, because there is no way to pay for the containers directly.

Hi,
could you check the waste amenities added here?

- a "waste_transfer_station" is usually a larger industrial complex, but not containers in a residential area
- the different things collected are usually tagged as 'recycling:*', not with the 'waste' tag
- what does "payment:tax" mean? This tag is not used in other places.

Regarding the containers, see
amenity=recycling

Something went wrong here - there are 55000 new objects without any proper tag.

Hi,
you added a strange "sharko" tag to thousands of objects. Was this added by mistake?

Hi,
there are a couple of tags here that are not in use up to now. Could you point us to a definition of them? Numeric "level" values are always quite difficult to understand without a proper definition.

noise_level = 3
safety_level = 4
security_level = 4
soundproof_level = 3

The phone numbers are *from* different countries, but not *for* different countries. Both have a country prefix and are reachable from anywhere in the world.
The phone:XX tags with country suffixes are used for local phone numbers (often toll-free or special numbers) that are only usable within one country.

It's hard to judge what the best solution is. If the codes refer to different parts of the station, I would map them as such. If the station just has two codes, I'd add them in the main tag as a list.

Nevertheless, could you decide for one spelling of the suffix?
E.g. there are:
network:wikidata:Elizabeth_Line
network:wikidata:Elizabeth_line
network:wikidata:Elizabeth line

Hi Robert,
I see that you started to use a properly namespaced version of cqc location ids. Could you also have a look to the 100 existing

cqc:location:id
cqc:location_id

and check if they can be updated as well?

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.