https://standards.buildingsmart.org/IFC ... ntpart.htm
yeah IfcBuildingPart in IFC is not the container but the parts inside ... I will hav a look if there is some standard container object in ifc. Allplan does create it different from ArchiCAD and Vectorworks. They use some standard containerobjet and uses products insted of IfcBuildingElemntPart inside.
As said I will have a look.
IFC export workaround and question
Re: IFC export workaround and question
As far as I know there is no standard "container" object type in IFC. That's a problem...
Now, any object can act as a container for others. For a simple example look into the IfcOpenHouse, the windows are an agglomerate of IfcPlates and IfcMembers. And their shape is understood as an aggregate of the children shapes.
But that means the container is also an IfcProduct. A container is not just a container.
Now, any object can act as a container for others. For a simple example look into the IfcOpenHouse, the windows are an agglomerate of IfcPlates and IfcMembers. And their shape is understood as an aggregate of the children shapes.
But that means the container is also an IfcProduct. A container is not just a container.
Re: IFC export workaround and question
Thus should we use IfcBuildingElementProxy as standard? Storey of a Storey is not good either.
Re: IFC export workaround and question
Agree...
Maybe we need to remove the "Undefined" option and default everything to BuildingElementProxy
Maybe we need to remove the "Undefined" option and default everything to BuildingElementProxy
Re: IFC export workaround and question
https://standards.buildingsmart.org/IFC ... tproxy.htm
the first two lines does say exact this ... If nothing fits use this ...
the first two lines does say exact this ... If nothing fits use this ...