IfcTester: Bug for IDS in specification Pset_ManufacturerOccurence

Dear community,
I have started to use IDS in a project of mine with blenderBIM and trying some sustainable specification.
When I am setting up the property about Pset_ManufacturerOccurence, the IDS become invalid. I do assign this property to my ifc model in blenderbim. But the testing reulst failed. Does anybody know whats wrong with it?
I am using blender4.1 with blenderbim 240602, and i use usBIM online editor to write my ids file.


Comments

  • edited July 2024

    My orignial IDS file, since i cant upload IDS here so i change it to text.

  • edited July 2024

    You can see in the audit report that it is actually checking for the pset named ManufacturerOccurence, not Pset_ManufacturerOccurrence. This is probably because there is a typo when creating your IDS (Occurrence has two r)

    Another problem is that you are asking for an IfcLabel but the BarCode should be an IfcIdentifier.

  • Ys I did try what u say. But the file still valid.


  • Do I need to import a barcode instead of just type in something?

  • What does "Reserved prefix 'Pset_' for property set name (Pset_ManufacturerOccurence) in the context of Ifc2x3 on property. " mean?

  • You still didn't fix the typo, you need two R in occurrence. It should look like this:

            <ids:property dataType="IFCIDENTIFIER" cardinality="required">
              <ids:propertySet>
                <ids:simpleValue>Pset_ManufacturerOccurrence</ids:simpleValue>
              </ids:propertySet>
              <ids:baseName>
                <ids:simpleValue>BarCode</ids:simpleValue>
              </ids:baseName>
              <ids:value>
                <ids:simpleValue>123456</ids:simpleValue>
              </ids:value>
            </ids:property>
    

    What does "Reserved prefix 'Pset_' for property set name (Pset_ManufacturerOccurence) in the context of Ifc2x3 on property. " mean?

    It means that Pset_ is a special name that only buildingSMART can use. Once you fix the spelling mistake, the error should go away. If it does not, it's a bug with usBIM and feel free to report to them :)

    Ace
Sign In or Register to comment.