Pset_SlabCommon / StructuralFunction

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":

Parents
  • 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



  • Actually I'm using none of those, but created our own, because Bentley doesn't deliver any dataset for Norway anymore.

    Our workspace is based on the unified Dataset_NM buildingdataset.

    IFC_PropertyMapping.set has this line included.

    Slab * Pset_SlabCommon LoadBearing IfcBoolean EVALUATE DG("ObjectStructuralUsage/@StructuralFunction") EQ "Load-bearing"; StructuralFunction ('Load-bearing'=True)

    Enumlookups_Structural.xml has this one.

    <EnumLookup definition="ObjectStructuralUsage" property="ObjectStructuralUsage/@StructuralFunction" extendable="false">
    <Enum value="Structural"/>
    <Enum value="Non-Structural"/>
    <Enum value="Undefined"/>
    </EnumLookup>

    So apparently the bug is in the Dataset_NM.

    However this still does not explain the IsExternal bug, doesn't it?

  • Unfortunatly the IsExternal properties don't export to ifc correct either.

    This one is a screenshot from Tekla Bimsight.

  • Looks like the Enumlookups_Structural.xml in the Dataset_NM is different from both the british, danish and swedish one.

    I'll change that in our company set in the meantime.

Reply Children
No Data