Autodesk / Autodesk/revit-ifc

ENH: Export IfcVirutalElement as Type

Open
#815 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

### Enhancement Description

It's great we can export IfcVirtualElement.CLEARANCE and IfcVirtualElement.PROVISIONFORVOID.
However, they can only be exported as instance. If I search for the IfcVirutalElement in my Family I cannot find it:

![image](https://github.com/user-attachments/assets/18e6b5bd-609f-4a6f-95d4-51d3d5f576b0)

It would be great If we could add this to Types so the Famiulies can be maintained better.

Revit 24.3.0.13, export to IFC4x3

Thanks!

### Revit Version

2024.0.x

### IFC for Revit Addon Version

24.x.x

### Windows Version

11 22H2

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the export in Revit 2024.0.x with IFC4x3, checking how IfcVirtualElement.CLEARANCE and PROVISIONFORVOID are represented as instances. Trace the export path for these elements and identify how exported Types are handled. Done means the elements are available under Types and families can be maintained there.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.