revit-ifc
revit-ifc copied to clipboard
Revit Curtain Walls doesn't seem to obey IfcExportAs
This seems symptomatic of a few other family categories, but Revit curtain walls don't seem to respect the value of the IfcExportAs. I can't get it to export, say, as an IfcFurnishingElement.
I ran into this problem as well.
My BIM Manager is requesting to export all subparts of a curtain wall as IfcCurtainWall, for very good reasons.
But when using the Revit curtain wall tool, the IFC classes seems to be hard coded:
- IfcCurtain (container) -- IfcMember (for mullions) -- IfcPlate (for panels)
Which means we will have to redo the whole project in ArchiCAD, or whatever else. Great,
To understand what you are trying to do. Do you want every mullion and panel to be exported as a non-contained IfcCurtainWall? Are you willing to share the very good reasons? I can create an item to expand this case, once I completely understand it, since it might not be as simple as IfcExportAs - it may also require changing containment as well.
There should be an option to:
- Either export the entire curtain wall as a single IFC element (i.e. joined geometry) of a class of our choice
- Export the curtain wall with as a class of our choice, and the elements aggregated within it as classes of our choice (so it isn't all IfcMember and IfcPlate
The usecase is that so many modelers abuse Revit curtain walls to model all sorts of stuff that just ... aren't curtain walls. They can be as docile as glazed shopfronts, which are regular walls, not curtain walls, to office partitions, to fencing, to really funky stuff like skirting, signage, other types of coverings, etc.
That's on our fairly short term plan, to improve mapping of elements. I guess one complexity here is how to distinguish:
- This is really a window not a curtain wall - but I want it to be a container, and
- This is really one window, export it as such. I guess maybe it should always be number 2?
So, two years later, has there been any progress?
...and - three years later, news?
Just that this is part of some work we are currently working on, around option 2 above only.