CoD Wiki

Layer Organization, Units & Annotations - Professional Documentation

Layer Management - The Foundation of Organization

Why Layers Matter:
Layers in Rhino are like a filing system for your geometry. They control visibility, editability, appearance, and ultimately determine how organized and professional your file is. A well-layered file can be understood by anyone, edited efficiently, and prepared for different outputs (rendering, fabrication, documentation).

Layer Panel Interface:

Layer Naming Conventions:

Standard Professional Structure:

00_Reference             (imported drawings, images)
01_Site                  (context, terrain)
02_Grid                  (construction grids, axes)
10_2D_Construction       (working curves, guides)
11_2D_Profiles          (final curves for extrusion)
12_2D_Annotations       (dimensions, text)
20_3D_Mass              (basic volumes)
21_3D_Structure         (structural elements)
22_3D_Envelope          (walls, roofs, floors)
23_3D_Details           (hardware, fixtures)
30_Analysis             (studies, alternatives)
40_Make2D               (2D output from 3D)
99_Archive              (old versions, unused)

Industry-Specific Examples:

Architecture:

Product Design:

Jewelry:

Layer Hierarchy & Sublayers:

Layer States Manager:

Advanced Layer Controls:

Units & Tolerance - Precision Settings

Document Units Setup:

Access: File → Properties → Units

Key Settings:

1. Model Units:

2. Distance Display:

3. Absolute Tolerance:

Recommended Tolerances:

4. Angle Tolerance:

Grid Settings:

Access: File → Properties → Grid

Configure:

Best Practices:

Template Management:

Annotations & Documentation

Dimension Tools:

Linear Dimensions:

Radial/Angular:

Dimension Style Configuration:

Access: File → Properties → Annotation Styles

Key Settings:

Creating Custom Styles:

  1. Duplicate existing style
  2. Rename descriptively (e.g., "Fabrication_Dims")
  3. Adjust all parameters
  4. Set as current for new dimensions

Text Annotations:

Text Commands:

Text Formatting:

Professional Annotation Layout:

  1. Title Block Elements:

    • Project name
    • Drawing number/revision
    • Scale notation
    • Date and author
    • Client information

  2. Drawing Notes:

    • General notes layer
    • Numbered lists for specifications
    • Material callouts
    • Fabrication instructions

Hatching & Section Fills:

Commands:

Pattern Types:

Best Practices:

Print Display Settings:

Print Width by Layer:

Print Color Options:

Layout Space:

Detail Views:

File Management Best Practices

Naming Conventions:

ProjectName_PartName_Version_Date.3dm
Example: ChairDesign_BackRest_v03_2025-08-28.3dm

Version Control:

File Organization Structure:

Project_Folder/
├── 01_Reference/
│   ├── Images/
│   ├── Drawings/
│   └── Specifications/
├── 02_Rhino_Files/
│   ├── Working/
│   ├── Archive/
│   └── Templates/
├── 03_Exports/
│   ├── STL/
│   ├── DXF/
│   └── PDF/
└── 04_Renders/

Purge & Cleanup:

Block Instances:

Before you hand a file to someone else

Prepare the file so another person can understand what is current, what the dimensions mean, and what you need them to do.

  1. Save a working checkpoint. Keep the editable project and important construction geometry before making a submission copy.
  2. Identify the intended result. Say whether the file is for feedback, a drawing, rendering, laser cutting, or 3D printing. The right output depends on its purpose.
  3. Make the current geometry obvious. Use clear layers and separate the intended output from studies, reference objects, duplicates, and earlier versions.
  4. Check units and a known dimension. Write down the units and one expected overall dimension. After exporting, reopen or import the output in a separate file and check that dimension again.
  5. Distinguish full-size design from a physical model. Keep the full-size design intact. If you create a scaled fabrication copy, name it clearly and record its intended finished dimensions.
  6. Include dependencies when needed. If a collaborator needs to edit or render the project, include the relevant linked images, textures, and references rather than assuming the main file contains everything.
  7. Give the handoff a clear name. Include the project, part or sheet, and revision so people can distinguish it from an earlier submission.

Changing the units in Rhino can prompt you to scale the geometry. Read that choice carefully and verify a known dimension afterward. See McNeel's units guidance.

For fabrication, also follow the current preparation instructions for laser cutting or 3D printing. An organized file still needs the checks required by its intended process.

A short note to send with the file:

This is revision __ of __. It is intended for __. The file units are __, and the finished output should measure __. The current geometry is on __. I need help with / would like feedback on __.

Quick Reference Card

Layer Shortcuts:

Annotation Shortcuts:

Organization Commands: