IFC 4.3.x development

5.4.3.56 IfcRelSpaceBoundary

Change log

IFC4

additions where_rules CorrectPhysOrVirt
deletions where_rules WR1
modificationsattributes RelatedBuildingElement is_optionalChanged from True to False
modificationsattributes RelatingSpace definition Changed from IfcSpace to IfcSpaceBoundarySelect

IFC4X1

additionswhere_rulesCorrectPhysOrVirt
deletionswhere_rulesCorrectPhysOrVirt

IFC4X2

additionswhere_rulesCorrectPhysOrVirt
deletionswhere_rulesCorrectPhysOrVirt

IFC4X3_RC3

additionswhere_rulesCorrectPhysOrVirt
deletionswhere_rulesCorrectPhysOrVirt

5.4.3.56.1 Semantic definitions at the entity

The space boundary defines the physical or virtual delimiter of a space by the relationship IfcRelSpaceBoundary to the surrounding elements.

  • In the case of a physical space boundary, the placement and shape of the boundary may be given, and the building element, providing the boundary, is referenced,
  • In the case of a virtual space boundary, the placement and shape of the boundary may be given, and a virtual element is referenced.

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 element (including virutal elements and openings) to define many such relationship and each space to be defined by many such relationships.

Space boundaries are always defined as seen from the space. In general two basic types of space boundaries are distinguished:

  • 1^st^ level space boundary: defined as boundaries of the space, not taking into account any change in building element or spaces on the other side.
  • 2^nd^ level space boundary: defined as boundary taking any change in building element or spaces on the other side into account. It can be further distinguished into
    • 2^nd^ level type A: There is a space on the other side.
    • 2^nd^ level type B: There is a building element on the other side.

The exact definition of how space boundaries are broken down depends on the view definition, more detailed conventions on how space boundaries are decomposed can only be given at the domain or application type level.> * In an architectural or FM related view, a space boundary is defined totally from inside the space. This is a 1st level space boundary. * In a thermal view, the decomposition of the space boundary depends on the material of the providing building element and the adjacent spaces behind. This is a 2nd level space boundary.

1st level 2nd level

Figure 1 — Space boundary at first level

Figure 2 — Space boundary at second level

2nd level type a 2nd level type b

Figure 3 — Space boundary at second level type A

Figure 4 — Space boundary at second level type B

The differences between the 1^st^ and 2^nd^ level space boundaries is identified by:

  • 1^st^ level: SELF\IfcRoot.Name = "1stLevel" SELF\IfcRootDescription = NIL
  • 2^nd^ level: SELF\IfcRoot.Name = "2ndLevel" SELF\IfcRootDescription = "2a", or "2b"

Differentiation between physical and virtual space boundary is illustrated in Figure 1 and Figure 42.

As shown in Figure 41, if the IfcRelSpaceBoundary is used to express a virtual boundary, the attribute PhysicalOrVirtualBoundary has to be set to VIRTUAL. The attribute RelatedBuildingElement shall point to an instance of IfcVirtualElement. If the correct location is of interest, the attribute ConnectionGeometry is required.

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.

"IfcRelSpaceBoundary_virtual (35K)"

As shown in Figure 42, 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 geometically, or it may be omited, in that case it describes a physical space boundary logically.

"IfcRelSpaceBoundary_physical (35K)"

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.

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

NOTE  In most view definitions the connection geometry for the related IfcElement is not provided.

The geometric representation (through the ConnectionGeometry attribute) is defined using either 2D curve geometry or 3D surface geometry for space boundaries. In most view definitions the 3D connection surface geometry is required.

Surface connection geometry

The following constraints apply to the surface connection geometry representation:

Curve connection geometry

The following constraints apply to the 2D curve representation:

HISTORY  New entity in IFC1.5, the entity has been modified in IFC2x.

IFC2x CHANGE The data type of the attribute_RelatedBuildingElement_ has been changed from IfcBuildingElement to its supertype IfcElement. The data type of the attribute ConnectionGeometry has been changed from IfcConnectionSurfaceGeometry to its supertype IfcConnectionGeometry.

IFC4 CHANGE The attribute RelatedBuildingElement has been made mandatory. For virtual boundaries the reference to IfcVirtualElement is now mandatory.

5.4.3.56.1 Attributes

#Attribute Type Description
IfcRoot
1GlobalId IfcGloballyUniqueId Assignment of a globally unique identifier within the entire software world.
2OwnerHistory OPTIONAL IfcOwnerHistory Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object,

> NOTE  only the last modification in stored - either as addition, deletion or modification.

> IFC4 CHANGE  The attribute has been changed to be OPTIONAL.
3Name OPTIONAL IfcLabel Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule.
4Description OPTIONAL IfcText Optional description, provided for exchanging informative comments.
IfcRelationship
IfcRelConnects
IfcRelSpaceBoundary
5RelatingSpace IfcSpaceBoundarySelect Reference to one spaces that is delimited by this boundary.
6RelatedBuildingElement IfcElement Reference to ~~Building~~ Element, that defines the Space Boundaries.

> IFC2x CHANGE  The data type has been changed from IfcBuildingElement to IfcElement with upward compatibility for file based exchange.

> IFC4 CHANGE  The attribute has been changed to be mandatory.
7ConnectionGeometry OPTIONAL IfcConnectionGeometryPhysical representation of the space boundary. Provided as a **curve or** surface given within the LCS of the space.

> IFC2x CHANGE  The data type has been changed from IfcConnectionSurfaceGeometry to IfcConnectionGeometry with upward compatibility for file based exchange.
8PhysicalOrVirtualBoundary IfcPhysicalOrVirtualEnum Defines, whether the Space Boundary is physical (Physical) or virtual (Virtual).
9InternalOrExternalBoundaryIfcInternalOrExternalEnum 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).

5.4.3.56.2 Entity inheritance

dot_inheritance IfcRelSpaceBoundary1stLevel IfcRelSpaceBoundary1stLevel IfcRelSpaceBoundary IfcRelSpaceBoundary IfcRelSpaceBoundary1stLevel->IfcRelSpaceBoundary IfcRelConnects IfcRelConnects IfcRelSpaceBoundary->IfcRelConnects IfcRelConnects_children 15 more... IfcRelConnects_children->IfcRelConnects IfcRelationship IfcRelationship IfcRelConnects->IfcRelationship IfcRelationship_children 5 more... IfcRelationship_children->IfcRelationship IfcRoot IfcRoot IfcRelationship->IfcRoot IfcObjectDefinition IfcObjectDefinition IfcObjectDefinition->IfcRoot IfcPropertyDefinition IfcPropertyDefinition IfcPropertyDefinition->IfcRoot

5.4.3.56.3 Definitions applying to General Usage

5.4.3.56.3.1 Identity

IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.

5.4.3.56.3.2 Revision Control

Ownership, history, and merge state is captured using IfcOwnerHistory.

5.4.3.56.4 Formal representations

ENTITY IfcRelSpaceBoundary
 SUPERTYPE OF (ONEOF
	(IfcRelSpaceBoundary1stLevel))
 SUBTYPE OF (IfcRelConnects);
	RelatingSpace : IfcSpaceBoundarySelect;
	RelatedBuildingElement : IfcElement;
	ConnectionGeometry : OPTIONAL IfcConnectionGeometry;
	PhysicalOrVirtualBoundary : IfcPhysicalOrVirtualEnum;
	InternalOrExternalBoundary : IfcInternalOrExternalEnum;
 WHERE
	CorrectPhysOrVirt : ((PhysicalOrVirtualBoundary = IfcPhysicalOrVirtualEnum.Physical) 
  AND (NOT('IFC4X3_DEV_a1492713.IFCVIRTUALELEMENT' IN TYPEOF(RelatedBuildingElement)))) 
OR 
((PhysicalOrVirtualBoundary = IfcPhysicalOrVirtualEnum.Virtual) 
  AND (('IFC4X3_DEV_a1492713.IFCVIRTUALELEMENT' IN TYPEOF(RelatedBuildingElement)) 
  OR   ('IFC4X3_DEV_a1492713.IFCOPENINGELEMENT' IN TYPEOF(RelatedBuildingElement)))) 
OR 
(PhysicalOrVirtualBoundary = IfcPhysicalOrVirtualEnum.NotDefined);
END_ENTITY;