Layer Mapping
Customise the Rhino® layers RAY creates
RAY puts each exported Revit element on a Rhino layer. By default the layer path is:
Project::Category::SubcategoryFor example Tower_A::Walls::Common Edges. The project name is the Revit file name.
To use your own layer structure, create a mapping file.
Where to put the file
Save a plain text file here:
C:\ProgramData\Beam\Mapping.txtRAY reads it on every export. Delete the file to go back to the default structure.
File format
Lines that start with
#are comments. Blank lines are ignored.The first other line is the layer pattern.
Every line after it renames a category.
The pattern line
The pattern is a list of layer levels separated by ::. Each level can mix plain text and any number of keywords in braces.
{Project}
The Revit project name
{Category}
The element's category, for example Walls. Renamed by the category lines below.
{Subcategory}
The subcategory of the geometry
{Family}
The family name
{Type}
The type name
{FamilyAndType}
The family and type, as Family - Type
For example:
gives layers like Revit_Tower_A::Walls::Basic Wall - Exterior 300::Common Edges.
A level can combine keywords, for example {Family}_Type_{Type} gives Basic Wall_Type_Exterior 300.
Levels that come out empty are left out. For example, if an element has no subcategory, its objects go on the level above.
Category lines
Each line after the pattern has the form RevitCategory=LayerName:
This changes how {Category} is printed. Categories without a line keep their Revit name.
Lines without = are ignored. If a category appears twice, the last line wins.
Example
Special cases
Grids and curves and Adaptive Components only use the
{Project}and{Category}levels of the pattern.Edges go on the current layer.
Rooms from Batch Export use the category
Rooms.In Batch Export with Include Design Options as Rhino Layers, elements in a primary design option go under
Project::Design Option::<Option Set>::<Option>, followed by the rest of the pattern.
Last updated