Please check that `name:zh=` is the standard used for the text. `name:yue=` is only added when Cantonese info is added.

Besides you haven't added back the roads between containers.

You should keep the container stacking areas as `highway=service` + `area=yes` or something.

* `=service`
As well as `placement=`

Please check that the merge on HZMB already has `lanes=4`. Don't over-extend the `=motorway_link`. It is ugly and unrealistic. Follow the physical separation rule for best results.

Ok to clarify there are difficulties with overlapping `boundary=administrative` at the bridge. It is also not require to have `boundary=` on the lines, especially when there are multiple `boundary=` applicable.

This is not a `=administrative`. It is `=border_area` if anything.

And it's a continuation of the `=primary` Po Shek Rd

(1. So I mean it is still part of the main line of Harcourt Rd, as such should not have `=*_link` used)

(In US terminology, is a form of braided ramps)

1. Please don't use `=*_link` for forks. This is supported by some routers and applications
2. I made this `=primary` as you can technically continue on Harcourt Rd, and as a connection to Cotton Tree Dr. Moreover it is to distinguished between the ground-level `=secondary` section downstream.

I made this `=primary` because it is Castle Peak Rd and Fan Kam Rd combined.

However quite many "non-franchised" bus look similar to "local" buses as well, depending on definition.

It is also unclear how the alternative of `tourist_bus=` and `coach=` should be used.

Please pay attention that Hong Kong strictly differentiates "franchised" (ie local) and "non-franchised" bus. Only certain bus can use these.

Please check that this is an established practice for government facilities admin_level=*#Usage

Usually `sidewalk=left` is added first. Then the `footway=sidewalk` is drawn later. So yes, but you should ensure all `=footway` in the vicinity have been connected properly for the separate network to work around the segment. Otherwise it's meaningless and misleading.

2. Searching for the `=stop_position` won't always work either. And that's even proposed to be left out by some.

2. You have to rely on the `=stop_area` which is not always created for every one. And it's less straightforward to process. As I have discussed elsewhere, there is a non-ignorable need for this across different features.

1. And `object:street=` doesn't appear at all.
2. It's not here, and can be uncertainty in many cases. How do you know it is for the `=primary` here, not the `=residential`?
The other purpose I'm looking into is associating it with the CA07-N prefix on this direction.