Borobudur Ws

They are actually the geometry of the Axis. In this case is the beam axis. In IFC2x3 export it seems that some beam axes may be placed with some offset incorrectly. They do not show up in most viewers since they do not usually draw the axis geometry. If you select the associated beam, you will see that the axis is also selected. The correct axis usually lies on the beam itself (or a the center of the beam, or near it depending on the axis of the beam when defined in the original authoring tool)....

If you use a parameter and "somehow" the enum is exported accordingly, it is probably a coincident? Revit exporter will try to determine the appropriate enum from the door definition (including the 2D geometrical representation to determine the swing). In this case, it might be just that the door you have is determined to be an enum that is consistent with the value you put into the parameter. Since Revit never uses the parameter, it does not really use the value from that parameter. The same enum...

Or if you could provide a small test data to show the issue.

Upon re-reading the message, I have a question: Are you using IfcDoorStyleOperationEnum as a name of a parameter? From the code I do not see anywhere that this name is used. If you could provide more detailed information, I maybe able to help. Thanks, Wawan

Yes, you are right. There is a change for the Enum in line with the change in the IFC4 schema. The older IfcDoorStyle (used in Ifc2x3) has been deprecated and replaced with IfcDoorType (http://www.buildingsmart-tech.org/ifc/IFC4/final/html/schema/ifcarchitecturedomain/lexical/ifcdoorstyle.htm). Along with this change, IfcDoorStyleOperationEnum has also been deprecated from IFC4 onward and it is replaced with IfcDoorTypeOperationEnum (http://www.buildingsmart-tech.org/ifc/IFC4/final/html/schema/ifcsharedbldgelements/lexical/ifcdoortypeoperationenum.htm)....