372x
003939
2023-01-30

FAQ 005348 | The IFC cross-sections from my imported IFC file are not converted correctly.

Question:
The IFC cross-sections from my imported IFC file are not converted correctly.

Answer:
In principle, you can select the IFC elements graphically. If you open the shortcut menu (by right-clicking the mouse button), you can decide for each element whether you want to convert it to a member, a surface, or a solid.
► Image | Converting IFC Elements https://www.dlubal.com/de/img/037164
To convert the IFC elements into the Dlubal elements (such as the Dlubal cross-sections), the required information must be available. Check the following aspects for this.
1. Assigning Dlubal Names in Conversion Table
In the CAD/BIM manu bar, you can access the information of the respective IFC objects by using the conversion tables. The information imported from the IFC file is displayed in the first table column. Successfully imported cross-sections are clearly assigned to the IFC objects. For the conversion, it is necessary to assign the Dlubal names accordingly in the table. You can easily select them from the material and cross-section library.
► Image | Assignment in Conversion Table https://www.dlubal.com/de/img/037103
2. Cross-section names cannot be imported from the IFC file
In the case of some imported IFC files, no imported cross-sections are displayed in the conversion table. The table column of the external cross-sections is empty. However, a cross-section name is visible in the properties of the IFC elements. This means that the information on the cross-section is available in the IFC file, but it cannot be read by RFEM.
► Image | Impossible to Read Out Cross-Section https://www.dlubal.com/de/img/037165
In this case, a conversion according to Point 1 cannot be carried out. The external cross-sections cannot be added to the conversion table afterwards, as they are not assigned to an IFC element. You can convert these IFC elements into members first in order to adapt the cross-section of the member subsequently.