Rhino Layer Standard for Architecture & Spatial Design

A practical Rhino layer management standard for architecture, interior design, exhibition design, and spatial interaction projects.

Developed by INF. STUDIO × Archintera as a public-facing workflow template for small studios, independent designers, and multidisciplinary teams working across Rhino, CAD, Enscape, D5 Render, Twinmotion, Blender, and Unity.

---

Why this exists

Rhino files often become difficult to hand over once they accumulate:

• imported CAD references,
• consultant models,
• copied furniture assets,
• render-only entourage,
• interaction devices and projection zones,
• undeletable Block-related ghost layers.

This repository packages a simple but robust layer logic that makes Rhino models easier to:

1. read,
2. clean,
3. hand over,
4. export,
5. render,
6. and reuse as a studio template.

---

What’s included

• Public layer standard in Markdown.
• PDF version for distribution and onboarding.
• Rhino Python generator that builds the full layer tree automatically.
• Reference logic for architecture, interiors, exhibition tech, rendering, and import cleanup.

---

Quick start

Option 1 — use the script

1. Open Rhino.
2. Run RunPythonScript from the Rhino command line.
3. Select scripts/generate_rhino_layers.py.
4. Save the resulting empty Rhino file as your project or studio template.

Option 2 — read the standard first

• Markdown: docs/Rhino_Layer_Standard_Public.md
• PDF: docs/Rhino_Layer_Standard_Public.pdf

---

Repository structure

docs/
  Rhino_Layer_Standard_Public.md
  Rhino_Layer_Standard_Public.pdf
scripts/
  generate_rhino_layers.py
README.md
LICENSE
.gitignore

---

Core layer logic

00_CTRL        Project controls, grid, levels, boundaries
01_SITE        Site, terrain, roads, paving, exterior objects
02_BUILDING    Main architectural model
03_INTERIOR    Interior architecture, furniture, lighting, details
04_INTERACTIVE Spatial interaction hardware, displays, sensors, trigger zones
05_RENDER      Render-only objects, cameras, lights, entourage
90_REFERENCE   CAD, client models, consultant references
99_TEMP        Incoming imports, temporary archive, cleanup zone

Why 90_REFERENCE and 99_TEMP?

They are intentionally sorted to the end of the layer list.

• 90_REFERENCE is for non-production geometry that should usually be locked, reviewed, and excluded from final export.
• 99_TEMP is for temporary, imported, or archived content that must remain visually obvious and easy to clean.

This leaves the middle of the list open for production systems like:

06_LANDSCAPE
07_LIGHTING
08_MEP
09_FACADE_DETAIL

without pushing references and temporary objects into the main modeling workflow.

---

Workflow principles

1. Production geometry and reference geometry should never be mixed

Formal model objects belong in production layers. Imported CAD, client material, and consultant files belong in 90_REFERENCE.

2. Imported content should pass through a sandbox

Use 99_TEMP > TEMP_Incoming as a quarantine zone before assigning imported or pasted objects to final layers.

3. Block definitions should stay clean

Keep Block internals on Default where possible, so layer deletion and file cleanup remain predictable.

4. Render-only objects should stay separate

People, cameras, lighting rigs, cars, and decorative entourage should not be confused with formal design geometry.

5. Interaction design deserves its own layer family

Screens, sensors, cable runs, trigger zones, and projection cones are spatial systems, not afterthoughts. Treating them as first-class layers makes downstream coordination easier.

---

Best use cases

This standard is especially useful for:

• boutique architecture studios,
• interior and exhibition designers,
• Rhino-first concept design teams,
• cross-platform teams using Mac + Windows,
• spatial interaction and immersive media projects,
• small practices that want cleaner project handoff without moving to a BIM-heavy workflow.

---

Included automation script

The script at scripts/generate_rhino_layers.py will:

• create the full nested layer structure,
• assign a readable color system,
• lock 90_REFERENCE by default,
• set IT_Cone to semi-transparent for spatial coordination.

It is designed for Rhino’s Python environment, which is why rhinoscriptsyntax, Rhino, and System.Drawing are expected imports.

---

Suggested publishing / team usage

• Use the PDF as onboarding or internal reference.
• Use the Markdown as the editable source of truth.
• Use the Python script to create a reusable Rhino starter template.
• Keep your own studio variant private if you need internal naming, file paths, or handoff procedures.

---

License

Released under the MIT License.

---

Credits

Created and maintained by INF. STUDIO × Archintera.

If you adapt this standard for your own practice, attribution is appreciated.