This is actually wrong. The absolute position is correct. It's the two relatively positioned on the west that are inaccurate in the first place.

Bucharest Henri Coanda, the `building=` vs `building:part=` problem way/771096083

`=terminal` without `building=` xamples:
LHR T5 relation/334919
CDG T3, separated into arrivals and departures relation/8473008
NRT T3, it may be asked what's the difference when the bridge is constructed together relation/8900158
Bahama, very interesting case of 2 small `building=` separated. Is anyone going to make them separate `=terminal`? relation/16025827
Honolulu International T1 Concourse B relation/14332839
These are better handled by `=concourse` inside.

1. For "invalid", I used it to the clearly ill-defined `site=terminal` which has no indication on what "terminal" it is.
2. `=university` is basically used as a university campus. But this is not comparable. Using `=terminal` for concourses is similar to using `=university` for Main and Centennial Campus in HKU separately, when they are continuous. That's actually named "Main Estate" officially, due to confusion with the old "Main Campus".
3. A `=site` + `=terminal` and `=terminal` polygon referring to different things is contradictory. You can notice there is a `perimeter` role defined for `=site` . Main T1 doesn't fit that.
3,4. If you see a possibility for main T1 and NSC to be 1 `building=` , isn't that conflicting with your preferred definition of `=terminal` to be 1 `=terminal` + `building=` ?
6.1. As I said, OSM has more precise, technical, and professional treatment. Other apps will have their own limitations, and they don't care about what is `=stopway` etc either. If you search "concourse vs terminal", you can see many results, and how they can be treated as different levels. You can see the same thing in HKIA officially, where they put all the T1 concourses in 1 tab. https://www.hongkongairport.com/en/map/
6.2. A `=terminal` covering all the `=concourse` shows what is accessed from the terminal completely. They can see the different `building=` without the need of a `=terminal` . It's also not exactly the same for navigating passengers. In the same main T1, they have to take the APM to West Hall for NW and SW concourse, while they can walk from East Hall to T1 Satellite Concourse directly. What matters is reaching the airport, where they only need to choose between T1, and T2 in the coming future. For the latter, the 2 buildings are called T2 and T2 Concourse. Making them different `=terminal` doesn't aid understanding. They can only go to T2 terminal directly.

Terminals vs concourses matters for presentation in application. A passenger going to an airport only needs to look at terminals first, then the concourses after entering. Making many `=terminal` inside the airport makes them less useful.

A wiki definition isn't absolute, and it may be using common language, or describing common simple case of having 1 terminal and 1 concourse only. `building=` already means it is a "building". Repeating this definition in `=terminal` is redundant. The emphasis on "building" may also refer to how you shouldn't draw the `=terminal` to cover the apron, only the passenger facility.

1. Why is it "invalid"? There's no "not accepted", especially for such a specialized topic. It is used by a few already. As asked there, JFK does have concourse A and B in Terminal 4. That remains unsolved.
2,3. I have already considered backward compatibility. The presence of `building=` is on those 2 `aeroway=concourse` should be enough. There is no necessity to enforce a one-to-one correspondence between `=terminal` and `building=` . For example, if Sky Bridge is considered as a `building:part=bridge` , can main T1 and NSC be 1 `building=` ? The definition of a `building=` may vary. The main problem here is both MFC and NSC are named "concourse", and marked as T1. That should be consistent with the 5 concourses in main T1.
4. There is no such thing as you must use "approved" features osm.wiki/Any_tags_you_like
5. You know you can discuss on my changeset first? Saying "fix incorrect" without checking doesn't help. You say "and it seems to make no sense to me personally. " , that's why " This doesn't automatically mean you should remove them. They may have been added for a specific purpose. If you think they might be junk then try to contact the author. ".

T1 is one terminal. MFC and NSC are 2 concourses of it. This follows the name, obviously.
2. `site=terminal` is invalid. What "terminal"? `aeroway=terminal` should be used Don't use `=site` either when `=multipolygon` is fine. Then it has the meaning as T1 being a `=terminal` covering all of these concourses. It is inconsistent to have some concourses being `=terminal` . and others simply a `building:part=` . This doesn't follow how they are named as T1 either. Different `building=` doesn't matter.

Actually Ft Lauderdale, and Richmond. In any case, please follow osm.wiki/Good_practice#Don't_remove_tags_that_you_don't_understand

Please read osm.wiki/Talk:Aeroways#Aeroway=concourse . This is in use in JFK. This is not a `building:part=` . It's meaningless to use it without different `building:levels=` etc 3D attributes.

Please don't upload test edits to a live public database. This is considered vandalism.

Please don't change minibus stops to franchised bus stops. Create a new point.

Please don't remove the `landuse=highway`

1. Please don't add `tourism=aquarium` inside a `=theme_park`
2. Please don't use `tourism=attraction` with `attraction=` facilities

Please don't delete then recreate basically the same thing. This has no difference.

That's why it's better to list them out on wiki instead of Github, if not help creating the wiki page. Few people will check external websites. Only Bing and DuckDuckGo shows your issue, not Google. Now it's basically unknown, causing these questions.

This rectangle is for the lot. It can be seen from old maps. You should create a separate object.

2. For back offices and online shopping, please don't use `shop=`

You don't occupy the entire building. Please create a point inside.

Also conceptually it's a shared straight or right turn lane. This may reflect it better.