Hi,
could you point us to a discussion of this change? LL-t-LL tags for transliteration are very rare in OSM, while adding -Script to a language is the common way for names in different alphabets.

Please don't dump all your recorded POIs into the OSM database. Edit them one by one, and upload only those that you reviewed and where you added the proper tags.

The larger part of the edit looks quite reasonable to me.

If you disagree, feel free to revert including my changes.

Something went wrong here. Most of these objects don't have valid tags, many are duplicates of existing POIs, all have a foreign 'gpxicon' tag that shouldn't appear in OSM.

Please check this area, it doesn't have any valid tag
way/1359381878

Hi,
bitte schau nochmal über die ganzen Wegweiser-Tags. Bei vielen stimmt die Reihenfolge im Key nicht, z.B.

destination:forward:lanes
-> destination:lanes:forward

destination:backward:lanes:colour
->
destination:colour:lanes:backward

Hi,
could you check this way without valid tags?
way/1359041111#map=16/39.43509/-31.20944

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?