Revit IFC import pitfalls

From Wiki.OSArch

If you intend an IFC file to be opened/imported with Revit things get complicated, just as they are for export from Revit (see: Revit setup). This page list some pitfalls to avoid.

Mandatory conditions[edit]

Having an IfcBuildingStorey is optional in IFC standards but mandatory for Revit (Last test: revit-ifc 21.1). Else an empty file will be created. Building elements like walls will be missing. [workarounds 1]

In IFC standards an IfcProduct can be contained in an IfcSite, IfcBuilding, IfcBuildingStorey or IfcSpace [1]. However if you do so, Revit will link element to a newly created Level called Default on import. [workarounds 1]

Geolocation / Model far from origin[edit]

Revit has currently no option to choose which base point an IFC model should be positioned by, it will be placed at the internal origin. If the IFC model is placed to far from this origin, Revit will not import your model correctly. Although in any software it is not a good idea to have large coordinates. Use relative placement as much as possible.

You might be able to see the model by linking the IFC instead of importing it, but if the coordinates are large (world-coordinates) the IFC needs to be pathced before it kan be linked in to Revit. This can be done in BlenderBIM:

  • Go to the scene pane and look for "IFC Patch"
  • Choose either "ResetAbsoluteCoordinates" or "OffsetObjectPlacements" in the Recipie dropdown.
  • Choose filepaths to patch and patched
  • If you choose "OffsetObjectPlacement" add in the "arguments"-field the Shared Coordinates in Revit in opposite direcion seperated by comma. x, y, z, rotation E.g: -128900, -1532260, 0, -19.5

Workarounds[edit]

References[edit]