Editing List of known invalid IFC practices
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | |||
See also [[:Category:IFC invalid practices]] | See also [[:Category:IFC invalid practices]] | ||
Line 12: | Line 11: | ||
|- | |- | ||
| Using <code>Link IFC</code>, IfcSpace will convert into Revit generic models, which is hardcoded. This makes it impossible for rooms to contain elements. The only workaround is to use <code>Open IFC</code> instead. | | Using <code>Link IFC</code>, IfcSpace will convert into Revit generic models, which is hardcoded. This makes it impossible for rooms to contain elements. The only workaround is to use <code>Open IFC</code> instead. | ||
− | |||
− | |||
− | |||
| 2021-04-12 | | 2021-04-12 | ||
|} | |} | ||
Line 29: | Line 25: | ||
[[Category:Industry Foundation Classes (IFC)]] [[Category:IFC invalid practices]] | [[Category:Industry Foundation Classes (IFC)]] [[Category:IFC invalid practices]] | ||
− |