Geoscience Reference
In-Depth Information
Fig. 1 Structure of the
building model. It consist of
six application schemas (grey
boxes) which define four
profiles (depicted black). An
arrow denotes a dependency
between application schemas:
the schema on the backside of
the arrow uses and extends
the schema the arrow points
to (INSPIRE TWG BU
2013
)
Buildings
Base
Core 3D
Core 2D
Buildings2D
Buildings3D
Buildings
Extended
Base
Extended 3D
Extended 2D
Buildings
Extended2D
Buildings
Extended3D
3.1 The BuildingsBase Schema
The BuildingsBase schema collects all types, attributes and relations which are
common to all profiles. It defines two feature types: Building and BuildingPart.
The scope of Building has already been defined in the preceding paragraph.
A Building can be partitioned in different BuildingParts. This concept has been
taken from CityGML and accommodates the fact that components of a building
may differ with regard to geometry (different heights, for example) or thematic
properties (different years of construction, different usages, …). However, a
BuildingPart potentially might be considered itself as a building. In particular, it
must rest on the ground. This excludes dormers or towers on Buildings from being
BuildingParts. The UML diagram for the BuildingsBase application schema is
given in Fig.
2
and the (complex) data types used in the schema are provided in
Fig.
3
.
Buildings and BuildingParts potentially have the same spatial and non-spatial
attributes. The attribute values of a part apply only to that part, whereas attribute
values of a building refer to all parts. Care should be taken that no contradictions
are introduced (for details, see Stadler and Kolbe
2007
). If parts are present, the
building geometry should be represented for the parts only. The attributes of
Building and BuildingPart are provided by two super classes AbstractBuilding and
AbstractConstruction (the differentiation into two classes is due to the usage in the
extended profiles, where constructions inherit from AbstractConstruction only).
The inspire id (the type of this attribute is complex, see INSPIRE Drafting Team
Data Specifications
2010
) is the unique object identifier published by the
responsible body, which may be used by external applications to reference the
spatial object. Date and time a spatial object was inserted or changed in the data
set, and date and time is was removed are defined by the attributes beginLife-
spanVersion and endLifespanVersion: Both attributes are common for all INSPIRE
objects (for details see INSPIRE Drafting Team Data Specifications
2010
). The
conditionOfConstruction of a building can take one of the values 'declined',
'demolished', 'functional', 'projected', 'ruin', or 'under construction'. The dates
