BIM Workflow Guide
BlenderGIS to ArchiCAD Workflow: Real Terrain in Your BIM Projects (2026)
Site context makes or breaks an architectural project. Instead of modeling terrain by hand from a contour PDF, pull real elevation and building data with BlenderGIS, prepare it for CAD, and drop a georeferenced site model into ArchiCAD as native objects. This guide covers the full 2026 pipeline: import, cleanup, units and scale, layered export, and the ArchiCAD import itself.
The idea in one sentence: BlenderGIS fetches the GIS data and builds the meshes, Blender is the cleanup bench, and ArchiCAD receives the finished site model as lightweight, correctly scaled objects. Each tool does what it is best at.
The Workflow in Six Steps
- Install BlenderGIS. Grab the .zip from our download page (do not unzip it), then in Blender go to Edit > Preferences > Add-ons > Install, enable 3D View: BlenderGIS, and set a cache folder. Details are in the install guide.
- Frame your site on a basemap. GIS menu > Web geodata > Basemap, then position the 3D view over your project site. MapTiler requires a free API key (required since 2022) — see the MapTiler key guide if tiles stay blank.
- Import the terrain. Download SRTM elevation for the area or import your own DEM/GeoTIFF; BlenderGIS triangulates a terrain mesh from it. See creating 3D terrain from a DEM for a deeper look.
- Import OSM context. Query the Overpass API for buildings, roads, and water inside your extent, with extrusion enabled so footprints rise using height and building:levels tags where they exist.
- Clean and organize. Decimate the terrain, merge duplicate vertices, fix normals, and sort everything into layers: terrain, buildings, roads.
- Export and merge into ArchiCAD. Export each layer as FBX or OBJ, then import them into ArchiCAD as objects with matching units.
Before You Export: Units, Origin, and Mesh Cleanup
Get this section right and everything downstream just works. Get it wrong and your terrain lands kilometers from the ArchiCAD origin — or at the wrong size.
- Blender works in meters by default. BlenderGIS preserves real-world scale at 1 unit = 1 meter. Keep it that way — do not rescale the scene.
- Recenter the origin. BlenderGIS places geometry at true projected coordinates (Web Mercator, EPSG:3857) — millions of meters from zero, which ArchiCAD handles poorly. Move all site geometry near Blender’s world origin (0, 0, 0) before export, and write down the offset so you can restore true coordinates later if needed.
- Apply all transforms. Ctrl+A > All Transforms before export, so scale and rotation are baked into the geometry.
- Decimate the terrain. SRTM-derived Delaunay meshes are dense. Use the Decimate modifier to reach the lightest mesh that still shows the landform clearly.
- Merge by distance and fix normals. OSM imports contain duplicate vertices (Mesh > Clean Up > Merge by Distance), and inside-out faces shade wrong — recalculate normals outward in Edit Mode.
- Keep buildings low-poly. Extruded footprints are massing models; flat shading and simple geometry keep the ArchiCAD file responsive.
Match units on import: in ArchiCAD’s Merge dialog, confirm the unit setting is meters, then measure a known building footprint as a sanity check.
Export in Layers and Bring Them into ArchiCAD
Do not export the whole site as one mesh. Separate layers let you toggle context on and off, assign different fills and materials, and isolate heavy geometry.
| Layer | Format | Why separate |
|---|---|---|
| Terrain mesh | FBX or OBJ | Heaviest layer — keep it toggleable |
| Buildings (extruded) | FBX or OBJ | Distinct fills and pens for massing diagrams |
| Roads, water, context | OBJ | Lightweight reference for site plans |
In ArchiCAD, bring each file in through File > Interoperability > Merge — it arrives as a library object you can place, move, and assign materials to. Position every layer at the same project origin and they will align exactly.
What about IFC? Blender can export IFC via the BlenderBIM add-on, but be honest about the limits: raw GIS terrain does not map cleanly onto IFC entities and georeferencing through IFC is fiddly. Building masses can go out as generic IfcBuildingElementProxy objects — fine for early coordination, not construction documentation. For context and massing, FBX/OBJ as objects remains the reliable route in 2026.
Keep learning: once the site model is in place, the next skill is turning it into presentation imagery. Domestika’s architectural visualization courses teach rendering and storytelling techniques that pair well with a real-terrain base. For Blender-side rendering techniques, see architectural visualization with BlenderGIS.
If anything misbehaves — blank basemaps, failed imports, missing panels — the troubleshooting hub covers the common failure modes.
Frequently Asked Questions
Can ArchiCAD open Blender .blend files directly?
No — ArchiCAD has no native .blend importer. Export FBX or OBJ from Blender and bring it in as a library object via File > Interoperability > Merge.
What scale should I export the site model at?
Keep Blender’s default meters: BlenderGIS preserves real-world scale at 1 unit = 1 meter. Apply all transforms before export and confirm ArchiCAD’s import dialog is also set to meters.
Why does my terrain land far from the ArchiCAD origin?
BlenderGIS geometry sits at true projected coordinates (Web Mercator, EPSG:3857) — millions of meters from zero. Recenter it near Blender’s world origin before exporting, and record the offset.
How do I keep the ArchiCAD file from getting slow?
Decimate the terrain, keep extruded buildings low-poly, merge duplicate vertices, and export terrain, buildings, and roads as separate files so heavy layers can be toggled off.
Do I need an API key for the basemap step?
For MapTiler imagery, yes — a free API key has been required since 2022. See the MapTiler key guide for setup.
Is BlenderGIS really free?
Yes. BlenderGIS is open source under the GPL-3.0 license with no paid tier. The latest release is v2.2.15 (December 2025), available from our download page.