Autodesk / revit-ifc

IFC for Revit and Navisworks (2019+)
469 stars 193 forks source link

Exporting Revit walls to IfcCoveringType #155

Open AndersAlverfeldt opened 4 years ago

AndersAlverfeldt commented 4 years ago

Is there any way to export Revit walls to IfcCoveringType using the IFCExportType and IFCExportAs parameters? No matter what parameter values I set, the walls export to IfcWallStandardCase. This is working as expected for, for example, Revit ceilings and floors but not for walls or curtain walls. IfcCoveringType

thumDer commented 3 years ago

Any updates on this? It is an issue for at least 5 years, and it prevents us from providing appropriate IFCs, and makes us appologize to the customers every time.

AngelVelezSosa commented 3 years ago

We are looking at similar issues at the moment, so can try to get this in also.

thumDer commented 3 years ago

I've found that most of the system families have this non-documented hardcoded behaviour, which makes it very difficult to export proper IFC-s, since in most projects we cannot stick to the OOTB Revit Categories (so to speak miss-use them) because their graphical and other particular behaviour. At the and of the day the most convenient solution would be to get rid of the IfcExportAs limitations completely and let the user to export a Revit Railing as and IfcCoveringType.SKIRTINGBOARD if thats the correct class for that element. Honestly, I think adusting, or fine-tuning these System Family related hardcoded mappings is a dead-end.

AngelVelezSosa commented 3 years ago

Agreed, and that is the approach we are taking at least for walls and railings as a start. There is sadly no such thing as a System Family (a system family is basically something that doesn't have a real family element), but we plan to allow exporting a wall as anything. ... although a recent bug report shows that "anything" has its issues. Really, it will be a child of IfcProduct that's allowed.

thumDer commented 3 years ago

By "System Families" I mean anything that is not an instance of FamilyInstance API class. Elements of "System Families" have their own API classes, that can cause the confusion, but I think you are aware of that. Anyway, I'm glad to hear that you are taking that approach. Children of IfcProduct is quite enough.

thomvill commented 1 year ago

Any update on this? As far as I can tell, there is still no functionality for exporting ceiling grid lines to IFC, so curtain wall are often used as substitute.

AngelVelezSosa commented 1 year ago

You should be able to export a wall as covering types - are you finding this is not the case?

thomvill commented 1 year ago

I'm finding this is not the case, however I'm using Roof, not wall. The curtain wall (drawn as Revit Roof), comes out as IfcRoof and IfcCurtainWallType in Solibri.

I'm also having trouble modifying the IFC Export AS parameter in Revit, after updating to the latest IFC Exporter today (v23.3.0.0). That is likely an issue on my end, however.

image

AngelVelezSosa commented 1 year ago

"Export to IFC as" is the new parameter to use. And OK, the issue is that a roof can't be exported as a covering type? That would be a different (if related) issue.