Is there any particular reason why an Assembly (and the elements within the Assembly) always is associated with the lowest level in the model?
If I create in Revit an Assembly on Level 2, with elements on level 2, then the IfcElementAssembly (and the decomposed elements) are associated with Level1 in IFC...
Best regards,
Dirk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would a temporary fix with a parameter as "LevelOverride" or "LevelExportAs" be a possibility?
The only accepted values for this parameter should be the Name values of (Ifc)BuildingStoreys.
Best Regards,
Dirk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I am also struggling with this and believe I have asked this fix also a few years ago. Could you please specify the correct workaround as I have not managed to get it work so far? I have tried to create ifc parameters "LevelOverride" and "LevelExportAs" as suggested for assemblies in Revit and named them after existing higher levels in my project, but the assemblies still get assigned to lowest possible level in ifc. I have the latest exporter. I have tried with both instance and type parameters.
How do I override the level for assemblies?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A partial solution is currently in beta in GitHub - please see the issues board there. Basically, there will be an IfcSpatialContainer shared parameter that will allow overriding the level. But it is only a text parameter, so it will not be associative if you change level names. Again, this will be a partial fix only.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Is there any particular reason why an Assembly (and the elements within the Assembly) always is associated with the lowest level in the model?
If I create in Revit an Assembly on Level 2, with elements on level 2, then the IfcElementAssembly (and the decomposed elements) are associated with Level1 in IFC...
Best regards,
Dirk
Hi Dirk,
You're right, that's what happens. We have an item to fix this.
Andy
Hi,
Any chance this will be fixed soon?
Best regards,
Dirk
Would a temporary fix with a parameter as "LevelOverride" or "LevelExportAs" be a possibility?
The only accepted values for this parameter should be the Name values of (Ifc)BuildingStoreys.
Best Regards,
Dirk
Have this issue been solved ? I can't see other than it still exports on base level.. ? Any workarounds ?
It's not yet fixed, but there is a workaround, since Wawan Solihin recently added the functionality to override the level.
Regards,
Dirk
Hello,
I am also struggling with this and believe I have asked this fix also a few years ago. Could you please specify the correct workaround as I have not managed to get it work so far? I have tried to create ifc parameters "LevelOverride" and "LevelExportAs" as suggested for assemblies in Revit and named them after existing higher levels in my project, but the assemblies still get assigned to lowest possible level in ifc. I have the latest exporter. I have tried with both instance and type parameters.
How do I override the level for assemblies?
A partial solution is currently in beta in GitHub - please see the issues board there. Basically, there will be an IfcSpatialContainer shared parameter that will allow overriding the level. But it is only a text parameter, so it will not be associative if you change level names. Again, this will be a partial fix only.
Yes, I got it working now, thank you for quick response!