Custom 3D topographic maps have become a small industry: several workshops now sell made-to-order relief maps as home decor and gifts, which proves the demand is real. The DIY route exists because the raw materials — elevation data and 3D software — are free and open. This guide walks the whole path, and stays honest about what it costs you in time.

Buy it or build it: the honest comparison

A commissioned 3D map typically costs €39–199 depending on size, material, and finish. You pick a location on their website, someone else does the work, and a finished piece arrives at your door. The trade-off: you accept their choice of resolution, color scheme, and framing, plus shipping time and cost.

The DIY route costs nothing but your time — about one to two hours of hands-on work following the workflow below. You can map literally any place on Earth, in any style, at any size. The trade-off: you do the work, and your first attempt will probably not be gallery-perfect. For a gift with a hard deadline, buying is the sane choice. For a weekend project, or a gift where “I made this myself” is the point, build it.

Step 1: Pick a place that means something

A 3D map works as art because the terrain carries a story. Choose somewhere with real relief — mountains, coastlines, canyons, river valleys — and a personal connection: your hometown, a trail you hiked, your honeymoon spot, the city you just moved to. That connection is also what makes it a gift: a housewarming map of the new neighborhood, a wedding gift of where the couple met, an anniversary map of the summit.

Frame the area tightly. A smaller extent with crisp relative detail looks far better on a wall than a huge area where the mountains dissolve into noise. Roughly a 20–60 km square is the sweet spot for recognizable terrain.

Step 2: Build the terrain with BlenderGIS

BlenderGIS (v2.2.15, released 2025-12-20, GPL-3.0, by domlysz on GitHub) is a free Blender add-on that imports real geographic data. Use it to fetch a digital elevation model (DEM) of your chosen area and generate a true-to-scale terrain mesh. The full import workflow is covered in our guide to creating 3D terrain from DEM data: define your area of interest, import the elevation grid, and let the add-on build the mesh. If you want a realistic look, import a satellite basemap of the same extent and drape it over the relief.

Step 3: Choose a style

Three styles consistently look great on a wall:

• Realistic: satellite imagery over shaded relief. Instantly recognizable, reads as “a real place.”
• White plaster: a single matte-white material with soft studio lighting — the minimalist gallery look. Our white porcelain city maps guide covers the technique. It also hides low-resolution DEM artifacts and prints beautifully.
• Vintage topographic: hypsometric tinting — greens to browns to white by elevation — for a classic map feel.

For a gift, the white plaster style is the safest choice: it matches any interior and never looks dated.

Step 4: From screen to wall

Two ways to finish. Option one: export the mesh as STL and 3D-print it — the complete printing workflow is in our guide to 3D-printing terrain models. Mount the print on a backing board or float-frame it with a spacer so the relief casts real shadows.

Option two costs nothing: render the styled terrain at high resolution (4K or higher) from a slightly oblique top-down view and have it printed as a poster, or print it yourself. A render is also the fastest route when the gift deadline is this weekend.

One tip for wall display: exaggerate the vertical scale slightly (1.2–1.5x). Real terrain at true scale can look surprisingly flat when it is only a few centimeters deep; a gentle exaggeration reads better on a wall and still looks honest.

A realistic budget: time and money

Hands-on time: about 30 minutes to build the terrain, 30 minutes to style and light it, 30 minutes to export and test. Call it one to two hours for your first map, under an hour once you have done it before. Money: zero for the digital workflow — Blender and BlenderGIS are both free and open source. A 3D print costs whatever your printer or a local print service charges; a poster render costs the price of the print. Compare that with €39–199 for a commissioned piece, and decide which currency — money or an afternoon — you would rather spend.

Frequently Asked Questions

Is a DIY 3D map really free?

The software is free: Blender and BlenderGIS (GPL-3.0) cost nothing, and elevation data is freely available. You only pay if you 3D-print the result or order a poster print.

How long does it take to make a DIY 3D relief map?

Expect one to two hours of hands-on work for your first map: roughly 30 minutes to build the terrain, 30 to style it, and 30 to export or render. Repeat maps take under an hour.

Do I need a 3D printer?

No. You can render the styled terrain as a high-resolution image and frame it as a poster. Printing is optional.

Which is better: DIY or a paid service like MapKraft?

Paid services (MapKraft from 59 euros, HoldYourMap 39 to 129 euros) save you time and arrive ready to hang. DIY is free, fully customizable, and takes one to two hours. Choose based on whether you value your time or your money more.

What places work best for 3D map wall art?

Places with real relief – mountains, coastlines, canyons, river valleys – plus a personal connection: your hometown, a summit you climbed, a honeymoon spot. Frame the area tightly, around 20 to 60 km across, for the best detail.

What data does BlenderGIS use to build the terrain?

BlenderGIS imports digital elevation model (DEM) data such as SRTM and builds a true-scale terrain mesh from it. Our guide to creating 3D terrain from DEM data walks through the import step by step.

How custom services work in BlenderGIS

Basemap sources live in a file called servicesDefs.py inside the BlenderGIS add-on folder, and the add-on’s official wiki documents adding your own service there in a JSON-like syntax. Each service definition has the same shape:

• A name and description — what shows up in the basemap source list.
• A service type — WMS, WMTS, or TMS (slippy-map XYZ tiles).
• A grid — the tile grid the service uses, typically WM for Web Mercator (EPSG:3857), which is what almost every public tile service speaks.
• Layers — the layers you want available, each with its format (png or jpeg), style, and zoom range.
• A URL template — for WMS, the GetMap request parameters with placeholders BlenderGIS fills in per tile ({CRS}, {LAY}, {BBOX}, {WIDTH}, {HEIGHT}); for TMS, the classic {z}/{x}/{y} tile URL pattern.
• A referer — some tile servers check the HTTP referer and return blank tiles without the right one.

A minimal TMS/XYZ definition looks like this (edit names and URLs to match your service, then reinstall or re-enable the add-on so it reloads the file):

"MY_TILES" : {
    "name" : 'My Tile Service',
    "description" : 'Organization name',
    "service": 'TMS',
    "grid": 'WM',
    "layers" : {
        "TOPO" : {"urlKey" : 'topo', "name" : 'Topo', "description" : '', "format" : 'png', "style" : '', "zmin" : 0, "zmax" : 18}
    },
    "urlTemplate": {
        "BASE_URL" : 'https://tiles.example.org/topo/{z}/{x}/{y}.png'
    },
    "referer": "https://tiles.example.org/"
}

For a WMS service the URL template instead builds the full GetMap request: base URL plus SERVICE=WMS, VERSION, REQUEST=GetMap, and the {CRS} / {LAY} / {FORMAT} / {STYLE} / {BBOX} / {WIDTH} / {HEIGHT} placeholders. Copy the structure of a working WMS definition from the file and change the values — do not invent the key names.

Troubleshooting the common failures

Gray or blank tiles. This is the most common symptom and it almost always means the server refused the request rather than the geometry being wrong. Check the referer first (some servers require it), then open Blender’s system console and look for the “Invalid tile data” debug line — it prints the exact URL BlenderGIS requested. Paste that URL into a browser: if the browser shows the tile, the server accepted the request and the problem is on the BlenderGIS side (timeout, cache); if the browser also fails, fix the URL parameters.

URL returns an error in the browser. Walk the GetMap parameters one by one: layer name spelled exactly as the server’s GetCapabilities advertises, supported CRS (EPSG:3857 works for nearly everything public; some national geoportals only serve their local projection), and an image format the server actually offers. Get the layer’s GetCapabilities XML and read what it supports — guessing parameter values is how afternoons disappear.

Projection mismatch. BlenderGIS works in Web Mercator for the map view and reprojects on export. If your service only serves a local projection (common with government WMS endpoints), tiles may not align or may fail entirely. Prefer services that offer EPSG:3857, or accept that the source will need pre-tiling into Web Mercator outside Blender.

Authentication required. Some WMS services accept an API token baked into the URL (a query parameter), and those can work as custom definitions — just put the token in the base URL. Services needing headers, cookies, or interactive login are generally not workable through the add-on’s tile fetcher.

Tiles show but resolution is poor. You are likely capped by the layer’s zmax or by the zoom you exported at. Raise zmax to what the service actually serves (check its docs), and use the basemap’s lock-extent trick (L key) to force higher-zoom tiles for your chosen area. If the built-in sources are failing for you instead, our satellite maps not showing guide covers those fixes.

Finally: attribute your sources. Public tile services are free to use but almost all require or appreciate credit — put the provider’s name in your renders, videos, and project credits.

Where is the servicesDefs.py file?

Inside the BlenderGIS add-on folder in your Blender add-ons directory (for example, under Blender’s scripts/addons/blendergis). Back it up before editing, add your service definition in the same JSON-like syntax as the existing entries, then reinstall or re-enable the add-on so it reloads the file.

Which service types can I add?

WMS, WMTS, and TMS (slippy-map XYZ tiles), per the add-on’s official basemap documentation. Plain XYZ tile URLs are the easiest to get working; WMS needs the GetMap parameter template done exactly right.

Can I add a WMS that needs a login or API key?

If the key can be embedded as a URL query parameter, yes — put it in the base URL of your definition. Services that require HTTP headers, cookies, or interactive login are generally not supported by the add-on’s tile fetcher.

Why do I get gray tiles from a URL that works in my browser?

The server is likely rejecting the request for a non-URL reason: a missing or wrong HTTP referer is the classic cause. Check the system console for the exact requested URL, verify the referer field in your definition, and confirm the server does not block non-browser clients.

What projection should the service support?

EPSG:3857 (Web Mercator) is the safest — it is what nearly all public tile services offer and what the add-on’s map view expects. Services limited to a local projection may not align or may fail entirely.

How do I get higher-resolution tiles from my custom source?

Set the layer’s zmax to the highest zoom the service genuinely serves, then in the basemap view lock the extent (L key) and zoom in — the add-on downloads tiles from the higher zoom level for the same area.

An establishing shot has one job: orient the viewer. When it shows the actual place your story takes place in, it does double duty — geography becomes production design. With BlenderGIS you pick the real location, and Blender renders it with cinematic control over time of day, weather, and camera. Here is the workflow from location scout to final frame.

Step 1: Scout and build the real location

Start by choosing the exact spot. BlenderGIS’s basemap view lets you scout visually before importing anything — frame the area you want the audience to recognize, whether it is a mountain pass, a coastline, or a city skyline.

Then build the two layers that make a shot read as a place:

• Terrain. Import elevation for the area and generate the mesh, following our guide to creating 3D terrain from DEM data. For landscape shots the terrain is the star; spend your polygon budget here and consider a vertical exaggeration of 1.2–1.5× if the relief looks flat on screen.
• Buildings and context. For urban locations, import OpenStreetMap buildings as described in our guide to importing OSM buildings into Blender. You rarely need full detail — at establishing-shot distance, extruded footprints with simple materials read perfectly.

Drape a satellite basemap over the terrain as the base texture. It will not hold up to close inspection, but an establishing shot lives at wide distance, where it reads as photographic.

Step 2: Light it like a cinematographer

What separates a flat GIS screenshot from a cinematic establishing shot is almost entirely lighting and atmosphere:

• Shoot golden hour. Set Blender’s sun lamp low on the horizon (use the Sun Position add-on for accurate sun angles at your location and date). Long shadows and warm light do most of the cinematic work.
• Add atmosphere. A subtle volume scatter in the world shader or a simple mist pass in the compositor gives aerial perspective — distant ridges fade blue, exactly like real haze.
• Choose the lens deliberately. Wide lenses (24–35 mm) exaggerate scale and drama; a long lens (85 mm+) compresses a skyline into the classic flat establishing frame. A slow camera push-in over 3–5 seconds turns a still into a title-sequence shot.
• Grade it. A filmic color transform, slight vignette, and a contrast S-curve in the compositor unify the render with the rest of your footage.

Step 3: Enhance for photorealism (optional)

Satellite basemaps are low resolution, and wide renders can look soft next to real camera footage. If the shot must intercut seamlessly with filmed material, run the final render through an AI upscaler and enhancer — Topaz is the established tool in video pipelines for exactly this: sharpening soft renders and adding fine detail so a 3D establishing shot survives at full video resolution. Use it selectively on hero frames rather than every frame of an animation to keep render times sane.

Then cut the shot into your timeline and trim it to what establishing shots are: 2–5 seconds, just long enough to orient the viewer before the story begins.

Honest limits of this approach

This pipeline is excellent for wide shots of real places, but know its edges. Rural areas may have sparse OSM building data — check coverage before committing to an urban shot. Satellite textures stay soft up close, so keep the camera wide. And because the geometry comes from open data, it reflects the map’s last update, not today’s construction site. For the opening 3 seconds of a scene, these limits rarely matter; for a close-up hero shot of a specific building, they do.

Frequently Asked Questions

What are establishing shots in video production?

Wide opening shots that show the audience where a scene takes place — a city skyline, a mountain valley, a coastline. They orient the viewer before the story moves to closer shots, and they are usually only 2–5 seconds long.

How can I make an establishing shot of a real location for free?

Combine BlenderGIS (free, GPL-3.0) with Blender (free): import real elevation and OpenStreetMap buildings of the location, light it cinematically, and render. You get the actual place your story happens instead of generic stock footage.

What data do I need for a 3D establishing shot?

Two layers: DEM elevation data for the terrain (see our DEM terrain guide) and OpenStreetMap building footprints for urban context (see our OSM buildings guide). A satellite basemap draped over the terrain provides the photographic base texture.

How do I make a GIS render look cinematic instead of flat?

Low golden-hour sun, atmospheric haze for aerial perspective, a deliberate lens choice (wide for drama, long for classic flat frames), and a filmic grade in the compositor. Lighting and atmosphere do most of the work — the geometry can stay simple.

Can I animate the establishing shot?

Yes. A slow 3–5 second camera push-in turns a still render into a title-sequence shot. Keyframe the camera on a straight or gently curved path and render the short clip for your timeline.

Why do my renders look soft next to real footage?

Satellite basemaps are low resolution, so wide renders can look soft at full video resolution. An AI upscaler like Topaz sharpens and enhances hero frames so 3D establishing shots intercut cleanly with filmed material.

If you have ever wondered how studios produce those pristine all-white urban renders for bids and public presentations, the pipeline is simpler than it looks. The heavy lifting is the data: accurate building footprints with heights, placed at their true locations. BlenderGIS fetches that from OpenStreetMap in minutes. Everything after that is one material, one light rig, and one camera.

Step 1: Import real building footprints

The whole style depends on having every building in the right place at roughly the right height — drawing them by hand is not an option at city scale. Use BlenderGIS to query OpenStreetMap for the buildings inside your area of interest and import them with extrusion turned on. Where mappers have recorded height or building:levels tags, footprints rise to their real-world height automatically. The full data-import workflow is covered in our guide to importing OSM buildings into Blender.

A few practical notes before you style anything:

• Choose the extent carefully. Porcelain maps look best with a defined edge — a district, a downtown core, a campus. Query a rectangle with clear boundaries rather than “as much city as possible”.
• Fill missing heights. Buildings without height tags import as flat footprints. Select them, check typical heights for the block, and extrude them to a plausible value. A district where half the buildings are flat will break the illusion.
• Merge and clean. Join all building meshes into one or two objects, merge duplicate vertices, and delete any import artifacts. At city scale this keeps the scene manageable.

Step 2: The porcelain material and ground

The material is deliberately plain. On the buildings, use a Principled BSDF shader with a pure or near-pure white base color, roughness around 0.4–0.5, and a small amount of subsurface scattering in white to get that soft, ceramic light bleed on edges. Resist the urge to add detail: windows, doors, and facade textures are the enemy of this style. One material, assigned to every building.

The ground matters as much as the buildings. Place a large plane slightly below street level in a light neutral gray — just dark enough that the white buildings separate from it, just light enough that the whole image stays bright and calm. If you imported streets from OSM, you can keep them as a subtle darker inlay, but many artists delete them entirely; the floating-white-blocks-on-soft-ground look is the style’s signature.

Step 3: Soft studio lighting and the aerial camera

White-on-white scenes punish harsh lighting: everything blows out or goes muddy. Build a soft three-point setup instead:

• One large area light as the key, scaled up so shadows fall soft, positioned like late-morning sun.
• A weaker fill from the opposite side, no shadows, just enough to lift the dark faces.
• A gentle rim or back light to separate rooftop edges from the background.

Turn on ambient occlusion at low strength for contact shading where buildings meet the ground. Render in Cycles; Eevee can preview the look but Cycles’ light bounce sells the ceramic feel.

For the camera, use a long focal length (60–100 mm) from a high angle — a near-isometric aerial view. It flattens the city into a readable diagram, which is exactly what this aesthetic is for: reading urban form, not sightseeing. Keep the horizon line out of frame or let it dissolve into a soft light-gray background; a visible sky would turn it back into a “normal” render.

Porcelain vs. photoreal: when to use which

This style is not a substitute for photorealistic arch-viz — it is a different tool for a different moment in a project. A porcelain massing render reads as diagrammatic and honest: it shows form, density, and skyline without pretending to show the finished facade. That is precisely why juries, planners, and investors like it at early stages — nothing looks falsely finished.

Use the white porcelain look for: massing studies, competition boards, investor one-pagers, and public consultation material where you want feedback on form, not finishes. Switch to photoreal rendering — the full BlenderGIS architectural visualization pipeline with real materials, satellite textures, and Cycles lighting — when the design is fixed and you need to sell the final experience. Many studios deliver both: porcelain for the bid, photoreal for the brochure.

Frequently Asked Questions

What is the “white porcelain” city render style?

A stylized architectural rendering approach where an entire city or district is shown as smooth white 3D blocks on a neutral ground, mimicking a physical architect’s massing model. It communicates urban form and density without textures, and it is popular for competition entries, bids, and planning presentations.

How do I get real building footprints into Blender?

BlenderGIS queries OpenStreetMap and imports buildings as georeferenced geometry, extruded to their mapped heights where height or building:levels tags exist. The full workflow is in our guide to importing OSM buildings into Blender.

What material makes buildings look like porcelain?

A Principled BSDF shader with a near-white base color, roughness around 0.4–0.5, and slight subsurface scattering gives the soft ceramic edge glow. The key is restraint: no windows, no facades, no color variation — one uniform material across the whole city.

Why do some of my buildings import flat?

Those buildings lack height or building:levels tags in OpenStreetMap. Select the flat footprints and extrude them manually to a typical height for the area. You can also improve OSM data for everyone by adding the missing tags on openstreetmap.org.

Should I render porcelain maps in Cycles or Eevee?

Use Cycles for the final render — its light bounce and soft shadows are what sell the ceramic feel on all-white scenes. Eevee is fine for previewing the composition while you work.

Is white porcelain a replacement for photoreal arch-viz?

No — it is a different deliverable for a different stage. Porcelain reads as diagrammatic and honest, ideal for massing studies and early bids. Switch to the photorealistic architectural visualization pipeline when the design is final and you need to sell the finished experience.

This guide covers a practical pipeline for environment artists: pull terrain and OpenStreetMap data with BlenderGIS, reduce it to game-friendly polycounts, bake the detail into textures, and export clean FBX files to Unreal Engine or Unity — with collision and large-world streaming along the way.

Why real-world terrain wins for open worlds

Real watersheds beat noise. Nature already solved erosion, drainage, and ridgeline logic — a real DEM gives you valleys and slopes that feel right without weeks of sculpting. OpenStreetMap adds the human layer: streets, rivers, parks, and building footprints that make urban blockouts believable from day one. The biggest win is speed: a full landscape blockout with real geography can land in an afternoon instead of a month.

One honest caveat: raw GIS meshes are far too dense for real-time rendering. Treat BlenderGIS output as a high-quality base to optimize — not a final asset. The pipeline below assumes you will decimate, retopologize, and bake before anything reaches an engine.

The pipeline: GIS data to game-ready mesh

Seven steps from map to engine:

1. Install BlenderGIS. Get the add-on from /download/ — install the .zip without extracting it — then in Blender go to Edit > Preferences > Add-ons > Install, enable “3D View: BlenderGIS”, and set a cache folder for map tiles. Full walkthrough: /how-to-install-blendergis/.
2. Frame your area and pull a basemap. Define your play area on the map and import a satellite basemap for visual reference. Note: since 2022, a free MapTiler API key is required — see /maptiler-api-key-guide/.
3. Import elevation. Pull SRTM elevation through OpenTopography (free key: /opentopography-api-key-guide/) or import your own SRTM .hgt or GeoTIFF files. BlenderGIS triangulates the heightfield into a clean Delaunay mesh.
4. Add OSM context. Import roads, rivers, and building footprints via the Overpass API. Where contributors mapped height or levels tags, buildings extrude to real heights — instant city massing. Overpass errors? See /fix-overpass-406-error/.
5. Decimate and retopologize. Raw terrain is dense. Reduce to your polycount budget, keeping detail where players walk and simplifying distant zones. More on terrain prep: /create-3d-terrain-from-dem/.
6. Bake detail into textures. Bake a normal map (plus height and ambient occlusion) from the dense source onto the optimized mesh — a simple silhouette with a rich surface.
7. Export FBX. Apply all transforms, confirm units are meters, and export. Engine-specific axis settings are covered next.

Exporting to Unreal Engine and Unity

Blender is Z-up with -Y forward; the two engines disagree with each other, so set the FBX exporter axes per target:

Apply transforms (Ctrl+A) before every export, keep one material per terrain layer so the engine can batch cleanly, and always test with a single small tile first — a five-minute import test saves hours of re-exporting a full world.

Collision, LODs, and streaming large worlds

Never collide the visual mesh. For Unreal, author simple proxy meshes prefixed UCX_; for Unity, use convex Mesh Colliders or primitive proxies — terrain itself often works fine with engine-generated heightfield collision. Build two or three LODs per terrain chunk so distant tiles cost almost nothing at runtime.

Finally, split the world into tiles so the engine can stream them: UE5’s World Partition and Unity’s streamed scenes (or addressable chunks) both expect chunked content — one clean splitting pass in Blender saves real pain later. If anything breaks mid-pipeline, /troubleshooting/ covers the common failures.

Populate your world

Terrain is the stage; entourage sells it. Trees, rocks, street props, and vehicles turn a heightfield into a place. Envato Elements carries large vegetation and building 3D packs that drop straight into the same FBX pipeline, and the ArtStation Marketplace is a strong source of hero assets from working game artists. Keep purchased assets in meters to match your terrain scale, and check each pack’s license before shipping. For tooling that pairs well with this pipeline, see /best-blender-gis-addons/.

Frequently asked questions

Is BlenderGIS free for commercial game projects?

Yes — it is GPL-3.0, free and open source. Data licenses are separate: OpenStreetMap data is ODbL and requires attribution, and you should check the terms of any DEM or basemap provider before you ship.

What terrain resolution can I import?

It depends on the source — SRTM is roughly 30 meters, with higher-resolution DEMs available in some regions. For games you will decimate anyway, so source resolution mostly affects the detail you can bake into textures.

Do I need API keys?

For the built-in basemap and OpenTopography elevation services, yes — free keys from MapTiler and OpenTopography have been required since 2022. Importing local .hgt or GeoTIFF files needs no key.

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.

Do buildings import with real heights?

Where OpenStreetMap contributors mapped height or levels tags, footprints extrude automatically. Coverage varies a lot by city — dense in some European capitals, sparse elsewhere.

My basemap or Overpass import failed. What now?

Start with /satellite-maps-not-showing/ and /fix-overpass-406-error/, then check /troubleshooting/ for the full list of common fixes.

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.

The Workflow in Six Steps

1. 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.
2. 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.
3. 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.
4. 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.
5. Clean and organize. Decimate the terrain, merge duplicate vertices, fix normals, and sort everything into layers: terrain, buildings, roads.
6. 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.

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.

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.

If anything misbehaves — blank basemaps, failed imports, missing panels — the troubleshooting hub covers the common failure modes.

Frequently Asked Questions