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.

If you have checked the usage, `addr:street=` already have a significant number. So don't ask me. https://taginfo.openstreetmap.org/tags/highway=bus_stop#combinations
I don't believe `object:street=` or other existing solutions are better. osm.wiki/Talk:Tag:parking=street_side#Relating_to_street

`place=` is for existing concepts. Please use OpenHistoricalMap for the full history.

`name=` is the most common name in existing public use. Please don't remove other names. Use `alt_name=` etc.

`=village` is used for large ones with their own facilities. Use `=hamlet`, and if only a few houses `=isolated_dwelling`.

Please notice that they represent different things. One is the existing community at the center. The other is a `=locality` for the reclaimed island and cape.

What are you reading?
1. Yes, they are supposed to be on `=ridge`.
2. Yes, they must not be attached to `highway=`

It's very obvious `=path` is not the same as `=ridge`. The middle section deviates significantly.

Upload comments are not for arguing either.

6. You have not asked beforehand though? Simply coming in and deleting everything.

1. Explain how they are wrong? Iterative refinement, mate.
2. Have you read what `=ridge` is for?
3. This is renderer problem then. Complain to them if you want them less visible. Or in your application, reduce their visibility. You are also deleting this for everyone. And , ah yes, you are using "hack tools" too now. iD is also "3rd party" if you claim this way. Are you uploading to the APi directly?
You are committing vandalism by mass deleting while claiming others are graffiti.
5. One Feature One Object. You have not added `=ridge` to `=path` either, which is still wrong. A `=ridge` is more continuous and longer. A `=path` has many attributes that can be split.
6. EDM is not the same as `=ridge`. SRTM is not the most accurate. Moreover, the contour is also generated artificially.

You yourself have attached a `=peak` to `=path`. So I don't know what you are complaining.

1. `=ridge` and `=path` are different things.
2. `=peak` are supposed to be on `=ridge`.