VisualArq and IFC export


I have a question regarding IFC export with VisualArq. I am working with models created fully with Rhino geometry following this logic:

  • The object’s material are informed using the object’s layer
  • Components and sub-components are blocks and nested blocks

These models are mainly off-site prefabricated architecture, hence the possibility to follow a strict components and sub-components logic.

I need to create IFC from these models, for interoperability and documentation purposes.

My question is the following (and sorry if it contains a misinterpretation of what IFC can do, I’m still in the process of learning): can I strictly follow this previous hierarchy and replicate it with IFC, or do I have to think about this problem differently?

An example will be more obvious: let’s say I have a wall panel composed of one wood element and one metallic element. Is there a way to create an IfcBuildingElementProxy with the wood element and an IfcBuildingElementProxy with the metallic element (I would like to do this to have information like carbon footprint, density, etc, attached to each, and it varies according to materiality), and then create an IfcWall component from these two?

I know I may be reaching the limits of what VisualArq can do about IFC export but I am ready to spend some time writing python or tweaking grasshopper, so any hint about this will be of great help!

Thank you :slight_smile:

Hi @antoine3,

You can define the Ifc type you need for any Rhino geometry, but I am afraid you cannot define a different Ifc type for hosted geometry.

Maybe you can create a wall with two layers and create some parameters in that wall with a name which identifies the hosted element. I mean something like this:

Here you have more information about IFC:

1 Like