Difference between revisions of "List of known invalid IFC practices"
From Wiki.OSArch
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{IFC_Documentation}} | ||
See also [[:Category:IFC invalid practices]] | See also [[:Category:IFC invalid practices]] | ||
| Line 28: | Line 29: | ||
[[Category:Industry Foundation Classes (IFC)]] [[Category:IFC invalid practices]] | [[Category:Industry Foundation Classes (IFC)]] [[Category:IFC invalid practices]] | ||
| + | [[Category:Revit]] | ||
Latest revision as of 15:19, 4 August 2022
|
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). |
See also Category:IFC invalid practices
Autodesk Revit[edit]
| Summary | Last Verified |
|---|---|
Using Open IFC, any objects using Tessellations are not supported. For example, if you export an IFC4 from ArchiCAD, unless you force it to use parametric solids, Revit will be unable to show the geometry in these IFCs.
|
2021-04-12 |
Using Link IFC, 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 Open IFC instead.
|
2021-04-12 |
| When exporting, Revit will not record metric units correctly for the geolocation map conversion. This makes geolocation useless. | 2021-04-12 |
Bentley OpenBuildings Designer[edit]
| Summary | Last Verified |
|---|---|
IfcSurfaceStyleShading is still exported without an a Transparency attribute, even if an IFC4 export is done. This is technically correct if you check in a pre-addendum version of IFC4, but is not useful to users or updated IFC4 parsers.
|
2019-05-23 |
