Please check the 'rickshaw' tags you added. These are not in use in OSM. Did you mean auto_rickshaw or cycle_rickshaw?

Hi,
this destination sign got again about 20 new keys that are not used in other places.

There's a problem with the numbered tags:
- I wouldn't use numbered tags on a single-panel sign, if you want to have a change to tag different panels on other signs. Numbers are more or less the only possibility to do that.
- the numbers don't match in the left direction: The 'pier' symbol is matched with 'Tarragona', but in fact all symbols are equally in a separate line.

This simple sign can be easily described in the existing tagging schemes - with one new, additional tag to note that it shows a roundabout with 5 exits.

node/12645204191

Hi,
is that reverted correctly? This shop node now got completely different tags:
node/11655897469/history

I reverted this import for now so that you can start importing these objects again in a clean way.

Hi,
you used the tag "gtfs:ref" here. This is not used in other places. Could you check the documentation for the correct tag? Might be gtfs:stop_id

Hi,
something went wrong here.
First, different languages are given using a ":xx" prefix, not "_xx". It's also not necessary to give several translations if the Latin name is given - all translations can generated automatically with a simple software, there is no need to have all of them in the OSM database thousands of time.

Hi,
something went wrong here. All these objects don't have any valid tag.
Also: Please don't forget to add meaningful changeset comments to your edits!

All nodes have these wrong tags:

Nom = Fondation médicale Saint Raphael
amenity = batiment Public
categorie = Structure privée
institution_de_tutelle = MINSANTE
xcoord = 11.6037621
ycoord = 3.9778637

There is no correct source given and the mandatory link to an import documentation is missing.

All nodes have these tags:

etat = Fonctionnel
niveau_de_degradation = eleve
xcoord = 11.5779586
ycoord = 3.9436049

There is no correct source given and the mandatory link to an import documentation is missing.

I think I managed:

https://openingh.openstreetmap.de/evaluation_tool/?EXP=Tu-Fr%2012%3A00-13%3A45%2C16%3A30-19%3A30%2CTu%2CFr%2019%3A30-21%3A30%2CWe%2013%3A45-16%3A30%2CSH%20Mo%2012%3A00-19%3A30%2CSH%2013%3A45-16%3A30%2CSu%2CPH%2010%3A00-19%3A00%2CSa%2014%3A30-19%3A00%2CJul-Aug%20SH%20Tu-Su%2010%3A00-14%3A30%2CJul-Aug%20SH%2019%3A00-20%3A00%2CJul-Aug%20SH%20Tu%2CFr%2021%3A30-21%3A45%3BSa-Su%2013%3A00-14%3A30%20off%3BPH%2013%3A00-14%3A30%20off&lat=48.7769&lon=1.1844&mode=0&DATE=1707856140000

Could you check that for any (very possible) mistakes?
There is a problem with holiday definitions in May 2025, so better check it in 2024 :)

Hi,
something went wrong here. All these nodes don't have valid tags.
If you want to import a larger number of objects, please have a look to our import guidelines:
osm.wiki/Import/Guidelines

Hi,
something went wrong here. All these nodes don't have valid tags.
If you want to import a larger number of objects, please have a look to our import guidelines:
osm.wiki/Import/Guidelines

Hi,
something went wrong here. All these nodes don't have valid tags.
If you want to import a larger number of objects, please have a look to our import guidelines:
osm.wiki/Import/Guidelines

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