Difference between revisions of "Revit setup for OpenBIM/Revit IFC import pitfalls"
(Start Revit import pitfalls page) |
m (Duncan moved page Revit IFC import pitfalls to Revit setup for OpenBIM/Revit IFC import pitfalls) |
||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Autodesk_Revit}} | |
| + | {{IFC_Documentation}} | ||
| + | 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 | + | =Mandatory conditions= |
| − | + | Having an <code>IfcBuildingStorey</code> 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. <ref name=link group="workarounds">Link the IFC file instead of importing it. Some elements behaviour might change eg. a wall geometry become not modifiable by hand</ref> | |
| − | + | ||
| + | In IFC standards an <code>IfcProduct</code> can be contained in an <code>IfcSite</code>, <code>IfcBuilding</code>, <code>IfcBuildingStorey</code> or <code>IfcSpace</code> <ref>''[https://standards.buildingsmart.org/IFC/RELEASE/IFC4/ADD2/HTML/schema/ifcproductextension/lexical/ifcrelcontainedinspatialstructure.htm IfcRelContainedInSpatialStructure]'', IFC documentation</ref>. However if you do so, Revit will link element to a newly created <code>Level</code> called ''Default'' on import. <ref name=link group="workarounds"/> | ||
=Geolocation / Model far from origin= | =Geolocation / Model far from origin= | ||
| − | Revit will not import your model correctly | + | 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 importing it. | + | |
| + | 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. <code>x, y, z, rotation</code> E.g: <code>-128900, -1532260, 0, -19.5</code> | ||
| + | |||
| + | =IfcSpace= | ||
| + | When linking <code>IfcSpace</code> are converted into Generic Model and it is not possible to fix this. See issue [https://github.com/Autodesk/revit-ifc/issues/15 revit-ifc/issues/15]. A [https://github.com/Autodesk/revit-ifc/issues/15#issuecomment-558748917 workaround] is to create a model with spaces only and import it instead. | ||
| + | |||
| + | =Workarounds= | ||
| + | <references group="workarounds" /> | ||
| + | |||
| + | =References= | ||
| + | <references /> | ||
| − | [[Category:Autodesk Revit]] [[Category:Proprietary software]] | + | [[Category:Autodesk Revit]] [[Category:Proprietary software]] [[Category:Industry_Foundation_Classes_(IFC)]] [[Category:IFC invalid practices]] |
Latest revision as of 06:40, 31 January 2022
|
This page is Autodesk Revit documentation on implementing OpenBIM. All articles in the OSArch wiki related to Autodesk Revit can be seen in the Category:Autodesk Revit |
|
This page is relevant to understanding Industry Foundation Classes (IFC). The Industry Foundation Classes (IFC) Category includes all pages related to Industry Foundation Classes (IFC). |
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, rotationE.g:-128900, -1532260, 0, -19.5
IfcSpace[edit]
When linking IfcSpace are converted into Generic Model and it is not possible to fix this. See issue revit-ifc/issues/15. A workaround is to create a model with spaces only and import it instead.
Workarounds[edit]
References[edit]
- ↑ IfcRelContainedInSpatialStructure, IFC documentation
