Please don't delete directly, as this contains an address, and represents a shop space for tracking and updating. Change it a plain "point", or "vacant shop".

2. Please don't move unrelated features to a `=footway` . That's not realistic, and makes editing more difficult.

Please don't delete `shop=vacant` . Its purpose is exactly to record a shop space for tracking and updating later.

The `=no_left_turn` was wrongly set as `=only_left_turn`

`=private` means individually allowed. which is not the case here. Events accept anyone willing to pay (`=yes`) , so should be `=customers`

There are 2 `architect=` here, one without Wikidata. Emptiness is the standard format for indicating absence in such text.

As said many times, please don't make random edits especially deletions to attempt to fix a software issue. You should investigate the software, not fiddle with the data.

Please don't directly delete them, as they still represent a shop space. It makes tracking and updating them more difficult. Others may contain addresses and other info. They should be changed to a plain "point", or "vacant shop".

Refuge islands should not be changed to `=crossing` osm.wiki/Tag:footway=traffic_island

Please don't use brackets. `name=` is for proper names only, not a descriptor label. This is a digital map database, not personal or printed paper map.

1. The roads are kept because the ingress and egress will be the same. I don't know if the bus terminal will be changed to sawtooth layout, but parallel stands seem likely for this small size of intermediate stops.
2. The `addr:housenumber=` should be kept as they still exist, and would be reused somehow
3. It's usually not a good idea to draw the exact layout of the construction site in the status you find now, as OSM is not about recording construction progress. There will only be one continuous site with 2 towers, the Low Block extending from Kwun Tong Rd to Fuk Ning Rd

(Fixed)

Please be careful of the preset meanings. This is not an entire `building=`

I would think `*:conditional=* @ (obstruction)` is conceptually better reserved for signs saying you are automatically legally allowed to do something when there are crashes.

1. Even if I don't use `*:variable:values=`, `shoulder:variable=` and `lanes:variable=` are more accurate and consistent for "exceptionally in cases like accidents or breakdowns, on occasional traffic peaks (few days of year only, for example start or end of school holidays), road works or other traffic obstructions ahead. "
It seems static vs dynamic values isn't the reason of `*:variable=` , as discussions has mentioned the existence of boards that can only show one other speed. But they would still be considered `maxspeed:variable=` now. osm.wiki/Proposal_talk:Dynamic_maxspeed#Active_traffic_management_vs._LED_road_signs
For reference, the `*:condiitonal=` `wind_speed` restrictions always happen.

1. I have read somewhere that `*:conditional=` is considered inappropriate as compared to `*:variable=` , because it's not always active even when there are `obstruction` . It will only be in effect when the staff judge it's needed.
2. No, it's only a pilot project to have optional hard shoulder running if there are crashes

`=wastewater_plant` is for treatment plants only. This is `=pumping_station`

Please don't add short-term temporary events. They don't belong in OSM.

`service=driveway` is not used for roads connecting carparks. Only `=service`

There's no wall here. Only a cut rock face.