Please don't upload personal edits to a live public database. This is vandalism. I only see you mass deleting features that shouldn't be removed, and you should still change stores to a plain "point" when they change hands..

1. Or you can try to reply, instead of using upload comment as your personal announcements?
2. And why not use `=track` ?
3. `=pedestrian` has been used across HK. Given the lack of `=track` in HK (many existing are also misuse from the "single-track access road term, which should be `=unclassified` , `=residential` , and `=service` ) , it's unclear how it should be used. `=pedestrian` fit the mainly pedestrian use definition, connects between `=service` , and ties with actual park EVA.

Actually it's only the site branch. The office itself is still in the Goverment Office.

It depends on your definition. The magistracy may be only one of the tenants. SWD has a Probation and Community Service Order Office inside. They aren't always inside a court building either.
(Note a court building can also contain multiple different courts and tribunals)

Don't simply combine them. The building and site is really called Tuen Mun Law Court Building.

It was changed away from `=service` for good reasons. `=service` is an internal serving a facility. At most, it's better used for the specific road connecting a facility and the main road. `=pedestrian` means pedestrian is the main user, but `motor_vehicle=` can be allowed in limited capacity. You should only argue about using `=track` road.

A `=service` road has been deleted without even replacing it. Please don't upload incomplete edits.

1. Please don't delete & redraw. This makes tracking changes more difficult. Simply move them to the correct position.
2. You removed the concave part detail on the south side of blocks 2 to 5
3. `=living_street` means a signposted legally pedestrian priority road, not any road

1. You are adding `amenity=police` to the `building=` and `building:part=` ie creating `amenity=fire_station` in every `building=` `building:part=` inside again, not changing what `building=` they are
2. `building=` is a structural form, not only function. `=office` already adequately presents it. There is already a spatial relationship, where you can get all `building=` inside a `amenity=police` area to know they are police buildings. `building=fire_station` is unique and recognizable, with fire trucks below the quarters.
In any case, creating duplicate `amenity=police` station is absolutely wrong. It doesn't solve your problem.

3. Each unit doesn't occupy the entire `building=` or `building:part=` . They shouldn't be added to the entire area.

Please don't apply `building=` to land-only areas

1. Please don't add duplicate `amenity=police` . There should only be 1 for each police station. This is Tagging For Renderer, Application, or Editor.
2. Please don't change `building:part=` to `building=`

Please don't add duplicate `amenity=police`

The problem is they are basically only handling `operator=` now, not `owner=` . So the acceptance is uncertain. OSM is usually quite cautious and suspicious towards `owner=` .
Some people can argue HKHA is the direct `operator=` , with HD behind that should be interpreted from `*:wikidata=` etc if needed. It may also be argued the managing company contracted is the `operator=` . So it's not immediately obvious and straightforward.

Please don't delete things you don't understand yet. They need to be reformed into `building:part=` properly.

That seems to be a misunderstanding. At least in this case, it will only be suggested when the `operator=` contains it. So it's only being formatted.
Ultimately, it's only a suggestion. You are responsible for accepting it. When there's already something better, it should be rejected.

Please don't change Housing Department to HKHA. That's the actual agent, more accurate, and has been used by some.

As mentioned before, please don't blindly add HA as `operator=` of HOS. They are no longer owners after being sold, nor usually the management.

Please don't Edit For Application. It's the responsibility of apps to handle controls, categories, and discoverability.

A related issue is how `name:zh-Hans=`, and `name:zh-Hant=` , etc is often added. That's the amount of permutation/combination on the extra work, for `name:yue-Hant=` etc. So the effect of all these needs to be considered.