Relation:route_master

From OpenStreetMap Wiki
(Redirected from Tag:type=route master)
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 · Baso Minangkabau · bosanski · brezhoneg · català · čeština · 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 · português do Brasil · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · 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 service
Group: Public transport
Members
  • Relation - (blank)
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 service.

Key Value Comment Recommendation
type route_master Defines the relation as route_master mandatory
route_master train / subway / monorail / tram / bus / trolleybus / aerialway / ferry / bicycle Defines the route_master as train, subway, monorail, tram, bus, trolleybus, aerialway, ferry or bicycle route_master mandatory
ref Reference The reference number by which the service is known recommended
ref:<qualifier> Operator's or network's reference The reference by which the service is known by a specific operator or network recommended if the service changes the reference number when crossing the network's border
name <Vehicle type> <Reference number> Short prose description of route master. <Vehicle type> should be identical to route=*. Example: Bus 201 recommended
operator Operator Name of the company that operates the service recommended if available
network Local / regional network Name of the network the route belongs to recommended if available
colour Colour Route/Service colour (HTML named colour or web colour in hexadecimal format) recommended if available

Members

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

Element Role Recurrence? Description
Relation <empty> Two or more All route variant/directions

Examples

Number Relation Used Tags Description
Bus 201 Relation 1244886 (XML, Potlatch2, iD, JOSM, history, analyze, manage, 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 (XML, Potlatch2, iD, JOSM, history, analyze, manage, 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