Open brunopostle opened 10 months ago
It is not really clear for me to understand the expected behavior you are looking for but I think I have 2 proposals.
IfcVirtualElement
and an IfcRelSpaceBoundary
relating to each space are created. For geometry, I think all the 3 should share the same 3D geometry although it would be nice for the IfcVirtualElement
to have a 2D representation too for plan/section views.
IfcVirtualElement
with a surface as 3D geometryIfcVirtualElement
in account in addition to walls)IfcVirtualElement
in account)Both workflows requires to code some new features.
Where two spaces are connected but there is no wall or slab between them it is necessary to create a Virtual Element (without a Body representation) and give it a boundary geometry for each space.
However creating a Boundary from a Virtual Element and a Space produces this error:
Workaround is to create a dummy Wall, give it boundaries, reassign the class to Virtual Element, then delete the Body representation.
See also #1676 and #3493