I guess you want to use Ruby API… (if yes the topic forum category needs to be modified to [Developers][Ruby API])
The Model #export method description contains a small ifc export example and link to the Exporter Options file. Where you can find the options and very short description for IFC…
One of the main concepts of an IFC is it’s hierarchical structure (Project > Site > Building > Storey)
Every object is therefore nested.
Ideally every object needs to be a component and need to be nested in the Storey-component (no sub-wall)
Normal tags have no influence on this, they need Classification Tags (eg. An IFCBuildingElement (stud) is nested in a componet that is classified as IFCStorey, which is nested in a component with the IFCBuilding classification.
It looks like one has to nest things a certain way to get IFC to work, not sure if IFC is really worth the trouble. It also seems like it was developed for large multi-story buildings rather than residential projects, but I’m sure it could be adjusted to work for either.
At first glance, not a big fan. I’ve heard of IFC before but have never really dug into it until this point.
In europe in 2030 IFC will be mandatory for permits. Anything that can be developed towards greater compatibility between Sketchup and IFC import and export will be great to have.
Ifc is the way to exchange geometry and information between different software.
You can add parameters to each component that can be read by every software.
The structure is very simple:
a project
a site
one or more buildings
one or more stories
Inside every storey each component has its own category, so you can distinguish between walls, doors, etc.
Adding information to each one is easy.
Send me a message if you want me to show you how to manage all that information.
Yes, groups are a problem with Ifc. The Ifc schema is saved in component definition and while exporting all entities nested into a group are not exported correctly.
In Spain since 2023 Ifc has started to be the exchange format in big public projects. It’s expected to be in all public projects in a few years.
So if you don’t use Ifc you have less opportunities because private projects requirements are also copying government exchange formats.
P.D. Components have more taged information in layout than groups.
All Ifc parameters can be labeled. Rich information for your drawings