1. Any GIS or geo-database application could do a spatial join to append the `landuse=residential` `name=` to `building=`. On the contrary, you can't remove them as easily when considering button and label names, which creates clutter. Bus routes has the same problem.

There are many address formats which applications may not support. Even for UK. And HK is more complicated than UK in some sense.

1. That isn't relevant here. If you follow by the books, you would look at `addr:housename=` . Besides, another rule is not to artificially make composite names, ie combining different features' names.
2. It's the best option. All this does is make managing building names more complicated.
3. Not a data problem. Carto is a static raster map background. Any proper application should have more overlays and clickable buttons.

Please don't add the estate name to the `building=` . This is not the common practice, and makes the data more complicated.

Please notice that `residential=apartments` is described for housing estates, and that's how it's used in HK. Don't use it on single building ones.

Please pay attention that Hong Kong uses billingualism in names. It's not redundant.

3. Please don't use `building=hospital` for something that's not a hospital.

2. Its management is irrelevant to Red Cross.

2. This should not be said as under the Red Cross. It is for HK and HA.

Please pay attention that no donation occurs here. This doesn't reflect its function.

`name=` should be proper names only. Don't add descriptor labels,.

Please don't add descriptor labels to `name=`

Please don't change `=unclassified` . `=residential` should at most be used for local streets.

2. And please split your uploads. They are unrelated.

1. Please don't delete and redraw to pencil-tip shape intersections. This unneccessarily distorts the left turns, and will confuse routers and applications. At least you don't need to modify the ground-level southbound. https://labs.mapbox.com/mapping/mapping-for-navigation/modeling-intersections-for-map-navigation/ You can use osm.wiki/Relation:connectivity#Examples if needed.

In `=hiking` / `=foot`, it doesn't need to be `name:en=Wilson Trail Section 3 (Lam Tin — Tseng Lan Shue)` either.

As linked, this situation has been specifically called out for how bad it is, in need of a clean up. It should not be encouraged.
https://github.com/osm-search/Nominatim/issues/413
osm.wiki/Homonymous_keys#Incompatible_formats
Besides, `name=` is the common name. In this thinking, you would say eg "KMB Route 89D Towards Wu Kai Sha", as in the bus broadcast. So even if you want to include redundant non-proper-name info, it is debatable whether you need the origin, arrows, and brackets.

Please don't use change `bicycle=` from `=no` to `=use_sidepath` when there is no `=cycleway`. Legally, you are not allowed to bike on sidewalks.

What I do is move this label to `description=` . Use `name=` for company and route number only, similar to the Schedule of Routes. The direction can be obtained in `from=` and `to=`. That's why I add `from:*=` and `to:*=` languages.
In the status quo, it is common to have `name:en=` and `name:zh=`, but not for `from=` and `to=` .
It is very tedious to update routes when you put all the info in `name=` . I said screw it when I have to update Tuen Ma Line and East Rail Line

It just works poorly in long descriptive cases.
6 osm.org/relation/9383262 osm.org/relation/6517616
89D osm.org/relation/16227456
There are 114 `route=bus` with `name=` longer than 100 chars. These 5 exceeds 150 chars.
682C osm.org/relation/1290051 osm.org/relation/1317095
HZMB (because tri-lingual) osm.org/relation/8858065 osm.org/relation/8858068
788 osm.org/relation/10866299 osm.org/relation/10866300