PR: IfcSpatialContainer doesn't work properly

[Mairh93]

Problem Description

Dear all,

I am working in Revit 2023 and IFC Version 23.3.1.0. I added the parameter IFCSpatialContainer from the Autodesk's .txt file.

In Revit I assigned to my elements two different levels. When I export in IFC the elements are not in the levels that I assigned.

See images below:

Thank you in advance!

Revit Version

2023.1.x

IFC for Revit Addon Version

Other / None

Windows Version

11 22H2

[Teun1]

Have you also tried using the Revit Level name? It looks like Niveau 3 and not DOWN. And perhaps change the space in the Revit Level name to an underscore. Niveau_3

[Mairh93]

Yes I used the IfcName parameter in order to 'rename' the level in the ifc exportation. The puprose of the ifcSpatialContainer parameter is to assign the elements in the level that I need. Is it correct?

I tested and if I delete the IfcName Parameter (so I need to name the levels as I want to have them in the IFC exportation), it seems to work. Why there is this 'conflit' between these two parameters?

Thank you in advance for your time!

[AngelVelezSosa]

IfcSpatialContainer may be based on the internal (not IFC) name of the Level. So instead of deleting IfcName, can you set IfcSpatialContainer to the "real" name of the level? I don't think one is more correct than the other, but I wouldn't want to toggle the behavior since it would break the other half of the people (assuming I am correct in my first line of assumption).

[ArtemHnatko]

Hello @Mairh93,

Thank you for reporting this issue. Based on Autodesk documentation and previous discussions, the IfcSpatialContainer parameter is supported, but it has some known limitations:

• The value must exactly match the Level name in Revit (including spaces and characters) Link.
• If an IfcName override is applied to the Level, it may conflict with IfcSpatialContainer and cause unexpected results Link.
• The parameter can sometimes be reset or ignored during export, especially if the Level is not marked as Building Storey Link.
• When two Levels have the same or very close elevations, the exporter may ignore IfcSpatialContainer and assign elements to the first detected Level Link.

To help us confirm the root cause, could you please provide a minimal sample model that demonstrates the issue? In particular, it would be useful to test:

• A case with IfcSpatialContainer set to the exact Level name (no overrides).
• A case with IfcName overrides disabled.
• Confirmation that the target Level is marked as Building Storey.

This will allow us to reproduce the behavior and decide whether it is a bug or a limitation in the current exporter logic.