Autodesk / Autodesk/revit-ifc

PR: not able to export built in material parameters into standardised IFC psets

Open
#766 4 comments 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

There are two ways material psets come out:

1. https://github.com/Autodesk/revit-ifc/blob/b83595ff01f72f2a63242e00daf01508f2264287/Source/Revit.IFC.Export/Utility/MaterialPropertiesUtil.cs#L56-L58 from built-in parameters into hardcoded property sets called things like "Identity" or "Structural".
2. https://github.com/Autodesk/revit-ifc/blob/b83595ff01f72f2a63242e00daf01508f2264287/Source/Revit.IFC.Export/Utility/MaterialPropertiesUtil.cs#L60 using a custom mapping from custom project / shared parameters where you can use the user defined psets txt config file to put it in whatever Pset you want.

The problem is that the first way does not put data into standard bSI psets. So the Revit built-in concrete compression data goes into a pset called "Structural", not "Pset_MaterialConcrete". And the second way cannot map these "built-in parameters" to my knowledge.

So my possible workarounds are to 1. patch the IFC to put it in the right spot and delete the other parameters that don't interest me / aren't validated or 2. create another project parameter and have the data duplicated in two spots.

### 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 in Source/Revit.IFC.Export/Utility/MaterialPropertiesUtil.cs, especially the built-in parameter handling around lines 56-58 and custom mapping around line 60. Trace how built-in material parameters are assigned to exported property sets. Done means built-in concrete compression data and other applicable material parameters can be placed in the corresponding standard bSI property sets rather than only hardcoded sets such as "Structural".

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
tooling
Issue type
Feature
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.