Id:Bus

Artikel ini merupakan terjemahan yang belum lengkap: artikel ini berisi kelalaian, kesalahan yang belum diperbaiki, atau beberapa bagian yang belum diterjemahkan.
Jika Anda memahami terjemahan asli dalam bahasa Inggris, mohon bantu menyelesaikan terjemahan bahasa Indonesia ini. Baca petunjuk tentang cara menerjemahkan wiki ini.
Sepertinya tidak ada yang mengerjakannya saat ini, jadi Anda dapat mengerjakannya.

Fitur: Bus

Deskripsi

Bentuk angkutan umum

Tag

Contoh relasi: rute bus 36052(ditandai dengan warna biru) di mana semua halte bus bukan merupakan bagian dari jalan, melainkan di samping jalan. Rute bus ini berada di dalam London dan nomor rutenya adalah 12.

Bus kota, bus antarkota, dan bus troli (trolleybus) adalah bentuk angkutan umum yang beroperasi terutama di jaringan jalan. Sistem ini terdiri dari rute-rute bus yang berhenti di halte dan stasiun bus, serta memiliki sejumlah fitur terkait.

Halte dan stasiun/terminal bas

Halte bus

The common way to map bus stops is using a node with highway=bus_stop beside the highway at the point where passengers would wait immediately prior to boarding the vehicle. This may be in a suitably positioned bus shelter, or by the bus stop pole. It might be a few meters from the point where one enters the vehicle. Add the name of the stop (as it appears on the stop, or on a timetable) using name=*. Many mappers also add public_transport=platform, which can also be used for all types of public transport.

Stasiun/terminal bus

Terminal atau stasiun bus direpresentasikan dengan menggunakan node atau area yang diberi tag amenity=bus_station . Seseorang juga dapat menambahkan public_transport=station . Beberapa pemeta menambahkan bus=yes jika mereka menggunakan public_transport=station saja.

Rute bus

Layanan bus dipetakan dengan menandai elemen-elemen yang termasuk dalam suatu rute sebagai anggota suatu relasi. Ini termasuk:

• halte (highway=bus_stop) dan posisi perhentian (public_transport=stop_position)
• segmen jalan (garis) yang bus dilalui pada rute.

Gunakan satu relasi per arah (juga disebut varian) dari rute layanan, ditandai dengan type=route+route=bus/route=trolleybus.

Relasi master rute

Untuk menyimpan relasi varian rute bus bersama-sama, relasi lain digunakan: type=route_master+route_master=bus/route_master=trolleybus.

Öpnvkarte.de (atau openbusmap.org) menunjukkan rute bus, serta rute kereta api dan trem e.g. di Cologne

Untuk mengidentifikasi layanan bus sebagai bagian dari jaringan bus, gunakan tag operator=* dan network=*.

Jalur bus dan jalan khusus bus

Artikel utama: Id:Jalur bus

Bus umumnya beroperasi di highway=*, tetapi terkadang bus juga menggunakan infrastruktur yang dikhususkan untuk bus.

Terdapat dua skema yang umum digunakan di OpenStreetMap untuk merepresentasikan jalur bus di jalan biasa: skema busway=* (atau bus_bay=*) yang menunjukkan keberadaan setidaknya satu jalur bus (atau ruang) di satu atau lebih "sisi" jalan, dan skema lanes:psv yang menyediakan jumlah jalur yang diperuntukkan bagi "kendaraan layanan umum" (termasuk bus) dan "arahnya". Kedua skema ini kompatibel dengan jalur sepeda. Keduanya dapat digunakan secara bersamaan; untuk informasi lebih lanjut, lihat jalur bus.

Dua skema yang umum digunakan sudah cukup untuk sebagian besar peta. Namun, informasi khusus jalur yang berlaku untuk jalur bus juga dapat diperoleh dengan akhiran :lanes yang canggih.

Sebaiknya sediakan tag access=* dan maxheight=* untuk jalur yang mencakup jalur bus, jika memungkinkan. Untuk bus troli, kabel harus disertakan dengan trolley_wire=yes.

Untuk jalan khusus bus terpisah, gunakan highway=busway. Contoh

Menambahkan rute bus ke OpenStreetMap

Langkah 1 - Tambahkan halte bus ke OpenStreetMap

Demi kesederhanaan dan kemudahan, halte bus sebaiknya ditambahkan sebagai simpul di lokasi rambu atau halte. Beberapa halte telah ditambahkan sebagai jalur atau poligon, yang sepenuhnya valid. Namun, menambahkan halte sebagai simpul akan membuat rute lebih rapi dan mudah dirawat.

Beberapa pemeta menggunakan simpul posisi perhentian di jalur yang dilalui rute, serta menggunakan simpul di pinggir jalan. Penggunaan simpul public_transport=stop_position di jalan dapat bermanfaat dalam beberapa kasus yang jarang terjadi, tetapi biasanya tidak diperlukan. Cara sederhana dan dianjurkan untuk menambahkan halte bus adalah sebagai simpul di lokasi tiang atau halte.

Jika terdapat beberapa halte yang merupakan bagian dari stasiun yang sama, relasi area halte harus digunakan untuk menunjukkan bahwa semua halte tersebut merupakan bagian dari stasiun yang sama. Hanya halte individual, dan bukan relasi area halte, yang harus ditambahkan ke rute bus.

Tambahkan tag berikut ke halte bus: Template:Id:Template:Map Features:Bus Stop

Setelah memastikan setiap halte bus ada di peta, lanjutkan ke langkah 2.

Langkah 2 - Membuat relasi rute bus baru

According to the PTv2 schema, one relation must be created for each variation of the route. For example, a bus route with both Northbound and Southbound buses should be mapped as two separate relations. If the bus route is a loop, only one relation is needed. If the bus route has some buses that start out half way through, serving only the second half of the route, but following the same route as other buses, a separate relation is needed for that variation.

To create the bus route relation for one of the directions the bus travels, select the first stop that the bus stops at and create a new relation from it.

To create a bus route for the weekend/weekday variation of the route, use the opening_hours=* key to differentiate between the variations.

Add the following tags to the new relation:

Tag	Kepentingan	Deskripsi	Contoh
type=route	Mandatory	Menunjukkan bahwa relasi tersebut adalah rute.	type=route
route=bus	Wajib	Menunjukkan bahwa rute tersebut adalah rute bus	route=bus
ref=*	Lebih penting	Menunjukkan kode referensi atau nomor referensi rute. Jika tidak ada, tag nama=* diperlukan. Rute bus harus memiliki pengenal tertentu agar berguna.	ref=29C
public_transport:version=2	Penting	Tag ini berguna bagi pengguna data transport OSM karena memberi tahu mereka bahwa rute telah ditambahkan sesuai dengan sistem baru PTv2. Hal ini memudahkan penguraian dan validasi.	public_transport:version=2
operator=*	Disarankan	Nama operator rute.	operator=Dinas Perhubungan Kota
network=*	Disarankan	Jaringan rute bus. This can either be an abbreviation or full name, depending on the network. Check other bus routes or bus stops near the one being mapped to find out how the network should be tagged in your area.	network=CHT, network=London Buses, network=NYC Buses, and network=TNSW
opening_hours=*	Recommended	The opening hours of the bus route. Use this tag for differentiating between a weekend and weekday routes. This should include the time between the first bus of the day starting out (in the direction being mapped - different directions can have different opening hours) to the time of the last bus of the day arriving at the last stop of the route.	opening_hours=Mo-Fr 07:23-18:44
interval=*	Recommended	The time between arrivals at any given stop along the route. Also known as the service frequency. Use HH:MM:SS, H:MM:SS, HH:MM, H:MM, MM, or M format. The example on the right is for a bus route that operates every 6.5 minutes.	interval=00:06:30
duration=*	Recommended	The duration of the bus route, or the time between the bus leaving the first stop and arriving at the last stop. The example on the right states that the bus runs for 31 minutes from end to end. Use HH:MM:SS, H:MM:SS, HH:MM, H:MM, MM, or M format.	duration=00:31
fee=*	Disarankan	'yes', jika ongkos diperlukan untuk menaiki bus pada rute tersebut, dan charge=* opsional (tetapi tetap penting) untuk jumlah biayanya. 'tidak', jika tidak ada ongkos yang diperlukan.	fee=yes+charge=2000 IDR/km
bicycle=*	Disarankan	'yes' jika sepeda diperbolehkan di dalam bus. Bus yang memperbolehkan sepeda sering kali memiliki rak di bagian depan untuk menyimpannya.	bicycle=yes
wheelchair=*	Recommended	'yes' if wheelchairs are accommodated. 'no' if not. Routes that accommodate wheelchairs have special ramps that can be laid down for wheelchairs to enter the bus. There will be a dedicated area in the bus for wheelchairs that may have straps or a cushioned pad that the wheelchair can the reversed up to and the brakes applied to hold a wheelchair in place.	wheelchair=yes
from=*	Recommended	The name of the location where the bus is coming from. This does not have to be the name of the bus stop.	from=Southern Village
via=*	Recommended	The name of an important stop along the route (for example, the turning point of a loop line). Many bus routes do not have an important via stop, so in the case of trying to add such a route, don't use this tag.	via=Franklin Street
to=*	Recommended	The name of the destination of the bus. Many buses display a banner across the top of the bus with the destination.	to=Eubanks Road Park and Ride Lot
name=*	Recommended	Artikel atau bagian ini mengandung informasi yang dipertanyakan atau kontroversial. Lihat halaman diskusi untuk informasi selengkapnya. Descriptive naming is generally frowned upon. This recommendation has attracted criticism many times over the years. The 'name' of a bus route should follow a specific format and is not the official name of the bus route. This tag is more of a description of the route than the actual name of the route. To add the name, use the following format: "name"="Bus <ref>: <from> => <to>". If the bus route has a "via", you can use "name"="Bus <ref>: <from> => <via> => <to>", however using via in the name is optional. Note that "->", "-->", or "→" can be used instead of "=>". Use which ever style you like. As long as the ref=*, from=*, and to=* tags are filled out, data users can create their own names however they prefer. If the bus route is a round trip, the "to" and "from" tags will be the same, causing a rather silly bus route name to be tagged (eg. Bus 27B: Downtown => Brightley => Downtown). In the case of such a bus route, you can choose to use "Bus <ref>" as the name. Example: name=Bus 27B.	name=Bus 405: UNC Hospitals => Downtown Durham Transit Center
official_name=*	Recommended	For describing the name of the bus route as used on official maps. Most routes have only a reference number and not a name, so for those cases, don't use this tag.	official_name=Bull City Connector
colour=*	Recommended	The colour of the bus route on official maps. Many bus routes do not have an "official colour", so for those routes, simply don't use this tag. The colour should be in hex format, however, using HTML colour codes will work as well. Note that the British English word "colour" is used for this key rather than the American English "color".	colour=#58912F
roundtrip=*	Optional	To specify whether the relation is a round trip. For most routes, the value is 'no'. Routes that complete a loop and are therefore only added with one relation should have the value 'yes'. This is optional because it can be inferred from the relation itself.	roundtrip=no

Menambahkan halte bus ke relasi

The next step is to add each bus stop to the bus route relation in the correct order with the role "platform". If both public_transport=platform and public_transport=stop_position as a connected relation were used for a bus stop, just add the platform node to the relation.

To add a bus stop to the route, select that bus stop (platform), and then click the plus symbol near the bottom under All relations. Then, choose the relation that you have just created, add the stop to the relation, and set the role to platform.

It is very important that the stops be added to the route relation in the order that the bus stops at them. If the bus stops at a stop twice, add that stop to the relation twice. Each stop must have the role "platform" in the route relation. Although many people use the role "stop" for the bus stops, the role is now discouraged. Use "stop" for stop positions instead.

If the stops or roads have been added in the wrong order, they can be dragged and dropped into the correct order.

Some platforms / bus stops have entry only/exit only restrictions. For those cases, use the roles "platform_exit_only" and "platform_entry_only" instead of the role "platform" (resp. "stop_exit_only" and "stop_entry_only" for "stop").

Menambahkan jalan-jalan ke relasi

The final step is to add the streets covered by the bus route in the correct order with empty role "".

Many data consumers, including OsmAnd, are able to use bus routes without any streets added to the relation - only stops. Adding the streets is recommended, but not mandatory.

To add streets to the relation properly, select the first street that the bus drives over after leaving the first stop in the route. You may need to split the street to only select the part of it that is covered by the bus route. Add the first street covered by the bus route to the relation with an empty role. Then, add the next street covered by the route, and then the next, in order as for the stops. Using the roles "forward", "backward", "both", "North", "South", "twice", or any other role is not supported in the original PTv2 proposal. Each street must be added with an empty role ("") except for sections of the route where one can board or leave the bus at any point along the road by giving a sign to the driver instead of waiting for the next stop which can be marked with hail_and_ride. For PTv2 routes the direction that the bus travels on the way can very easily be found by a computer (if there are no gaps), and using roles other than an empty role for streets covered by the bus route is usually redundant.

The relation is now finished.

Langkah 3 - Membuat relasi master rute

No route master relation is needed if the bus route is a loop, and therefore only mapped with one relation (and given the tag roundtrip=yes).

Route master relations represent all variations of a single bus route, not a network of bus routes.

Now that each direction of the bus route has been added as a separate relation, they should be connected with a route master relation. The route master relation should include both directions of the route, as well as any variations of the route. For example, if a bus route operates normally Monday through Friday, but has a different route and different opening hours on weekends, then the weekend routes (both directions) should be added as separate relations, for a total of four relations. All relations that are part of the same route should be added to the route master relation.

Tambahkan tag berikut ke relasi master rute:

Tag	Kepentingan	Deskripsi	Contoh
type=route_master	Mandatory	To specify that this relation is a route master.	type=route_master
route_master=bus	Mandatory	To specify that this route master is a bus route master.	route_master=bus
ref=*	Mandatory	If no ref exists, you must use official_name=* instead.	ref=800
name=*	Recommended	Artikel atau bagian ini mengandung informasi yang dipertanyakan atau kontroversial. Lihat halaman diskusi untuk informasi selengkapnya. Descriptive naming is generally frowned upon. This recommendation has attracted criticism many times over the years. As is true with the individual bus relations, this value should not be the "official" name of the bus route. Use the following format: "Bus <ref>".	name=Bus 800
operator=*	Recommended	Name of the company that operates this bus route.	operator=Transport for London
network=*	Recommended	The network of the bus route master. Look to other public transport features in your area to see what the common value of the network=* tag is for your local transit network.	network=London Buses
wheelchair=*	Recommended	'yes' if wheelchairs are accommodated. 'no' if not. Routes that accommodate wheelchairs have special ramps that can be laid down for wheelchairs to enter the bus. There will be a dedicated area in the bus for wheelchairs that may have straps or a cushioned pad that the wheelchair can the reversed up to and the brakes applied to hold a wheelchair in place.	wheelchair=yes
bicycle=*	Recommended	'yes' if bicycles are permitted on the bus. Buses that permit bicycles often have racks on the front for storing them.	bicycle=yes
official_name=*	Recommended, if one exists.	For the name of the bus route as it appears on official maps. If no official name exists, don't use this tag.	official_name=Bull City Connector
ref:<qualifier>=*	Important, if several refs exist.	The reference by which an operator or network, specified by <qualifier>, refers to the route or service. Important, where the reference code of the bus route is known by two or more different refs depending on which operator is contacted.	ref:OPT=OCH & ref:TTA=420

Add the child bus route relations to the route master.

After adding the necessary tags to the route master relation, add each of the individual routes to the route master with an empty role, or ("").

Relasi jaringan

Artikel utama: Relation:network#Public transportation networks

A network relation can be used to link each member of a network together. The network relation represents existing networks (i.e. a common fare system). Network relations can be hard to work with, and have therefore been deprecated in some places (for example Germany). Using network=* on each bus route and route master relation is preferred over network relations.

Contoh rute bus

London Buses route 12: route master relation

Menghapus rute bus dari OpenStreetMap

Ketika seluruh baris menghilang, relasi route_master dan rutenya dihapus. Kecuali halte bus juga telah dihapus secara fisik, halte tersebut tidak boleh dihapus. Jika halte tersebut diganti namanya dan/atau pengenalnya berubah dan jelas bahwa semuanya didasarkan pada pendahulu yang telah dipetakan, Anda dapat 'menggunakan kembali' relasi tersebut. Tidak ada cara yang baik untuk menunjukkan kapan situasi baru dimulai atau situasi lama berakhir.

Peta bus

Situs berikut merender rute bus (berdasarkan data relasi).

• Öpnvkarte (http://öpnvkarte.de/ atau alternatifnya http://www.openbusmap.org/ atau OSM Inspector Public Transport - Network) Peta angkutan umum di seluruh dunia.
• Transport Map: Lapisan dibuat oleh Andy Allan yang menunjukkan rute angkutan umum di seluruh dunia. Halaman wiki
• Permintaan Overpass Turbo:
  • Mempertimbangkan warna lin rute, dan tidak merender rute tanpa warna
  • Tanpa memperhitungkan warna, menampilkan semua rute dan halte
• Peta rute Overpass API: http://overpass-api.de/public_transport.html
• OrganicMaps: mendukung navigasi bus di beberapa wilayah.

Rute bus menurut negara

Lihat Category:Bus routes by country.

Lihat juga Category:Public transport by country.

Lihat juga

• Angkutan umum
• Tag:route=bus
• Relatify (editor rute bus)
• Bus Rapid Transit

Usulan

• Proposed features/Public Transport (PTv2) - diterima, sedang digunakan.
• Usulan hail_and_ride - disetujui