Relation:building

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Relation:building
· Afrikaans · Alemannisch · aragonés · asturianu · Aymar aru · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · bamanankan · 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î · Latina · latviešu · Lëtzebuergesch · lietuvių · Limburgs · 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 · Tagalog · Tiếng Việt · Türkçe · Türkmençe · Vahcuengh · vèneto · walon · Wolof · Yorùbá · Zazaki · isiZulu · српски / srpski · авар · Аҧсшәа · башҡортса · беларуская · български · қазақша · Кыргызча · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · भोजपुरी · मराठी · संस्कृतम् · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · བོད་ཡིག · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 中文(繁體)‎ · 吴语 · 粵語 · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް
Public-images-osm logo.svg building
Building part areas in building area.svg
Description
The building relation is used to group elements that form a building in simple 3D modelling.
Group: Buildings
Members
  • way - outline
  • way - part
  • see description for further members
Wikidata
Status: in use

Relations of type=building are used as one way to group elements that form a building in Simple 3D Buildings. Note that in many cases the added complexity of a relation is unnecessary--unless at least one part of a building is hanging over the building footprint, or the building has a complex structure with lots of parts, one can simply position building parts within a building outline as described in Simple 3D Buildings.

Disambiguation: This kind of relation modeling was also used for indoor mapping to group building levels, but with the introduction of Simple Indoor Mapping in 2012 these relations are deprecated. There was an earlier proposal for this tag in the context of address mapping, apparently abandoned in 2007.

Tagging

type=building are used in two contexts: 3D modelling and indoor mapping. We will here distinguish those two usages, however they can be combined in a same relation.

For 3D modelling

They relate building:part=yes, roof:ridge=yes and roof:edge=yes to a building outline.

Further details, in particular the properties that can be assigned to the individual parts of the building, are described in Simple_3D_Buildings.

Role Elements Recurrence Comment
outline area relation one or more The area that makes up the building outline, e.g. the walls.
This outline needs to be tagged with Tag:building=yes or another building value for compatibility with 2D-renderers.
part area one or more Building parts. These parts differ from each other in terms of height, roof-shape, colour, material, ...
ridge way zero or more Ways which make up the roof ridges of a building or building part.
edge way zero or more Ways which make up the roof edges of a building or building part.

For indoor mapping

There are different approaches for indoor mapping.

Simple Indoor Tagging

The Simple_Indoor_Tagging scheme does not need additional relations for the levels.

IndoorOSM

IndoorOSM is a deprecated tagging scheme that has been replaced by Simple_Indoor_Tagging

An example of building relation (indoor mapping) and its members

The IndoorOSM proposal defines separate relations per level type=level and groups them into the building entity. Each level has a level_n role, where n is the level number (level_0 for ground). Entrances can be added in the relation with the entrance role. See also entrance=* and amenity=parking_entrance

Role Elements Recurrence Comment
level_n relation one or more For type=level relations, with n as the level number (level_-1, level_0, level_1, ...). There should be at least one member (level_0).
entrance node one or more Building entrances. There should be at least one member, the main entrance.

Examples

Examples tested 2014-12-15:

Further Demo areas here.

See also