Door Operation should also work as an Instance parameter in Revit
- Dominant language
- C#
- Stars
- 637
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
We would love to have the IFC override parameter "Operation" for the Doors Category to also work as an Instance parameter. At the moment it doesn't.
The IFC operation type in the IFC file is based on both, this **Type** Operation parameter in Revit (if it is there), and the **Instance** placement of the Door (Flipped / Mirror) in Revit.
I am happy that the exporter already translates the Instance placement to an IFC Type value. But it will be more consistent if it also works with an Instance "Operation" parameter.
- just a thought-
Revit and IFC do not have parrallel structures if you think about Type or Instance. And that is ok. Revit is a modelling program. So it should be flexible. And IFC is an exchange format. So it should be basically rigid. The IFC exporter can and should be a way to bridge these differences without troubling Revit or IFC.
Contributor guide
Research direction
Start by tracing the Revit IFC exporter’s Door handling, including the existing IFC override "Operation" mapping and the logic that translates flipped or mirrored instance placement into the IFC operation type. The change is complete when an Instance "Operation" parameter on a Door is honored consistently alongside the Type parameter and placement, with exporter behavior verified in a representative IFC file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100