Difference between revisions of "Revit setup for OpenBIM/Revit IFC import pitfalls"
m |
(Add some additional infos) |
||
| Line 1: | Line 1: | ||
When you need to author an IFC file which will be opened by Revit things get complicated as they are for export (see: [[Revit setup]]). This page list some pitfalls to avoid. | When you need to author an IFC file which will be opened by Revit things get complicated as they are for export (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 if your geometry is too far from Revits internal origin. Although in any software it is not a good idea to have large coordinates. Use relative placement as much as possible. | Revit will not import your model correctly if your geometry is too far from Revits internal origin. 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. | + | You might be able to see the model by linking the IFC instead of importing it. |
| + | |||
| + | =Workarounds= | ||
| + | <references group="workarounds" /> | ||
| + | |||
| + | =References= | ||
| + | <references /> | ||
[[Category:Autodesk Revit]] [[Category:Proprietary software]] [[Category:Industry_Foundation_Classes_(IFC)]] | [[Category:Autodesk Revit]] [[Category:Proprietary software]] [[Category:Industry_Foundation_Classes_(IFC)]] | ||
Revision as of 00:36, 19 November 2020
When you need to author an IFC file which will be opened by Revit things get complicated as they are for export (see: Revit setup). This page list some pitfalls to avoid.
Mandatory conditions
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
Revit will not import your model correctly if your geometry is too far from Revits internal origin. 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.
Workarounds
References
- ↑ IfcRelContainedInSpatialStructure, IFC documentation
