Handle first Level Space Boundaries

[DaJansenGit]

In GitLab by @veronikarichter on Apr 28, 2021, 13:31

Up to now, none of the ifc files provided first level space boundaries. Erics Space Boundary Algorithm now provides those first level space boundaries: AC20-FZK-Haus_with_SB_with1stLevel.ifc

The kernel is not yet able to handle ifcs including first level space boundaries properly. First level space boundaries should be excluded within the inspect-methods (e.g. tz_inspect). Something like this could work:

• ifc_type = 'IfcRelSpaceBoundary'
• for entity in entities:
• if entity.RelatedBuildingElement is not None:
• related_element = Element.get_object(entity.RelatedBuildingElement.GlobalId)
• if not entity.RelatingSpace.is_a('IfcSpace'):
• continue
• if related_element is not None:
• space_boundary = SubElement.factory(entity, ifc_type)
• if space_boundary.ifc.is_a() == 'IfcRelSpaceBoundary1stLevel':
• continue
• elif space_boundary.ifc.Description not in {'2a', '2b'}:
• continue
• self.sb_instances[space_boundary.guid] = space_boundary
• self.logger.info("Create space boundaries by semantic detection") Even if this works for self.sb_instances first level SBs are listed in the instances (globally), attached to thermal_zones and to bound_instances. A hotfix could be to preprocess the ifc file and to remove all first level space boundaries from the IFC before import.

[DaJansenGit]

this is strongly related to #109 I think. After we have a dedicated base element type for related Elements (which are not IfcProducts) we have to improve the way how the space boundaries are inspected.