I think there is a bug in the ifc extensions, which is due to a change in the Structural Function choices.
"Load-bearing" is no longer possible to pick, now it's "Structural":
Actually there are more bugs in the mapping, none of the properties is mapped correctly.
SR 7000222169 filed.
There is also a bug during export.
Property Description is not defined in IFC property set definition for Pset_SlabCommon
Doesn't work for beams either.
Pset_BeamCommon properties don't change when changing corresponding values, like IsExternal, FireRating, etc.
In AECOsim Building Designer Ss5, the property 'Description' has been removed from Pset_SlabCommon.
You are correct on that one, Holger. Apparently I didn't recognize that workspace / DatasetExtensions/IFC2x3_psets was updated in the last release.
However even after update of that one in my workspace, there is still no update of the IFC2x3_psets.
Take the IsExternal property, for example. Shouldn't the Pset_SlabCommon/IsExternal property change when the Thermal_Transm.../IsExternal value changes?
Andreas,
It seems you are mixing the US and GB datasets?!?
The US dataset uses enum values 'Structural' and 'Non-Structural' defined in ObjectStructuralUsage_enumlookups.xml (in the application), while the GB dataset uses enum values 'Load-bearing' and 'Non-Load-bearing' defined in file EnumLookups_Structural.xml (in Dataset_GB), which override those defined by the application.
This is reflected in the respective files ...\setting\IFC_PropertyMapping.set:
Dataset_US has entries, such as:Aluminum Beam * Pset_BeamCommon LoadBearing IfcBoolean EVALUATE DG("ObjectStructuralUsage/@StructuralFunction") EQ "Structural"; StructuralFunction ('Structural'=True)i.e. if the value of StructuralFunction is 'Structural' (as in your image), TRUE will be exported to the LoadBearing property of Pset_BeamCommon; any other value will be exported as FALSE.
In Dataset_GB, however, the entries (as in your image) are, for instance:Aluminum Beam * Pset_BeamCommon LoadBearing IfcBoolean EVALUATE DG("ObjectStructuralUsage/@StructuralFunction") EQ "Load-bearing"; StructuralFunction ('Load-bearing'=True)i.e. if the value of StructuralFunction is 'Load-bearing', TRUE will be exported to the LoadBearing property of Pset_BeamCommon; any other value will be exported as FALSE.
So, in your image above, although you entered 'Structural' for Structural Function, it will be exported as FALSE to the LoadBearing property, because as per you image, only the value 'Load-bearing' will be exported as TRUE.
So, you either have to change your enum values to ''Load-bearing' and 'Non-Load-bearing', or you have to edit bearing' with 'Structural'. Obviously, if you don't mix datasets, this won't be necessary.
>>> Warning: Editing text files can make them useless if you get the syntax wrong, so be very careful! <<<
Also please note: While mapping of properties with the same format can be done in the Property Mapping GUI (>>> only necessary if you add user-defined properties that duplicate IFC properties!!! <<<) it cannot be done if the formats are different, e.g. for ObjectStructuralUsage/Structural Function = string, Pset_BeamCommon/LoadBearing = Boolean.
Hope this clarifies the issue.
Regards,
Volker