Skip to main content

Ensure compatibility of IFC classes and IFC properties in specifications

Currently, users can add every IFC standard property to every specification regardless of the IFC entity of the specification, meaning you could add the property "ExtendToStructure" (PsetWallCommon) to an IfcBoiler which would not be schema conform.

Option 1:

  • When adding a property to a specification, filter the IFC catalog for properties that match the IFC entity of the specification - if the specification is mapped on an IFC entity

Option 2:

  • Show a warning in the property table of the specification, when the property that is mapped on an IFC schema property does not match the IFC classification of the specification.

This would help to use the IFC standard correctly in your catalog and avoid assignments that are not intended by the schema.

Log in to comment and vote

No comments yet

Be the first to share your thoughts.