Revit Type Catalogs
As we continue to test more Revit Families with our FAR Designer we have come across some very interesting items related to creating Revit Type Catalogs.
Here are some examples of items we found that I would like to present as discussion points and encourage your feedback:
- A Revit Type Catalog included Parameter Values using simple equations for a manufacturer and/or other text items where no equation was required. The parameters are not part of the text file, but part of family. It is my understanding that Revit will add those Parameter Values when importing into the Revit Project File which eliminates the need to have Revit evaluate an equation that is not required in a Revit Type Catalog. However, if you do not use Revit Type Catalogs, then it is appropriate to take the approach of including Parameter Values using simple equations.
- Another Revit Family we tested included Parameters with Values that were determined by an equation and they were trying to place those Parameters into Revit Type Catalog text file. I question why anyone would consider doing this as any Parameter that has an equation should let Revit determine the Value.
- Another Family we tested had an Instance Parameter in the Type Catalog and Instance Parameters should not be in Revit Type Catalogs.
- We also tested a Revit Type Catalog that had 170 Types and 45 Parameters within the Type Catalog. I question the size and feel it should have been broken down for ease of use, as going through 170 Types is a lot to search when looking for what you need.
I can fully understand why architects do not trust what they are downloading when there are such inconsistencies, even with something as trivial as creating Revit Type Catalogs.
It is my opinion that a 'best practice' approach should be taken into account when creating Revit Type Catalogs.