Wall-based IfcOpeningElements from doors and windows behaving differently
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
Looks like ```IfcOpeningElement``` objects generated from doors or windows do not behave the same way as those generated from wall-hosted Generic Model void cut families (exported as ```IfcBuildingElementProxy```):
- Property set ```Pset_OpeningElementCommon``` is not exported.
- Base quantities are not exported
- ```IfcRectangleProfileDef.ProfileName``` not exported (Yes, I know that's an optional attribute, but it exports for the Generic Model openings so why not here, too? Solibri seems to use either this property or the opening's ```Reference``` attribute - also not exported - for structuring its model browser, see screenshot below)
Would be great if the export behaviour could be consistent for all wall based openings.
- Exporter: 23.2.5
- Tried IFC2x3CV2.0 & IFC4RVArch.
- Tried old and new shared parameters
```IfcOpeningElement``` of a generic model void cut family:

```IfcOpeningElement``` of a door family:

Contributor guide
Research direction
Reproduce the export with wall-hosted door/window families and Generic Model void cut families using IFC2x3CV2.0 and IFC4RVArch, then compare the resulting IfcOpeningElement data. Done means both opening types consistently export Pset_OpeningElementCommon, base quantities, IfcRectangleProfileDef.ProfileName, and the opening Reference where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100