Skip to main content

Lesson 02 - Python in the AEC Ecosystem

Understand where Python fits in the "Big Picture" of design software. The Reality: Python is the universal connector in a fragmented industry.

Introduction

We moved from drafting (lines) to CAD (digital lines) to BIM (databases).

The modern architect manages data. Costs. Materials. Schedules. Quantities. Coordination rules.

The problem? Our software creates data well. Manipulating it the way you need? Not so much.

Revit, Archicad, Navisworks store enormous amounts of information. But when you want custom logic, batch rules, or project-specific checks, you hit friction.

That's where Python enters the picture.

Lesson Overview

This section contains a general overview of topics you will learn in this lesson.

  • Understand why Python instead of C#
  • Learn where Python lives in AEC software
  • See Python working inside tools (Revit, Rhino, Blender)
  • See Python working between tools (Excel ↔ Revit, Web ↔ Design)
  • Understand the difference between Python grammar (logic) and vocabulary (APIs)

Why Python and Not C#?

Most professional software (Revit, AutoCAD) is written in C#.

If C# is the industry standard, why aren't we learning that?

Think of C# like Construction Documents. Incredibly precise, structured, and "safe" — but it takes time to set up. You have to define every single detail before you can even start. It's designed for software engineers building heavy-duty applications.

Python is like a napkin sketch. It's designed for speed and readability. You have an idea, type it out, see the result immediately.

The Trade-off

  • C# is faster for the computer to read (microseconds)
  • Python is faster for you to write (minutes vs. hours)

As architects, we aren't building the next Revit from scratch. We just want to automate a boring task before lunch.

Python is the tool that lets you "sketch" that solution quickly.

Where Does Python Live?

Python is unique because it's platform-agnostic. It lives everywhere.

Inside the Tools (Embedded)

These are scripts that run inside your design software to handle tasks the standard buttons can't.

Revit (via Dynamo or pyRevit)

The Pain: You need to create 50 sheets for a new project and name them based on a client's Excel standard. Doing this manually takes an hour.

The Python Fix: Script reads Excel. Creates all 50 sheets. 4 seconds.

Rhino (via Grasshopper/GhPython)

The Pain: You want to create a facade pattern that changes randomly, but standard Grasshopper "spaghetti" is getting messy and slow.

The Python Fix: Simple loop generates thousands of unique panels efficiently. Canvas stays clean.

Blender (Native)

The Pain: You need to render 20 different camera angles for a client presentation overnight.

The Python Fix: Script moves camera, renders, saves, moves to next spot. While you sleep.

Between the Tools (Interoperability)

Python acts as the "Universal Translator." Software A doesn't speak to Software B, but they both speak Python.

Excel ↔ Revit (The Data Bridge)

Scenario: Your Room Data Sheets (finish requirements, occupancy loads) live in Excel.

The Python Fix: Script pulls data from Excel and pushes it into Revit Room Parameters automatically. No manual typing.

Web ↔ Design (The Context Fetcher)

Scenario: You need site data (weather stats, topography, nearby buildings) for a new site.

The Python Fix: Script connects to Google Maps or OpenStreetMap APIs to download 3D site context directly into Rhino.

Civil 3D ↔ Structural Analysis (The Calculator)

Scenario: Site terrain changed in Civil 3D. You need to re-check column foundation depths.

The Python Fix: Script reads new terrain mesh and updates column heights in analysis software immediately.

The Core Concept: Grammar vs. Vocabulary

This is the most important concept to grasp before we write code.

What Stays the Same (The Grammar)

Whether you're in Dynamo, Grasshopper, or a standalone script, the Python logic is identical:

  • Variables: Storing data (e.g., wall_height = 3000)
  • Loops: Repeating actions (e.g., "For every sheet in this list...")
  • Conditionals: Making decisions (e.g., "If the room area is < 10 m²...")

What Changes (The Vocabulary)

The inputs and outputs depend on the software you're using.

  • In Revit: You speak the "Revit API" (walls, windows, sheets)
  • In Rhino: You speak "RhinoCommon" (NURBS, meshes, points)

We'll cover these later.

The key takeaway: learn the grammar once. Apply it everywhere.

Assignment

  1. List the three main software tools you use most often (e.g., Revit, Rhino, Excel, Navisworks)
  2. For each tool, write down one repetitive task you wish you could automate
  3. Think about whether that task happens inside one tool or between multiple tools

Knowledge Check

The following questions are an opportunity to reflect on key topics in this lesson.

Additional Resources

This section contains helpful links to related content. It isn't required, so consider it supplemental.

Updated on Mar 27, 2026