Super-Relation
• 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 • norsk nynorsk • occitan • Oromoo • oʻzbekcha/ўзбекча • Plattdüütsch • polski • português • 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 • беларуская • български • қазақша • македонски • монгол • русский • тоҷикӣ • українська • Ελληνικά • Հայերեն • ქართული • नेपाली • मराठी • हिन्दी • অসমীয়া • বাংলা • ਪੰਜਾਬੀ • ગુજરાતી • ଓଡ଼ିଆ • தமிழ் • తెలుగు • ಕನ್ನಡ • മലയാളം • සිංහල • ไทย • မြန်မာဘာသာ • ລາວ • ភាសាខ្មែរ • ⵜⴰⵎⴰⵣⵉⵖⵜ • አማርኛ • 한국어 • 日本語 • 中文（简体） • 吴语 • 粵語 • 中文（繁體） • ייִדיש • עברית • اردو • العربية • پښتو • سنڌي • فارسی • ދިވެހިބަސް
Other languages — Help us translate this wiki
A super-relation is a relation that contains other relations. Relations have initially been created to contain nodes, ways or areas and combinations thereof.
A super-relation is referred to as a 'parent' in Osmosis. The hierarchical structure of super- and sub-relations is also called a 'nested relation'.
Usage
Nested relations are virtually undocumented and rarely used but still there is an effort to process them.
- Routes, especially national and international cycling and hiking routes should be rendered by Waymarked Trails
- Routes, general? by the OSM Route Manager
- boundaries are used to build a hierarchy tree by Boundaries.pl
An example of a super-relation is the Great Lakes 1124369
1124369. It contains five members for each of the five lakes. Each member is itself a relation.
See also
- Pros and cons of nested route relations: Relation:route#Creating super-relations for routes
- Implementation: Super-Relation/Implementation
