Creating aggregated elements and exporting to IFC


IFC format has functionality to create aggregates of elements that will be treated as elements on their own. For example IfcCurtainWall can be composed of IfcPlates and IfcMembers. There are other similar types: IfcElementAssembly, IfcWallElementedCase etc.

Is there a way to create this kind of aggregated elements manually in VisualArq and export those to IFC?


Hi @Taavi_Looke VisualARQ provides the ifc Tag feature that lets you assign an ifc Category to a piece of geometry, in order to export it to IFC with that specific category. If you create a block from different objects that have been tagged with different ifc categories, these will be lost and only the ifc category assigned to the block will remain. On the other hand, if you group these objects instead, the ifc Category of each part will remain when reading that IFC file.
In case of VisualARQ objects, something similar happens. They are composed by different parts/components (curtain wall frame, cells, supports, etc…) but the curtain wall objects are exported as ifc Curtain Walls.


It seems that if objects are part of an IfcElementAssembly that VA brings these into the Rhino document as a block. This is good, but all the elements that are within that assembly do not have any parameters. This represents a large data loss.

Could there be an update to the VA .ifc import tool to allow for the paramters (and values) to be maintained for elements within IfcElementAssemblies?



Hi @lignindes,

Yes, we’re aware of this issue, and we have plans to fix it in a future update. I’ve added your vote to our wish list, and you’ll be notified when we have news about this issue.