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: 1) building outlines for the most general area of a complex building and 2) building parts to describe sections of the building, especially those with different height or other attributes.
- 1 How to Map
- 2 Tagging for building outlines and parts
- 3 Demo areas
- 4 Software support
- 5 Terminology
- 6 Related Proposals
How to Map
The building outline represents the area of land covered by the union of all parts of the building. The outline may in most cases also be considered the building footprint. This is a closed way or multipolygon tagged with building=*.
Building attributes (e.g., address, name, overall height, operator, etc.) must be tagged on the building outline.
The building outline provides backward compatibility for 2D rendering software, such as Mapnik, and other data consumers not interested in 3D modelling. When a building has any building:part=* areas, the building outline is not considered for 3D rendering.
Parts of a building that have differing physical characteristics (height, color, etc) are usually modeled by drawing an area within the building outline tagged with the building:part=* tag. The value of the building:part=* tag is usually yes, but it can be any building=* value.
The entire building outline is filled with building:part=* ways, 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.)
See the following section for building attribute tags typically applied to ways tagged with building:part=*.
Ways tagged with building:part=* are mainly considered for 3D rendering. 2D renderers ignore the building attribute tags described in the following section.
For buildings with a complex structure, a type=building relation can be used to group the building outline and all building parts together. However, there is no need to create a type=building relation if the building contains only a few building parts or has a simple structure
If there is no relation, an application should treat all building parts within the area of the building outline as part of that building.
Tagging for building outlines and parts
The following tags can be used on both building outlines and building parts.
Height and levels
|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 modeled with the simple techniques described on this page.
Surface color and material
|building:colour=*||Colour of the building façade. See colour=* for possible values.|
|roof:colour=*||Colour of the building roof. See colour=* for possible values.|
|building:material=*||Outer material for the building façade.|
|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||OSM2World||OSMBuildings||F4 Map||OpenScienceMap||OSM go||Mapbox GL||Tangram||Blicky|
|Karlsruhe, Fernmeldeturm Grünwettersbach|
|Köln, Wohngebiet in Neuehrenfeld als "Labor"|
|New York City|
|Paris, Eiffel Tower||N/A|
|San Jose (California)|
|Syracuse (New York)|
Main article: 3D development
Many maps and tools support the simple 3D buildings schema. Among the first were the OSM-3D.org renderer in 2009, the OSM2World renderer and Kendzi3D JOSM plugin in 2011, and the Nutiteq Android 3D Mapping SDK (now Carto Mobile SDK) and WikiMiniAtlas in 2012. OSMBuildings launched a 2.5D display in 2012, followed by a 3D version in 2015. In 2013, F4 Map became the first renderer to fully support the simple 3D buildings schema.
|Software name||Platform||Schema support||License||Notes|
|Kendzi3d||Windows, macOS, Linux||yes||BSD||JOSM plugin|
|Application name||Platform||Schema support||License||Notes|
|F4 Map||Web||yes||Proprietary||Demo Web Map with rendering and scene support|
|Mapbox Static API||Web||partial||BSD||Requires a free Mapbox Studio account.|
|OpenScienceMap||Web||partial||LGPL||Interprets only height/min_height tags client-side. The S3DB Layer uses vtm meshes generated on the server (using plpgsql with PostGIS and SFCGAL). Web map|
|OSM2World||Web||partial||LGPL||Currently implementing the remaining features for the 0.2.0 release - slippymap (Germany only)|
|osmapa.pl Mapnik stylesheet||Web||partial||most roof types implemented in 2.5D view|
|OSM go||Web||partial||GPL||Only pyramidal and dome (yet, flat is default)|
|WikiMiniAtlas||Web||partial||GPL||only pyramidal roofs|
Main article: Frameworks
|Software name||Platform||Language||Schema support||License||Notes|
|Carto Mobile SDK||Android, iOS, Windows Phone||Java, Objective-C++, Swift, C#||partial||BSD||most roof shapes supported; see Carto's documentation|
|Mapbox Android SDK||Android||Java|
|Mapbox iOS SDK||iOS||Objective-C, Swift, Interface Builder|
|Mapbox macOS SDK||macOS||Objective-C, Swift, Interface Builder, AppleScript|
|Mapbox Qt SDK||Qt||C++, QML|
|Mapbox Unity SDK||Cross-platform||C#||Apache|
|osm2x3d||Web||partial||Unknown||see also  and |
|Tangram ES||Android, iOS, Linux, macOS||C++|
|VTM||Android, iOS, Web||Java||partial||LGPL||Part of the mapsforge project.|
|Software name||Platform||Schema support||License||Description|
|blender-osm||Windows, macOS, Linux||partial||GPL||One click download and import of OpenStreetMap and terrain. Can import more than 100,000 buildings. A large number of roof shapes is supported: flat, gabled, hipped (for a quadrangle outline only), mono-pitched, half-hipped, round, pyramidal, gambrel, dome, onion and saltbox.|
|Mapbox Studio||Web||partial||Proprietary||Includes a Mapbox GL style editor that supports building (part) heights.|
|Maputnik||Web||partial||MIT||A Mapbox GL style editor that supports building (part) heights.|
|Tangram Play||Web||partial||MIT||A Tangram scene editor that supports extruded buildings with heights based on OSM data.|
- F3DB (Full 3D buildings)