Hi,
you added three new keys for seemingly the same thing, the planned phases of construction. Could you decide on one?
development:phase
development_phase
ref:development

It looks like there is no need for an additional tag here. At the point of the traffic_signals node you can't turn right anyhow - the ways already split 20 meters further west.
The particular design with one common light for all lanes is just a design choice of the street planner - and we currently don't have any tags for such a detailed description.

It seems ChatGPT told you something wrong. "traffic_signal:direction" is just about the direction of travel along the road, not about turning.

Do you have a photo of these traffic lights, then I might be able to help.

Hi,
"traffic_signals:direction:right=arrow" is not yet used anywhere. What does it mean?

Hallo,
die marker=aerial haben hier Tags die es sonst nicht gibt, und die anscheinend nicht nötig sind.

colour und material sind die Tags für den von oben sichtbaren Teil.
Die Form könnte man in marker:shape packen.

support, support:material, support:colour beschreiben den Pfosten an dem es befestigt ist.

Please don't delete tags like 'ele', just because they are not commonly used. They still serve their purpose.
Please also have a look at the description of the 'name' key - such generic descriptions are not to be tagged.

Hi,
thanks for the reply!

- The 'ele' tag can be added to any point, not just peaks.
- 'moutain_pass' is misspelled.
- '(Pas)' is for sure not a proper name and should not be in the name tag.

Hi,
could you explain this change?
node/10672746368

You removed the 'ele' and 'natural' tag and added a strange "moutain_pass" tag.

Hi,
something went wrong here. All of this data are duplicates of existing features.
This happens if you load a geojson or similar file into JOSM and then try to upload it. You have to load data directly from the API or Overpass - every other way will lead to duplicates and not to editing the already existing objects.

I reverted these changes.

Welcome to OSM!
Please don't just dump any data from external sources into the OSM database.
It is necessary that any import of data follows our import guidelines:
osm.wiki/Import/Guidelines

The proposal was made and left inactive. There was no discussion or rejection. The tag is in use for a decade now - although the number of uses is still low.

Hi,
"ad_libitum" is not a common tag. Do you mean "all_you_can_eat"?

Hi,
there are some ways with a strange tag here, could you check that?
osm.org/E.g. way/1391745075

Hi,
I didn't add these names, they are there since 3 years. I just fixed the mistake in the keys with a ':' at the end.

What is easier or faster depends a lot on the specific use case.
Separate tags makes parsing the value slightly quicker (you save just a simple split operation of a string), but on the other hand it makes finding the tags a lot more expensive: Your database request doesn't ask for a simple key, but you need a wildcard search for numbers as subkeys.

In general, I prefer the list in a single tag - any software has to be able to cope with this syntax, supporting yet another tag is a non-issue.

Hi,
please check these edits. The common tag is "motorcycle:sales", not "motorcycle:sale".

Hallo,
ich habe hier ein paar maxspeed tags korrigiert. Die richtige Reihenfolge im Key ist "maxspeed:hgv:forward". Erst das Fahrzeug, dann die Richtung.

Hi,
it's not necessary to add almost 30 "frequency:78" tags to a single object. You can just combine them in a single tag, separated with a semicolon.

Hi,
here are some payment tags on a highway, but there is no tag about a toll or similar. Could you check that?
way/565349328

Hi,
in total 18 of the tags you added are not used in any other place - that makes it unlikely that any tool will understand them. I'd suggest to check some other similar airports to see how they are tagged.

Especially suffixes like "primary" or "ft" are not generally used. Information like the runway length should be added to the runway itself.