Autodesk / Autodesk/revit-ifc

ENH: Use IFC parameters from parameter service when linking models

Open
#799 1 comment 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

## Problem description
Currently,Revit creates a separate shared parameters file for every IFC file that is linked into a project. This has two major disadvantages, though:
- When creating schedules for elements in linked IFC files, it is impossible to display information from multiple IFC-links in a single schedule in a meaningful way since the shared parameters from the respective models have different GUIDs, even if their names are the same.
![image](https://github.com/user-attachments/assets/bc2c2b6e-16ee-471a-a21c-4499ea423d2a)
- The impact on tagging is even worse. Individual tag families have to be created for each linked IFC file.

## Proposed changes
- For all standard attributes/properties use the shared parameters that are provided via the ACC parameter service.
- Only create a shared parameter file for custom properties

### Revit Version

2024.0.x

### IFC for Revit Addon Version

24.x.x

### Windows Version

10 22H2

Contributor guide

Open the contributing guide

Research direction

Start by locating the IFC linking flow that creates shared parameter files and the integration point for the ACC parameter service. Compare how standard attributes and custom properties are handled; done means standard properties use service-provided shared parameters while a shared parameter file is created only for custom properties.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.