properties of exported nested Wall Sweeps
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
When exporting Walls with nested Wall Sweeps to IFC. The nested Wall Sweeps become IfcBuildingElementProxy objects without infomation and their Id as a Reference. They also clash with their original host Wall.
When exporting with the IFC4 Reference View option. All Walls layers become IFC Building Element Parts in the IFC. These layers are grouped and found under the host IfcWall. And have a name based on their material in Revit (nice). Each layer has it's own Id in the IFC. But nested Wall Sweeps are still found as an individual IfcBuildinElementProxy object with a different Id. This second object lags a lot of information.
When you make parts of the host, it is possible to add more (IFC) information to these parts in Revit. This method works fine for e.g. Wall Layers (when needed). But it does not work at all for the Parts belonging to the nested Wall Sweep. They stay IfcBuildingElementProxy objects without a lot of information.



Contributor guide
Research direction
Start by reproducing the IFC4 Reference View export for Walls containing nested Wall Sweeps, then inspect the resulting IfcBuildingElementProxy objects and their relationship to the host IfcWall. Done means nested Wall Sweep parts no longer clash with the host and retain the expected information and distinct Ids, matching the behavior described for Wall layers.
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
- Needs clarification
- Newbie friendliness
- 30/100