Autodesk / Autodesk/revit-ifc

Problem: Bug Revit 2022 IFC Export Shaft opening in floors

Open
#609 8 comments 0 reactions 0 assignees View on GitHub
2022 export geometry problem Revit Triage
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

Hello,

The Revit 2022 IFC exporter 22.6.0.0 (and 22.6.2.0) has a issue with Shaft openings that share a edge with floor(s).

Bug occurs when there is also a shaft within the floor, if there are only shafts sharing egdes with the floor, the floor boundary is exported correctly.

After some testing I found out the combination of steps to reproduce this:
1. draw a rectangular floor on level1
2. copy floor to level 2
3. draw a shaft intersecting both floors AND have the shaft share a edge with the floors
4. draw a shaft in the middle of the floor and only let it intersect one of the floors.
5. export to IFC (2x3 scheme)

The floor boundary with the 2 schaft openings isn't correct, the other one is.

Further issue (minor) the shaft sharing it's boundary with the floor(s) isn't exported as opening in the Ifc.

Below a image with the IFC export on the left (with missing opening) and revit file on the right (with shafts selected)
![Revit2022_ifc_shaft_issue](https://user-images.githubusercontent.com/117643427/223349442-7a903854-ec87-447e-acbe-06b30fc48a39.png)

Contributor guide

Open the contributing guide

Research direction

Start with the Revit 2022 IFC exporter 22.6.0.0 or 22.6.2.0 and reproduce the five listed steps using IFC 2x3 export. Compare the exported floor boundary and openings against the Revit model, including the shaft that shares an edge with the floors; done means both shaft openings are represented correctly and the floor boundary is accurate.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.