[IFC Export] Problems with IFC (structural view) export

This forum section is only for IFC-related issues
balrobs
Posts: 449
Joined: Fri Apr 24, 2020 8:58 pm

Re: [IFC Export] Problems with IFC (structural view) export

Post by balrobs »

Moult wrote: Tue Jun 15, 2021 3:25 am Sorry for the late reply. Yes, Reference is more correct than Analysis.

IFC materials do not distinguish between architectural and structural. All IFC materials can store properties (e.g. youngs modulus) regardless of which discipline uses it. The same Ifc Material may be shared between disciplines (in an ideal, integrated world).

The relationship between the architectural model (i.e. body shapes) and structural model (i.e. stick model with analysis) is given by IfcRelAssignsToProduct.There are some discussions here: https://community.osarch.org/discussion ... nalysis/p1
So if I got it correctly it would be preferable to have only one material for both disciplines with all its properties.
I will try to understand the existing FreeCAD code and see how I can modify it to fit this needs.

Thank you @Moult for your valuable contribution :D
Kind regards
Jesusbill
Posts: 7
Joined: Wed Jun 10, 2020 11:53 pm

Re: [IFC Export] Problems with IFC (structural view) export

Post by Jesusbill »

@balrobs I am kind of leaning towards the use of a common material where possible. Certainly I would not be in favour of duplicate materials with the same name, as materials are non-root entities and there is no way to tell one of the other. At the end of the day, we want to promote collaboration between disciplines, so I think that in a general use case one can think that the architect uses a general "Beton" material for all concrete elements.
Then, the engineer, specifies for each element the specific grade/class so he is enhancing the available information relative to his domain. In that case it would make sense in my opinion that this new piece of information propagates back to the 3D model IfcElement related entities

@bernd the link Dion provided gives the thread, these comments are the most relevant https://community.osarch.org/discussion ... omment_944

PS: Nice screencast by the way!
Jesusbill
Posts: 7
Joined: Wed Jun 10, 2020 11:53 pm

Re: [IFC Export] Problems with IFC (structural view) export

Post by Jesusbill »

Found also this related thread https://community.osarch.org/discussion ... esentation
Had forgotten about it
User avatar
bernd
Veteran
Posts: 12849
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland
Contact:

Re: [IFC Export] Problems with IFC (structural view) export

Post by bernd »

balrobs wrote: Tue Jun 15, 2021 6:27 am
Moult wrote: Tue Jun 15, 2021 3:25 am Sorry for the late reply. Yes, Reference is more correct than Analysis.

IFC materials do not distinguish between architectural and structural. All IFC materials can store properties (e.g. youngs modulus) regardless of which discipline uses it. The same Ifc Material may be shared between disciplines (in an ideal, integrated world).

The relationship between the architectural model (i.e. body shapes) and structural model (i.e. stick model with analysis) is given by IfcRelAssignsToProduct.There are some discussions here: https://community.osarch.org/discussion ... nalysis/p1
So if I got it correctly it would be preferable to have only one material for both disciplines with all its properties.
I will try to understand the existing FreeCAD code and see how I can modify it to fit this needs.
IMHO and AFAIK. As said the hybird ifc just saves both models into one ifc file. They are totally independent from each other. They are just in one file. As long as they are independent you would have to create spearate materials for architecutral and for structural data.

On the contrary, if you would like to start to make one model out of it, no longer a hybrid out of two independent ones, it makes sense to use just one material for structural data and for architectur data.

BTW: these hybrid modells might not be standard according buildingSMART. We schould make sure they are before start to connect them.
balrobs
Posts: 449
Joined: Fri Apr 24, 2020 8:58 pm

Re: [IFC Export] Problems with IFC (structural view) export

Post by balrobs »

Jesusbill wrote: Tue Jun 15, 2021 10:00 am Found also this related thread https://community.osarch.org/discussion ... esentation
Had forgotten about it
Thanks @Jesusbill for the links!
a lot to learn ... will read it carefully.
Kind regards
balrobs
Posts: 449
Joined: Fri Apr 24, 2020 8:58 pm

Re: [IFC Export] Problems with IFC (structural view) export

Post by balrobs »

bernd wrote: Tue Jun 15, 2021 10:53 am ...
IMHO and AFAIK. As said the hybird ifc just saves both models into one ifc file. They are totally independent from each other. They are just in one file. ...
I'm not quite sure about that. Studying @Yoriks IFC-exporter I found this lines of code, which should bind architectural (product) and structural objects (structobj) together :?:

Code: Select all

# associate with structural analysis object if any

        if structobj:
            exportIFCStructuralTools.associates(ifcfile,product,structobj)
bernd wrote: Tue Jun 15, 2021 10:53 am BTW: these hybrid modells might not be standard according buildingSMART. We schould make sure they are before start to connect them.
I totally agree!
Before deciding how to procede we should check this and come to a consensus!
Maybe this two hybrid IFC files genereated for my test structure could be helpfull.
Proposal1: Material duplication (one for architectural one for structural elements)
prop1_hybrid_model.ifc
(55.33 KiB) Downloaded 132 times
Proposal2: No material duplication (one material both for architectural and structural elements)
prop2_hybrid_model.ifc
(53.1 KiB) Downloaded 123 times
Post Reply