FAMILY EDITOR GLITCH: Catalog files that use formulas

A simple detail item has been created that is using a formula.In this case it’s a detail item intended to represent a 2D downpipe. The radius parameter controls the circle size for the various type sizes but I wanted drafter’s to have the option of editing the diameter value as well if that was easier for them.

STEP 1: Create the masking region and assign radius constraint

STEP 2: Create parameter link using a formula in Family editor

STEP 3: Create Catalog text file:

STEP 4: Load family into project

STEP 5: Test sizes are correct based on family types created

A = 100mm Diameter

B = 150mm Diameter

RESULT: INCORRECT

STEP 4 REVISITED: Edit Catalog file to include Radius (Since diameter and radius values are interlinked)

STEP 5 REVISITED: Import family into project file

STEP 6: Test sizing

LESSON SUMMARY:

If you wish to control a Revit Catalog family with a parameter that is affected by any formula then all associated parameters that relate to the primary parameter need to reside in the catalog text file.

Please remember to click LIKE or SHARE if this has been a useful tip or a good reminder.

Advertisement

REVIT TYPE CATALOG FAMILIES – ANOTHER EXAMPLE

A Catalog family is a family that relies on a .txt file to define the values for certain parameters within a family. When loading the Catalog family into a Project file Revit® will automatically read the matching “txt” file and create the appropriate family types within the Project file, based on your selection. Catalog families do not save that much file size in my opinion. Their benefits are more about only having the relevant types listed in the Type pull down menu, within the Project file, if appropriate.

The .txt file will tell Revit® what values to apply to the various Type parameters within each family type so that the family types match the properties in the .txt file. A Type Catalog family is used when there are many types within a family and allows the Content creator to edit the defined values directly in the .txt file easily without even going into the Revit® family editor.

NOTE:

• The Catalog .txt file must match the family name exactly and be in the same folder location as the family in order to work. E.g. Family Name: Sculpture_cat.rfa and Catalog File name: Sculpture_cat.txt
• These families must be loaded into a project file using the “File> Load from Library> Load family “option.
• The user does not have to load in all the types within a family and can select which they want to load from the menu list which is automatically displayed by Revit®.
• You are not limited just to length parameter type, you can use text, yes/no and more. 
• When defining a text or using a Yes/ No parameter then use this parameter type and unit format   ##Other##
• Yes/ No parameter values are defined by a numerical value of  0 (Which equates to No)  or 1 (Which equates to Yes)
• ‘_cat’ is a suffix naming conventions that I use to indicate to myself quickly that it’s a catalog family. See example below.

EXAMPLE OF CATALOG FILE FORMAT

E.g. Family name: Sculpture_cat.rfa, Type name: Refers to sculpture type.

STEP 1    

Create a type Catalog file in Notepad where top row lists the relevant catalog parameters. The first parameter is always the Type name which is not entered by any identification, but is followed by a comma, thereafter followed by other parameters. Each parameter is separated by a comma with no space either side of comma. (You can use Excel to create csv file format to copy parameter value script)

Parameters are defined in the following format: Parameter Name##Parameter Type## Unit (If applicable)

See example below.

 STEP 2    

Associate values to each type (One type per row) See example below.

 

STEP 3    

Save the Catalog file as txt file.

E.g. Sculpture_cat.txt and must live in same folder as the Revit® family to work.

 

STEP 4   

When importing the Revit® family the following menu window (above) will pop up allowing you to select which types to import into the Project file.

 This example has a parameter called ‘Top cube’ which is a Yes/ No visibility control. It was defined in the catalog file with 0 & 1 values.

TYPE CATALOG FAMILIES

A Catalog family is a family that relies on a .txt file to define the values for certain parameters within a family. When loading the Catalog family into a Project file Revit® will automatically read the matching “txt” file and create the appropriate family types within the Project file, based on your selection. Catalog families do not save that much file size in my opinion. Their benefits are more about only having the relevant types listed in the Type pull down menu, within the Project file, if appropriate.

The .txt file will tell Revit® what values to apply to the various Type parameters within each family type so that the family types match the properties in the .txt file. A Type Catalog family is used when there are many types within a family and allows the Content creator to edit the defined values directly in the .txt file easily without even going into the Revit® family editor.

Note:

• The Catalog .txt file must match the family name exactly and be in the same folder location as the family in order to work. E.g. Family Name: AD_Broom.rfa and Catalog File name: AD_Broom.txt

• These families must be loaded into a project file using the “File> Load from Library> Load family “option.

• The user does not have to load in all the types within a family and can select which they want to load from the menu list which is automatically displayed by Revit®.

© Copyright Reserved by Michelle Louw (Excerpt from My speaker notes at National Revit Technology Conference 2008.)