By Dennis Collin
I recently posted when visiting offices or talking to delegates about the dangers of using manual text notes. This is because as the text string contents do not automatically relate to properties within the model. The views where text is intended to be used are either notes on a sheet, or the placement of notes on Drafting and Legend Views i.e. non model views.
Instead, a good Revit User will make use of Tag objects. Tag families are text like elements that relate to properties within the Revit model and will automatically update wherever the property is altered. Tags essentially come in two forms, by Category, where specific category information can be displayed or the more General-Purpose Multi-category tag which provides general information or manually defined shared parameters if required.
As I discussed in my previous post, Revit has some built in parameters, but often there is a need to have additional bespoke user defined fields. For this to work with tags, a Shared parameter file needs to be setup and configured to have standard name definitions to use with families and projects.
In the example above, some parameters have been added to a Shared Parameter file. Parameter types can include lengths, for dimensions, number format for identification and bespoke coordinate schedules, single line text for Manufacturer names and descriptions and multi-line text for more lengthy notes and descriptions. Multiline text will allow for notes to spill over several paragraphs and can also be used for client or site addresses.
These parameters can be assigned to family elements and then picked up within the project and show not just in schedule views, but also assigned to Tag families for the labelling of elements within Revit’s Model views.
When creating Tag families for bespoke fields, accessing bespoke parameter names can only be achieved by utilising a Shared Parameter file.