Relation:route_master

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Relation:route master
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Basa Sunda · Baso Minangkabau · bosanski · brezhoneg · català · čeština · corsu · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tagalog · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · भोजपुरी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ ⵜⴰⵏⴰⵡⴰⵢⵜ‎ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
Public-images-osm logo.svg route_master
Osm element relation.svg
Description
Contains all direction/variant routes of a public transport line
Group: Public transport
Members
Useful combination
Wikidata
Status: approvedPage for proposal

Relations of type route_master contain all the direction and variant routes and the information that belongs to the whole service.

A route/service is represented by vehicles that always run the same way with the same reference number. Each direction of a route should be tagged as a separate relation. If a route has several variants (e.g. different way at weekend), these variants should also be in separate relations.

Tags

A route master contains all the important information that belongs to the line.

Key Value Comment Recommendation
type route_master Declares relation to be a route_master. ! Required
route_master aerialway / bicycle / bus / ferry / monorail / subway / train / tram / trolleybus Defines the route_master as train, subway, monorail, tram, bus, trolleybus, aerialway, ferry or bicycle route_master. ! Required
ref Reference as text. The reference by which the service or route is known. ! Required
ref:<qualifier> <qualifier> is a name as text.

The value is the reference as text.

The reference by which an operator or network, specified by <qualifier>, refers to the route or service.  Important, where the service changes the reference number when crossing the network's border.
name <vehicle type> <reference number> as text. Short prose description of route master. <vehicle type> should be as in route_master=*. For example, Bus 201.  Important
operator Operator's name as text. Name of the entity that operates the service. ! Required, where available.
network Network name as text. Name of the local or regional network to which the route belongs. ! Required, where available.
colour CSS colour name, or #<red><green><blue>, each component 2 hexadecimal digits. Colour by which the route or service is identified on signage, maps, etc.  Important, where available.

Other useful tags

NB: These tags can belong to the route_master relation and/or its route relations. To ease maintenance, please avoid duplication if you can.

Key Value Comment Recommendation
tourism yes / only If it is a touristic service.  Important, where appropriate.
school yes / only If it is a scholar service.  Important, where appropriate.
wheelchair yes / no / limited  Important
opening_hours The service hours of the line. ? Optional

Only for public transport route_master.

Members

All the variants/directions of a route/service are members of this master relation.

Element Role Recurrence? Description
Relation <empty> ! 1; at least 2, usually. All route variant/directions.

Examples

Number Relation Tags Description
Bus 201 Relation 1244886 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Relation type=route_master + route_master=bus

Relation type=route + route=bus

Bus route with route master. One way has simple course, the other way has two variants.
Bus 221 Relation 1342798 (iD, JOSM, Potlatch2, history, analyze, manage, XML, GPX) Relation type=route_master + route_master=bus

Relation type=route + route=bus

Bus with ring route. Initial stop and terminal stop is identical, so from=* and to=* is identical. This route has two variants.

See also