This is what another contributor said after I shared this changeset on Discord: "Just bc you can't find it among the first 5 google results doesn't mean it doesn't exist"

Admittedly that's guy's rather rude, but I suppose you have surveyed the area to come to this conclusion?

FYI, this change caused all bus routes using Tsing Sha Highway northbound become out of order

Please feel free to join the discussion at osm.wiki/Talk:Hong_Kong/Transport/Public_transport if you have time

My apologies for bothering you again.

1. Please add the tag public_transport:version=2 to all bus routes you add.

2. I personally do not agree with what the wiki says about network (it seems to be written arbitrarily), but admittedly we do not have a consensus on how it should be defined yet. Seeing how it's being used in other places, I suggest keeping the value as simple as possible for the time being. Therefore maybe just add network=KMB and network:wikidata=Q312243 for KMB routes, and network=CTB and network:wikidata=Q5124055 for Citybus routes. (I also use network=Cityflyer and network:wikidata=Q5124066 for A-prefixed Citybus routes)

FYI, I have reversed the two Boundary Street nodes and adjusted the Lancashire Road one.

One last thing: If you find iD (or any other editor in this sense) responds to your dragging or other operations incorrectly, undo and try again.

Scissoring a way is mostly OK if I remember correctly, although it might mess up a circular route including the said way (I also suspect this is only an issue if one scissors a bi-directional way).

Specifically for this change, the new nodes are more of a problem. From my experience using iD, it sometimes makes new nodes when we actually intend to drag a way or an area, and its interface does not always display such changes obviously.

Hi Sam, just curious, I found a fair number of your changes involving a new, blank node storing all KMB route relations, away from their original stops. Is there any reasons that it is so?

That very much suggests StreetComplete is a flawed if not bad editing tool. Any ways to place a complaint on its (apparently buggy) behavior?

Hi, what bug did you fix?

Please keep your changes to one per country at most.

You can use this tool to check if routes break after you do edits:

https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=114.20806&lat=22.32860&zoom=16

Hi, I am afraid some of your edits have broken some existing routes and / or bus stops. For example this one breaks KMB 5D.

Please be noted that iD is not the best tool to edit bus routes. I learned it the hard way.

`stop_area` is, as you noticed, a compromise as a result of the above problems. But arguably I am mapping for the renderer here -- I found one of the (unintended) results is that routes look better on OSMTransportViewer.

Meanwhile, I found `stop_area` primiarily as a way to group stops described in the same hkbus Fandom page, and I found kicking the `ref:hkbus`=* tag to the relation improves the structure (to me). That said, I do not intend to treat the hkbus Fandom as 100% accurate.

I am unsure about how close we should follow the official stop names.

The simplest way is to follow whatever shown on the bus stop post (I believe mapping means putting something actually sitting there on the map). However this leads to awkward situations where companies give different stop names at the same location (it's even more complicated when we take in minibus stops -- most of them don't have names at all). Chung Wui Street is not the worst case already. At Ma Tau Wai Estate (at the north end of Ma Tau Wai Road and the subsequent section of Ma Tau Chung Road), Citybus effectively treats the northbound stops as one group but KMB names them in two. *That's* really tedious.

And of course I am, like many others, disgusted by the recent "Interchange" stuff introduced by KMB. On a more "practical" note, I believe it would go sooner or later.

Two more things.
1. "name" of all objects in Hong Kong should be bilingual, unless you cannot find the name in one of the languages.
2. "forward" and "backward" should be with respect to the way. The way iD shows direction is misleading -- we should follow the *opposite* its "shadow" shows us.

Route relations should have their members ordered in a specific way. Also, ways being visited twice or more should be included multiple times.

Yes, it's tedious, which is why iD is not a good tool to add bus routes.

route=bus

iD is sometimes misleading. I have reverted them.

The change is deliberately minimal (i.e. no new ways, bus stop positions, etc. other than whatever route is to be drawn) because the place is subject to reconstruction in the foreseeable future.

The three nodes are so far apart that you should have do this in three separate changes.