Changeset: 92985365
R4 road lanes
Closed by Kovoschiz
Tags
created_by | JOSM/1.5 (17084 en) |
---|
Discussion
-
Comment from 小智智
Please don't add invalid tags into bus routes.
There is no "brand" for routes 960X / 968X. (It does exist for Cityflyer routes or H1 / H2)
The designation should follow the schedule of routes order, i.e. "過海路線 Cross Harbour Route".
The network should have the same value as other routes in the area e.g. 960, 961, 962, 967, 968, 969, etc. because all these routes form a network. It is necessary that "network - ref" can identify the route.
"owner" and "ownership" are also invalid here. A bus route is not something which can be legally owned. It is only "franchised".
"passenger" is also invalid here as it is not a railway or train / ferry route. A bus route by its definition carries passengers.
"usage" is also invalid here. It is not a railway track.
-
Comment from Kovoschiz
1. `brand=` is for the brand it is carrying. `operator=` or `netowkr=` isn't exactly the same as `brand=`
2. "Special Departure Route" is used.
3. `network=` isn't used for that. Some other tags could be used, including the legal `designation=` that could be applicable here. And there are obviously a lot of varieties of usage in practice here.
4. This is same as the difference between track and train ownership on railways. A bus route could also be contracted out.
5. `passenger=` denotes the kind of passenger service it is. `railway:traffic_mode=passenger` is used for what you have in mind.
6. There are 1k usage of `usage=` on relations. `service=` has been suggested on routes, where they can likely be used together. -
Comment from Kovoschiz
For example, how would you tag MTR Bus and MTR Feeder Bus?
-
Comment from 小智智
type=route
route=bus
ref=K58
network="港鐵巴士 MTR Bus"
operator="香港鐵路有限公司 MTR Corporation" -
Comment from 小智智
The network tag here is debatable. Theoretically we should consider each franchise a network, but using this reasoning fails for jointly-operated routes.
-
Comment from Kovoschiz
1. This fails to reflect that it is integrated in the PT network of MTR.
2. I don't see how it "fails". They are simply only partially integrated. -
Comment from 小智智
1. The MTR Bus (港鐵巴士) routes are a separate network. They are not part of the MTR (港鐵). The MTR operates the following networks of routes:
- MTR
- Light Rail
- MTR Bus
- MTR Feeder Bus
- Ngong Ping 360
- High-speed rail
etc.2. What do you mean by partially integrated? For example, if I use S1 as the example, and consider each franchise a network, it belongs to both LWB franchise network and CTB franchise 2 network. The "network" tag clearly can't cater for this situation.
-
Comment from Kovoschiz
1. You are conflating system/mode and service. MTR, Light Rail, MTR Bus, and MTR Feeder Bus can be considered in the same "network". This is similar to considering transit agencies as a "network".
2. Again, what's the issue with a partially-integrated route in a network? -
Comment from Kovoschiz
2. You could even say it's not in any "network", for this example
-
Comment from 小智智
1. They are clearly not the same network according to the official usage. They are always listed out separately as MTR Bus, Light Rail, MTR, etc separately. Each of these are governed by different regulations. All these networks combined are called "綜合港鐵系統 Integrated MTR system".
Adding salt to the insult we may even consider the "Airport Express" in different network than the rest of MTR as well
-
Comment from Kovoschiz
1. That's what the `brand=` could be for.
-
Comment from Kovoschiz
2. Yet again, it's a matter of degree and considerations. Rail-side-wise, Airport Express is obviously in the same "network"; PT-service-wise, your raised a good question, but yet again I don't find partial integration to be an issue denying consideration as one "network".
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275798), v1
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275799), v1
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275800), v1
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275801), v1
- 863275802, v1
- 863275803, v1
- 中環及灣仔繞道隧道 Central–Wan Chai Bypass Tunnel (863275804), v1
- 中環及灣仔繞道隧道 Central–Wan Chai Bypass Tunnel (863275805), v1
- 4 (863275806), v1
- 863275807, v1
- 863275808, v1
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275809), v1
- 中環及灣仔繞道 Central–Wan Chai Bypass (863275810), v1
- 林士街天橋 Rumsey Street Flyover (32551402), v37
- 84759511, v15
- 林士街天橋 Rumsey Street Flyover (89141630), v23
- 林士街天橋 Rumsey Street Flyover (89319626), v21
- 干諾道西天橋 Connaught Road West flyover (89319633), v12
- 干諾道西天橋 Connaught Road West flyover (89319640), v14
- 干諾道西天橋 Connaught Road West flyover (89319645), v17
Relations (12)
- 11788888, v1
- 11788889, v1
- 九巴968X線(元朗(西) → 鰂魚涌) KMB Route 968X (Yuen Long (West) → Quarry Bay (King's Road)) (3930928), v64
- 四號幹線(東行) Route 4 (Eastbound) (6495846), v28
- 四號幹線(西行) Route 4 (Westbound) (6495894), v19
- 九巴960X線 KMB Route 960X (洪水橋(洪元路) Hung Shui Kiu (Hung Yuen Road) → 鰂魚涌 Quarry Bay) (6646336), v64
- 過海隧巴962C線 Cross-harbour Bus 962C (龍門居 Lung Mun Oasis → 鰂魚涌 Quarry Bay) (6889899), v50
- 過海隧巴962C線 Cross-harbour Bus 962C (三聖 Sam Shing → 鰂魚涌 Quarry Bay) (8704273), v25
- 10623688, v2
- 10623689, v2
- 新巴88X線 NWFB 88X (堅尼地城(卑路乍灣) Kennedy Town (Belcher Bay) → 小西灣(藍灣半島) Siu Sai Wan (Island Resort)) (10866547), v8
- 新巴33X線 NWFB Route 33X (數碼港 Cyberport → 西灣河 Sai Wan Ho) (11732982), v3
Nodes (1-20 of 36)
- 1
- 2
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |