Difference between revisions of "Revit setup for OpenBIM/Revit IFC type products"
From Wiki.OSArch
(Created page with "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...") |
m (adding categories) |
||
| Line 16: | Line 16: | ||
| Create a new <code>Ifcdescription</code> type parameter, assigned to the object. | | Create a new <code>Ifcdescription</code> type parameter, assigned to the object. | ||
|} | |} | ||
| + | |||
| + | [[Category:Revit]] | ||
Revision as of 17:00, 10 August 2020
The following attributes may be filled.
Note that the shared parameter names used for these parameters, such as Ifcname, 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.
| Attribute Name | Required | Procedure |
|---|---|---|
Name
|
Yes | By default, Revit exports the family's Type Name value. If these values match the codes used in schedules and annotation tags, your Name attribute will be correctly filled. 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 parameter, assigned to the object.
|
Description
|
Yes | Create a new Ifcdescription type parameter, assigned to the object.
|
