Definition from buildingSMART: The space boundary (IfcRelSpaceBoundary) defines the physical or virtual delimiter of a space as its relationship to the surrounding elements.
The exact definition of how space boundaries are broken down depends on the view, more detailed conventions on how space boundaries are decomposed can only be given at the domain or application type level.
EXAMPLE: In an architectural or FM related view, a space boundary is defined from the inside of the space and does not take the providing building element into account. A plane area (even if the building element changes) is still seen as a single space boundary. In an HVAC related view, the decomposition of the space boundary depends on the material of the providing building element and the adjacent spaces behind.
HISTORY: New entity in IFC Release 1.5, the entity has been modified in IFC Release 2x .
IFC2x PLATFORM CHANGE: The data type of the attributeRelatedBuildingElement has been changed from IfcBuildingElement to its supertype IfcElement with upward compatibility for file based exchange. The data type of the attribute ConnectionGeometry has been changed from IfcConnectionSurfaceGeometry to its supertype IfcConnectionGeometry with upward compatibility for file based exchange.
The IfcRelSpaceBoundary is defined as an objectified relationship that handles the element to space relationship by objectifying the relationship between an element and the space it bounds. It is given as a one-to-one relationship, but allows each building element to define many such relationship and each space to be defined by many such relationships.
Note: With the upward compatible platform extension the IfcRelSpaceBoundary can now also be given to an IfcOpeningElement.
If the IfcRelSpaceBoundary is used to express a virtual boundary, the attribute PhysicalOrVirtualBoundary has to be set to VIRTUAL. If this virtual boundary is between two spaces, and the correct location is of interest, the attribute RelatedBuildingElement shall point to an instance of IfcVirtualElement, and the attribute ConnectionGeometry is required to be inserted.
NOTE: The connection geometry, either by a 2D curve or a 3D surface, is used to describe the portion of the "virtual wall" that separates the two spaces. All instances of IfcRelSpaceBoundary given at the adjacent spaces share the same instance of IfcVirtualElement. Each instance of IfcRelSpaceBoundary provides in addition the ConnectionGeometry given within the local placement of each space.
NOTE: IfcVirtualElement has been introduced in IFC2x2 Addendum 1 to facilitate virtual space boundaries.
If the IfcRelSpaceBoundary is used to express a physical boundary between two spaces, the attribute PhysicalOrVirtualBoundary has to be set to PHYSICAL. The attribute RelatedBuildingElement has to be given and points to the element providing the space boundary. The attribute ConnectionGeometry may be inserted, in this case it describes the physical space boundary geometrically, or it may be omitted, in that case it describes a physical space boundary logically.
Geometry Use Definitions:
The IfcRelSpaceBoundary may have geometry attached. If geometry is not attached, the relationship between space and building element is handled only on a logical level. If geometry is attached, it is given within the local coordinate systems of the space and (if given in addition) of the building element.
NOTE: The attributes CurveOnRelatingElement at IfcConnectionCurveGeometry or SurfaceOnRelatingElement at IfcConnectionSurfaceGeometry provide the geometry within the local coordinate system of the IfcSpace, whereas the attributes CurveOnRelatedElement at IfcConnectionCurveGeometry or SurfaceOnRelatedElement at IfcConnectionSurfaceGeometry provide the geometry within the local coordinate system of the subtype of IfcElement.
The connection geometry, when given, can be given as a curve (for 2D representations of space boundaries) or as a surface (for 3D representations of space boundaries).
Note: With the upward compatible platform extension the ConnectionGeometry can now also be given by a 2D curve.
The geometric representation (through the ConnectionGeometry attribute) is defined using either 2D curve geometry or extruded surfaces for space boundaries which bounds prismatic spaces.
The following constraints apply to the 2D curve representation:
The following constraints apply to the surface representation:
|RelatingSpace||:||Reference to one spaces that is delimited by this boundary.|
IFC2x PLATFORM CHANGE: The data type has been changed from IfcBuildingElement to IfcElement with upward compatibility for file based exchange.
Physical representation of the space boundary. Provided as a curve or surface given within the LCS of the space.
IFC2x PLATFORM CHANGE The data type has been changed from IfcConnectionSurfaceGeometry to IfcConnectionGeometry with upward compatibility for file based exchange.
|PhysicalOrVirtualBoundary||:|| Defines, whether the Space Boundary is physical (Physical) or virtual (Virtual).
|InternalOrExternalBoundary||:|| Defines, whether the Space Boundary is internal (Internal), or external, i.e. adjacent to open space
(that can be an partially enclosed space, such as terrace (External).
|WR1||:||If the space boundary is physical, it shall be provided by an element. If the space boundary is virtual, it shall either have a virtual element providing the space boundary, or none.|