Simple 3D buildings
The following tagging methods are results of the 2nd 3D Workshop Garching, where most 3D developers agreed on supporting a unified subset of tags in their programs. Basically we describe the volume of a building using two types of areas. Building outlines for the most general area of a complex building and building parts, to describe esp. parts with different height or other attributes.
The building outline is a closed way or multipolygon tagged with building=*. It represents the area of land covered by the union of all parts of the building. The outline is also referred to as the building footprint.
Building attributes (e.g., address, name, overall height, operator, etc.) must be tagged on the building outline.
The building outline provides backward compatibility for 2-D rendering software, such as Mapnik, and other data consumers not interested in 3D modelling. 2-D renderers ignore the building:part=* tags described in the following sections.
There are two options for tagging buildings for 3D rendering:
- Cover the whole outline with building:part=* areas, tagged with their respective height and other attributes. These areas may overlap each other or may be disjunct, depending on the building. (But while 2D footprints can and often need to overlap, avoid overlapping 3D volumes – especially if the volumes have common faces.) This method uses parts to cover the building outline without using relations.
- As above, but use building:part=yes only for those parts which differ from the overall building. This may not be supported by all renderers.
A relation tagged with type=building groups building outline and all building parts together. It is highly recommended to use the relation if there is at least one building part. Otherwise an application has to fall back to search for building parts only within the area of the building outline. See also ProposedRoofLines#Building_Relation for proposals of further details.
Tags for buildings outlines and parts
The following tags can be used on both building outlines and building parts.
|height=*||Distance between the lowest possible position with ground contact and the top of the roof of the building, excluding antennas, spires and other equipment mounted on the roof.|
|min_height=*|| Approximate height below the building structure.|
Note that when min_height is used, height is still defined as the distance from the ground to the top of the structure. So "bridge" with 3 meters height, where bottom part of the bridge is positioned 10 meters above ground level will have min_height=10, height=13.
|building:levels=*|| Number of floors of the building above ground (without levels in the roof), to be able to texture the building in a nice way.
If you tag new buildings, try to give a height value. Try to use building:levels=* only in addition to an height tag!
|building:min_level=*||levels skipped in a building part, analogous to min_height|
You can characterize the building roof using a catalogue of well known roof types. Additional roof shapes may be introduced later (S3DB_Proposals), including advanced approaches for manual modelling (e.g., ProposedRoofLines or parts of OSM-4D/Roof_table).
|roof:orientation=along/across||For roofs with a ridge the ridge is assumed to be parallel to the longest side of the building (roof:orientation=along). But it can be tagged explicitly with this tag.|
|roof:height=*||roof height in meters|
|roof:angle=*||Alternatively to roof:height=*, roof height can be indicated implicitly by providing the inclination of the sides (in degrees).|
|roof:levels=*||Number of floors within the roof, which are not already counted in building:levels=*.|
|roof:direction=*||direction from back side of roof to front, i.e. the direction towards which the main face of the roof is looking|
Again, some roofs (e.g., square buildings) cannot be accurately modelled with the simple techniques described on this page.
|building:colour=*||Colour of the building facade. See colour=* for possible values.|
|roof:colour=*||Colour of the building roof. See colour=* for possible values.|
|building:material=*||Outer material for the building facade.|
|roof:material=*||Outer material for the building roof.|
To make it as easy as possible for the community, we started added details already to the following:
|Location||OpenStreetMap (2D)||OSM2World (3D)||OSMBuildings (3D)||F4 Map(3D)||OpenScienceMap||osm2x3d (x3d)|
|Graz 1 (AT)||Link||Link||Link||Link||Link||Link|
|Graz 2 (AT)||Link||Link||Link||Link||Link||Link|
|Rostock Südstadt (GER)||Link||Link||Link||Link||Link||Link|
|Eiffel tower/Paris (FR)||Link||Link||Link||Link||Link||Link|
|Karlsruhe 2 (GER)||Link||Link||Link||Link||Link||Link|
|Köthen 1 (GER)||Link Link-2||Link Link-2||Link Link-2||Link Link-2||Link Link-2||Link|
|Las Vegas (US)||Link||Link||Link||Link||Link||Link|
|New York (US)||Link||Link||Link||Link||Link||Link|
|Warszawa (PL)||Link||(no rendering)||Link||Link||Link||Link|
An image can help to understand some architectural terms.
There are many maps and tools that support the Simple 3D buildings schema. This is a list of known ones.
|Software Name||Schema Support||Description||Creator||Open source||Programming language|
|OSM Importer for Blender||Partial||Can import more than 100.000 buildings. Work is underway to support roof shapes||vvoovv||yes||Python|
|OSM2World||Partial||Currently implementing the remaining features for the 0.2.0 release - slippymap (Germany only)|
|Nutiteq Android 3D mapping SDK||Partial||most roof shapes supported|
|WikiMiniAtlas||Partial||only pyramidal roofs|
|F4 Map||Full||Demo Web Map with rendering and scene support|
|OpenScienceMap||Partial||Interprets only height/min_height tags client-side. The S3DB Layer uses vtm meshes generated on the server (using plpgsql with PostGIS and SFCGAL).|
|osm2x3d||Partial||see also  and |
|osmapa.pl mapnik stylesheet||Partial||most roof types implemented|
|Mapzen||Partial||Mapzen renders 3D buildings in Tangram and other products|
|Mapbox||Partial||Mapbox supports 3D buildings in its Mapbox GL JS specification.|
- F3DB (Full 3D buildings)