1. Changing `=stop_position` to `=platform` doesn't make sense. The former is located on the carriageway, the latter on the walkway.
2. Use `route_ref=`. `ref=` is for the bus stop itself.

`building=public` or similar is discouraged for their ambiguity. It could mean `ownership=`, or conflict with `building=office` for government offices. Personally I use `building=civic` for these, although this may similarly be questioned.

Don't be overly bothered by "dumb" validators complaining about no connections.

`bus=yes` is for the `public_transport=platform`. It's commonly thought `highway=footway` shouldn't used on `railway=platform` et al. Although, `highway=platform` isn't widely used locally, it should be considered.

It's preferable to use `was:name=`. `old_name=` implies TGT Hong Kong Data Centre 2 changed its name from Varitronix Limited, while it's actually repurposed.

Connecting them together degrades, rather than improve the data quality. Orthogonalize them and move them as needed instead.

On another side note, `description:en=` is always available.

On a minor note, abbreviations shouldn't be used in general..

changeset/94740151

changeset/94740151

Also, what's wrong with way/796387354/ ?

Please don't remove `building=` when you add `amenity=parking`. I suppose it's also `parking=multi-storey`, not `parking=underground`. Functionally, the facilities above can get `layer=1` and appropriate `level=` (best to add the whole `building:levels=`); descriptively `location=rooftop` can be added.

changeset/94740151

1. Please put the route to `route_ref=`, if you arent creating a `route=bus` relation yet.
2. Please don't put its heading in `name=`. This is for the bus stop's name, viz DB Plaza here. If the bus stops are coded in this bus terminus, that can be put into `loc_ref=`. I'm not sure if it's acceptable to put `to=` on a bus stop.

@sanctificatione Use JOSM's "upload selected" feature
---

Published using OSMCha: https://osmcha.org/changesets/94527517

This is debatable. I use the criteria of common usage when deciding whether `name=` should be the structure name, or the street name.
At the very least, don't remove the street name.

This is mainly not your fault. The iD editor software preset has to change the entire feature to a `barrier=wall`, removing other tags; plus adding `area=yes` for its object handling, meaning this is now one big block of wall. The most ideal method is to draw a new line along the perimeter for it to be the wall.

It was seen as acceptable to add street info to sidewalks. Please message at Discord https://discord.gg/P8fxC98.

Use `leisure=dog_park` directly, and don't use `name=` for generic descriptors.

You would want to fix how this building is modeled before detailing it as so
---

Published using OSMCha: https://osmcha.org/changesets/94358720