Autodesk / revit-ifc

IFC for Revit and Navisworks (2019+)
482 stars 194 forks source link

ENH: Better handling of import class mapping tables #798

Open andydandy74 opened 2 months ago

andydandy74 commented 2 months ago

Enhancement Description

Context

We often receive IFC files with MEP elements where the elements are only loosely classified by generic IFC classes like IfcFlowSegment (instead of e.g. IfcDuctSegment). When consultants are unable or unwilling to provide more precise classifications of their elements, we have to take matters into our own hands. To improve the mapping to Revit categories we have therefore created multiple import class mapping tables (e.g. one specific for HVAC models etc.).

Problem description

The main challenges of using these tables are:

Proposed changes

Revit Version

2024.0.x

IFC for Revit Addon Version

24.x.x

Windows Version

10 22H2

sweco-begertjanvdb commented 2 months ago

Something that might fit here too, make the Document.ExportIFCCategoryTable path not read-only In the Design Automation 4 Revit workflow we have to sometimes rely on different tables depending on the needs of a project. if the API allowed for setting that ExportIFCCategoryTable value, It'd be most convenient

denizmaral commented 1 month ago

Are you talking about export class mapping? @sweco-begertjanvdb You can change it here: https://www.revitapidocs.com/2024/d9696d40-cf97-5d24-8151-662e35e7d616.htm