Hi,
"destination:side" seems to be new, how is A/B defined precisely?

By the way, it seems the panoramax images on the destination_signs don't work, the API claims they don't exist, e.g.
https://api.panoramax.xyz/#focus=pic&pic=f7042b1c-c2dd-487c-81ed-5db5c6c487ce
node/9091507230

Regarding the name, I wouldn't add any name tag if there is just a description and no real name. At most I'd add the name of the subject in the name tag.

Regarding the rest: 👍

What was in the name tag was a description of the plaque, but not a proper name.

All the "inscription:translation:es:description:XX" tags are nothing else than the source of the translated transcription, so they should be in a source tag.

The -t- syntax is a standard also outside OSM for literally transformed text from one language to another.

In general, translations should not be in OSM - we're not a dictionary. On the other hand, one translation from Latin to the local language can for sure be helpful to understand what the POI is.

If you prefer having the translation in "inscription:translation:es" instead, this is fine with me - although I'd prefer a 'description' tag.

I didn't move the Catalan description to a Spanish tag - there's only a Spanish translation and it's source tag, which is in Catalan.

Hi,
I tried to find out if there is a way to put all the opening hours into one tag but got a bit confused.

It seems like the times you added for Jul-Aug are valid only on a few days, because the rest of the two month would be covered by school holidays. Or are the Jul-Aug times valid for the whole time and the "SH" times don't apply during summer holidays?

The tags you added are perfectly fine. In the database itself, it's always the English name that is stored. The editor software translates them for your convenience. If something is missing in the translation table, it will show the English original. This will happen quite often with rarer tags, because translations are often not complete (yet).

Hi,
welcome to OSM!

I see that you added a couple of 'recycling' tags. 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 have a look to the wiki and change the tags to those listed there?
amenity=recycling

Welcome to OSM.
please don't just dump a large set of data into our database.

I suggest that you start with some basic editing of individual objects. Later you can come back to an import - but this is a complicated task, see osm.wiki/Import/Guidelines

Klingt nach Schuko, aber wer weiß...

Wir haben aber tagging-mäßig vorgesorgt mit "socket:unknown=4" und
"socket:unknown:output=8"

Hi,
schau mal nach dieser Ladestation - die Angabe des Stecker-Typs fehlt:
node/12090042058

Hi,
was ist denn ein "foot_trigger"?

Hi,
it seems there is a mistake in the wiki.
The source tag should be
source:quiet_hours - "source" is almost always used as a prefix.
This is also as mentioned in the text in the Wiki, but the example below shows a wrong tag.
Could you check & edit the POIs?

"small_metal" in addition to the two tags I mentioned ("metal_packaging", "cans") seems to reflect the examples quite well. I think you can just add these three tags instead of the original one.

I suggest to remove the ~ 100 objects that are not tagged correctly for now. Then you can more easily enter them again using the presets available in the editor. That's simpler than trying to edit them in place.

Hi,
these bus stops got three strange tags:

stop_code
stop_desc
stop_url

The first one is a duplicate of 'ref'. Did you really mean to add these tags?

'wheelchair_boarding' is also not an established tag - bus stops are typically tagged with 'wheelchair'.

Yes, I understood that - but the choice of the tag doesn't fit to what OSM uses as definition for 'maxheight'.

Hi,
could you consider another tag instead of "maxheight:fall"? maxheight always refers to a legal height limit, which you tag does not.
Something lime 'hazard:fall:height' might be more appropriate

The tag "emergency" has a different meaning, it's not used to tag an abstract danger of some kind. That would be "hazard". Or, in the case of flooding, the common tag is "flood_prone".

If the buildings just were in danger of being flooded once, but nothing happened, then I'd say that this is nothing that belongs into OSM.

https://github.com/osmberlin/osm-traffic-sign-tool/issues/72

Das sieht nach einem Bug aus. Das Tag "oneway:cycleway" gibt es nämlich nicht. "oneway" oder "oneway:bicycle" wäre korrekt.
An Straßen gäbes dann noch "cycleway:left:oneway" als Möglichkeit.

Hi,
you added "efa:*" tags here. These are not used in other places. Aren't they meant to be "gtfs:*"?