Autodesk / Autodesk/revit-ifc

PR: Revit 2023 exporting IFC4 containing a few elements converted into Parts - all elements will be exported as Parts

Open
#749 1 comment 0 reactions 0 assignees View on GitHub
problem
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

### Problem Description

When a model that contains **just one (or a few elements**) converted into parts is exported into IFC4 (using the IFC exporter version **23.3.1** ) and the option to **Export only elements visible in the view** is checked, the result of export in the IFC file will be that all exported elements (visible in the view) will be exported as **IfcBuildingElementParts**. (as all of them was converted into parts in revit. which was not the case)
If the same options are used but the model is exported into IFC 2x3 file, the result of export will be accurate (only elements converted into parts in revit will be exported as IfcBuildingElementParts, and the rest of the elements will be exported as respective Ifc Entities )
Find attached RVT2023 sample file and exported IFC4 file using mentioned options
[Sample.zip](https://github.com/Autodesk/revit-ifc/files/14424421/Sample.zip)

In some cases this could be a great feature (to export all compound/multi-layered model elements as parts, and that's an option that ArchiCad's IFC exporter has), but a user should have a control over it, and also GUIDs of exported Ifc Parts should be preserved. Currently it seems as a bug.

### Revit Version

2023.1.x

### IFC for Revit Addon Version

23.1.1

### Windows Version

10 22H2

Contributor guide

Open the contributing guide

Research direction

Reproduce the export using the attached Sample.zip with Revit 2023.1.x and IFC for Revit 23.1.1, checking IFC4 with visible-elements-only against IFC 2x3. Compare whether only Revit elements converted to parts become IfcBuildingElementParts, and verify that the corrected IFC4 output preserves the expected part GUIDs.

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.