Autodesk / Autodesk/revit-ifc

LongName Attribute not supported for Mass Category when exported to IfcSpace

Open
#134 3 comments 0 reactions 0 assignees View on GitHub
parameters-properties Triage
Dominant language
C#
Stars
637
Forks
225
PR merge metrics
No merged PRs in 30d

Description

If I export a Revit Area as IfcSpace, the [LongName attribute](https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/FINAL/HTML/ifcproductextension/lexical/ifcspace.htm) is taken from the BuiltIn 'Name' parameter. Of course, the Area Category in Revit gives no control over 3D form.

Issue:
If I export a Revit Mass as IfcSpace, there is no BuiltIn 'Name' parameter. The LongName attribute apparently cannot be taken from any of the following parameters, named: 'Name', 'Longname', 'IfcName', 'IfcLongname', 'LongnameOverride'.

As an aside, the unavoidable presence of the 'Name' property in the [Pset_AirSideSystemInformation](https://standards.buildingsmart.org/IFC/RELEASE/IFC2x3/FINAL/HTML/psd/IfcSharedBldgServiceElements/Pset_AirSideSystemInformation.xml) results in this pset being assigned to the IfcSpace created from the Revit Area, even though none of the other relevant properties are given in Revit. Is this an unavoidable side effect?

Contributor guide

Open the contributing guide

Research direction

Reproduce exports for a Revit Area and Revit Mass converted to IfcSpace, then inspect the exporter’s parameter mapping for LongName and the assignment of Pset_AirSideSystemInformation. Compare the generated IFC output and confirm that the Mass can supply the intended LongName without incorrectly assigning the property set.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.