This guide walks the full arch-viz workflow: import site terrain and OpenStreetMap buildings as context, run sun and shadow studies with Blender’s built-in tools, render in Cycles, and polish in post — plus an honest note on what GIS data can and cannot promise.

Build real site context: terrain + neighboring buildings

Frame the site on the map, import elevation for terrain and a satellite basemap for visual reference. Then import OpenStreetMap buildings — footprints extrude to their mapped heights where height or levels tags exist, giving you an instant urban massing model around your plot.

Drop your design into the middle of that context. Give the surroundings muted, simple materials and keep full detail for the proposal itself, so the design reads clearly against the real city. Keep the context lightweight: decimate the terrain mesh and merge OSM buildings by material so viewport navigation stays smooth while you iterate on the design. For a deeper OSM import walkthrough see /import-osm-buildings-blender/; if your design iterates in ArchiCAD, /blendergis-archicad-workflow/ covers the round trip between the two tools.

Sun and shadow studies clients understand

Blender’s built-in Sun Position add-on places the sun from real latitude, longitude, date, and time — no guesswork, no faked lighting angles. That makes the classic client deliverables straightforward: morning, noon, and evening views of the proposal, plus summer and winter solstice comparisons that show overshadowing on neighboring plots honestly.

BlenderGIS adds geo-referenced photo cameras, which help you match render views to actual site photographs. Before-and-after presentations built on matched views are far more persuasive than floating beauty shots — the client sees their site, not just your building. Export the study as an image sequence or a small contact sheet: clients grasp a full day of shadows faster from six thumbnails than from a written description.

Rendering in Cycles, polishing in post

Keep the material strategy simple: full PBR materials on the hero building, flat and dark on the GIS context so it supports without competing. Cycles handles the rest — enable denoising, keep samples moderate, and simplify context geometry to protect render times on large sites.

In post, grade in Blender’s compositor first, then finish hero stills with Topaz Photo AI for noise cleanup and Gigapixel AI upscaling. It is an inexpensive route to print-ready presentation boards from modest render settings — render at 2K, deliver at 4K-plus without re-rendering.

Know the limits, then level up

An honest note on precision: OpenStreetMap is community-mapped, so building positions and heights are approximate. BlenderGIS is a concept and schematic-design tool — excellent for massing, site context, and client presentations, but never promise engineering accuracy. Verify against survey data before anything approaches construction documentation.

Once the workflow clicks, the fastest way to raise render quality is structured learning: Domestika’s architectural visualization courses cover lighting, composition, and storytelling that turn raw site data into winning presentations. Grab the add-on itself from /download/, and if anything misbehaves, /troubleshooting/ has you covered.

Frequently asked questions

Is BlenderGIS accurate enough for construction documents?

No. It is a concept and schematic-phase tool. OpenStreetMap geometry is community-sourced and approximate — always verify with survey data before construction documentation.

Can I import my ArchiCAD model into this workflow?

Yes. Export your design from ArchiCAD and bring it into Blender alongside the GIS context. See /blendergis-archicad-workflow/ for the round trip.

Do neighboring buildings import with correct heights?

Only where OpenStreetMap contributors mapped height or levels tags; elsewhere they arrive as flat footprints you can scale using local knowledge or reference photos.

Do I need API keys for basemaps?

Yes — free MapTiler and OpenTopography keys have been required since 2022. Setup guides: /maptiler-api-key-guide/ and /opentopography-api-key-guide/.

Which Blender versions are supported?

Blender 2.83 LTS at minimum, through 5.0 and later. The current release is BlenderGIS v2.2.15, published December 20, 2025.

Can I use BlenderGIS output in paid client work?

The add-on is GPL-3.0, free for commercial use. Respect data licenses separately — OpenStreetMap requires attribution under ODbL.