Difference between revisions of "Revit setup for OpenBIM/Revit IFC type products"

From Wiki.OSArch
m
Line 1: Line 1:
 
The following attributes may be filled.
 
The following attributes may be filled.
  
−
Note that the shared parameter names used for these parameters, such as <code>Ifcname</code>, are ''not'' in CapsCase format. This is because Revit only allows you to create parameters either as a type or instance parameter, but not both. As the parameter names are hardcoded in the Revit IFC exporter, we have established a convention of using CapsCase for instance parameters, and Capitalised for type parameters.
+
Note that the shared parameter names used for these parameters, such as <code>IfcName[Type]</code>, need to have <code>[Type]</code> as a suffix. It may be required to update to the latest IFC exporter, as the one shipped by Revit has a bug where type attributes are ignored.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 10: Line 10:
 
| <code>Name</code>
 
| <code>Name</code>
 
| Yes
 
| Yes
−
| By default, Revit exports the family's <code>Type Name</code> value. If these values match the codes used in schedules and annotation tags, your <code>Name</code> attribute will be correctly filled. In the likely event that this isn't the case (e.g. you are tagging a <code>Type Mark</code> field or other custom parameter), you will need to create a new <code>Ifcname</code> type parameter, assigned to the object.
+
| By default, Revit exports the family's type joined with the <code>Type Name</code> value (e.g. <code>Basic Wall:Block Wall - 140</code>). If you enable the <code>Use Type name only for IFCType name</code> option in the export <code>Advanced</code> settings tab, this will be simplified to just the type name (e.g. <code>Block Wall - 140</code>). The IFC requirement is to fill in the <code>Name</code> attribute with the codes used in schedules and annotation tags (e.g. <code>BLK140</code>). In the likely event that this isn't the case (e.g. you are tagging a <code>Type Mark</code> field or other custom parameter), you will need to create a new <code>IfcName[Type]</code> type parameter, assigned to the object, and tag that in your drawings instead of <code>Type Mark</code> or otherwise.
 
|-
 
|-
 
| <code>Description</code>
 
| <code>Description</code>

Revision as of 21:06, 9 September 2020

The following attributes may be filled.

Note that the shared parameter names used for these parameters, such as IfcName[Type], need to have [Type] as a suffix. It may be required to update to the latest IFC exporter, as the one shipped by Revit has a bug where type attributes are ignored.

Attribute Name Required Procedure
Name Yes By default, Revit exports the family's type joined with the Type Name value (e.g. Basic Wall:Block Wall - 140). If you enable the Use Type name only for IFCType name option in the export Advanced settings tab, this will be simplified to just the type name (e.g. Block Wall - 140). The IFC requirement is to fill in the Name attribute with the codes used in schedules and annotation tags (e.g. BLK140). In the likely event that this isn't the case (e.g. you are tagging a Type Mark field or other custom parameter), you will need to create a new IfcName[Type] type parameter, assigned to the object, and tag that in your drawings instead of Type Mark or otherwise.
Description Yes Create a new Ifcdescription type parameter, assigned to the object.
Retrieved from "https://wiki.osarch.org/index.php?title=Revit_setup_for_OpenBIM/Revit_IFC_type_products&oldid=1474"