[Bug]: The type of the NominalValue parameter in the IfcPropertySingleValue attribute is lost when read using the GetLine method.

[Jenychen1996]

What happened?

A bug happened!

When creating predefined classes such as IfcWallType, the type of the NominalValue parameter in the IfcPropertySingleValue within the passed parameter HasPropertySets is missing. In the IFC file, only the numerical value is saved without the type hierarchy (such as IfcLengthMeasure). When reading it through the GetLine method, the NominalValue parameter value is null.

Version

0.0.69

What browsers are you seeing the problem on?

No response

Relevant log output

Anything else?

Problem Document:
web-ifc-69-properties.txt

please change txt to ifc.

Please contact us if needed.

[NiklasPor]

I also just stumbled into this for IfcInteger and IfcReal. Did you find any workaround yet?

[NiklasPor]

I've tried a few other data types (IfcInteger, IfcReal, IfcHeatingValueMeasure) and it seems that any data type which extends NumberHandle is written to the ifc file without the type.

Expected

#123733=IFCPROPERTYSINGLEVALUE('PileProperty',$,IFCINTEGER(999),$);

Actual

#123733=IFCPROPERTYSINGLEVALUE('PileProperty',$,999,$);

[Jenychen1996]

I also just stumbled into this for and . Did you find any workaround yet?IfcInteger``IfcReal

I'm sorry, but I haven't found a suitable solution yet. I am still waiting for an official response.

[NiklasPor]

Okay, so I found the workaround for numeric properties. It seems that the error lies inside the NumberHandle class. Instead of using the class, if you pass a plain object with type, name and value writing the value will work correctly.

Workaround:

const property = /** Property from wherever **/;

const nominalValue = new IfcLengthMeasure(4);
const fixedValue = { name: nominalValue.name, type: nominalValue.type, value: nominalValue.value };

property.NominalValue = fixedValue;

ifcApi.WriteLine(modelId, property)