Editing Revit setup for OpenBIM/Revit IFC type products
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 2: | Line 2: | ||
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> | + | 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. |
{| class="wikitable" | {| class="wikitable" | ||
Line 11: | Line 11: | ||
| <code>Name</code> | | <code>Name</code> | ||
| Yes | | Yes | ||
− | | By default, Revit exports the family's | + | | 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. |
|- | |- | ||
| <code>Description</code> | | <code>Description</code> |