<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>survey — OSArch</title>
        <link>https://community.osarch.org/</link>
        <pubDate>Mon, 22 Jun 2026 00:22:53 +0000</pubDate>
        <language>en</language>
            <description>survey — OSArch</description>
    <atom:link href="https://community.osarch.org/discussions/tagged/survey/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Using Blender for construction &amp; survey workflows (points, terrain modelling, machine control)</title>
        <link>https://community.osarch.org/discussion/3363/using-blender-for-construction-survey-workflows-points-terrain-modelling-machine-control</link>
        <pubDate>Wed, 04 Mar 2026 18:42:46 +0000</pubDate>
        <category>General</category>
        <dc:creator>JanHolinka</dc:creator>
        <guid isPermaLink="false">3363@/discussions</guid>
        <description><![CDATA[<p>Hi everyone,</p>

<p>I come from a somewhat unusual background compared to most Blender users here.</p>

<p>I work as a <strong>site manager in road construction</strong>, but at the same time I’m also a <strong>software developer, 3D artist and long-time Blender user</strong>.</p>

<p>One of the reasons I started using Blender in construction workflows is the growing use of <strong>machine control systems on excavators and graders</strong>.</p>

<p>These machines require accurate <strong>3D terrain models</strong> (usually LandXML surfaces), but the geometry provided in project documentation is often incomplete or available only as <strong>2D drawings</strong>.</p>

<p>Because of that I started reconstructing and verifying project geometry directly in <strong>Blender</strong>.</p>

<p>Blender turned out to be surprisingly useful because it is:</p>

<ul>
<li>very strong at geometry modelling</li>
<li>fully <strong>scriptable with Python</strong></li>
<li>relatively lightweight compared to most civil engineering software</li>
</ul>

<p>Most professional civil CAD tools are extremely powerful, but also <strong>very expensive</strong>, which makes them hard to justify unless you use them constantly.</p>

<p>So I started building a workflow in Blender that helps me <strong>prepare machine control models, verify project geometry and generate survey points directly from the 3D model</strong>.</p>

<hr />

<h2>My workflow</h2>

<p>The goal is simple.</p>

<p>I want to be able to <strong>verify construction geometry myself</strong>, generate <strong>machine control models</strong>, and give the surveyor <strong>precise staking points</strong> without constantly measuring things manually on site.</p>

<p>A typical workflow looks something like this.</p>

<hr />

<h2>1. Import survey points</h2>

<p>First I import <strong>existing survey data</strong> from the surveyor (usually TXT or CSV files).</p>

<p>These points represent the <strong>current terrain and existing infrastructure</strong>.</p>

<p>I use them as references when reconstructing the <strong>existing terrain surface</strong> or important control points.</p>

<p><img src="https://community.osarch.org/uploads/editor/mu/1zzzkm16raos.png" alt="" title="" /></p>

<hr />

<h2>2. Rebuild project geometry in 3D</h2>

<p>Most infrastructure projects still arrive mainly as <strong>2D drawings</strong>.</p>

<p>When converting them into real 3D geometry you often discover issues immediately:</p>

<ul>
<li>incorrect elevations</li>
<li>inconsistent slopes</li>
<li>geometry conflicts</li>
<li>drainage problems</li>
</ul>

<p>By rebuilding the geometry as real surfaces in Blender (roads, sidewalks, terrain transitions), I can often detect problems <strong>before construction starts</strong>.</p>

<p><img src="https://community.osarch.org/uploads/editor/m3/0jh1kbjjghlq.jpg" alt="" title="" /></p>

<hr />

<h2>3. Terrain modelling and slope verification</h2>

<p>A large part of road design is about <strong>correct slopes and drainage</strong>.</p>

<p>Inside Blender I often model surfaces and visually verify things like:</p>

<ul>
<li>road cross slopes</li>
<li>transitions between surfaces</li>
<li>terrain shaping</li>
</ul>

<p>Sometimes I even run simple <strong>rain simulations</strong> to visually check where water flows.</p>

<p>This can reveal problems that are not obvious in 2D documentation.</p>

<hr />

<h2>4. Generating staking points</h2>

<p>Once the geometry is correct, I generate <strong>staking points</strong> directly from the model.</p>

<p>Instead of manually measuring elevations on site using a level and reading them from cross-sections, I can export the exact coordinates of important points directly from the model.</p>

<p>These can then be sent to the surveyor or used for <strong>machine control preparation</strong>.</p>

<hr />

<h2>5. Producing point diagrams and drawings</h2>

<p>On construction sites it's still very common to work with simple <strong>printed drawings showing labelled points and elevations</strong>.</p>

<p>For example:</p>

<ul>
<li>staking points</li>
<li>curb elevations</li>
<li>slope breaklines</li>
<li>drainage points</li>
</ul>

<p>Clear diagrams with labelled coordinates are extremely useful for communicating geometry on site.</p>

<p><img src="https://community.osarch.org/uploads/editor/di/hr73xia7rqxe.png" alt="" title="" /></p>

<hr />

<h2>Tools I built for this workflow</h2>

<p>Because Blender doesn't have built-in tools for this kind of work, I started writing a small set of add-ons that support this workflow.</p>

<p>Some of the tools include:</p>

<p><strong>Survey Points Importer</strong></p>

<p>Imports survey points from TXT/CSV files directly into Blender.</p>

<p>Useful for working with existing survey measurements.</p>

<p><strong>Survey Points Exporter</strong></p>

<p>Exports selected points back to TXT/CSV so they can be used by surveyors or machine control systems.</p>

<p><strong>Survey Points Annotator</strong></p>

<p>Automatically generates labels for points (numbers, coordinates or elevations).</p>

<p>This saves a huge amount of time compared to manually labeling hundreds of points.</p>

<p><strong>Scale Print Camera</strong></p>

<p>Creates <strong>true-scale technical drawings directly from Blender</strong>.</p>

<p>You can define:</p>

<ul>
<li>paper size</li>
<li>drawing scale</li>
<li>DPI</li>
</ul>

<p>and export renders that print at <strong>exact scale in PDF</strong>.</p>

<hr />

<h2>Upcoming tools</h2>

<p>I'm also working on additional tools for construction workflows:</p>

<ul>
<li><strong>Terrain Tools</strong> – helpers for modelling road surfaces and slopes</li>
<li><strong>LandXML export/import</strong> – mainly for exporting machine control models</li>
<li><strong>DXF import/export</strong> – for exchanging simple geometry with construction software</li>
</ul>

<p>All tools share a <strong>common reference point system</strong>, so coordinates stay consistent when importing or exporting survey data.</p>

<hr />

<h2>Curious about other workflows</h2>

<p>I'm very curious how others handle similar workflows.</p>

<p>Do any of you use Blender or BlenderBIM for things like:</p>

<ul>
<li>terrain modelling</li>
<li>survey data</li>
<li>construction verification</li>
<li>machine control preparation</li>
</ul>

<p>Or do you rely entirely on traditional civil engineering software?</p>

<hr />

<h2>Links</h2>

<p>Add-ons<br />
<a href="https://superhivemarket.com/creators/janholinka" rel="nofollow">https://superhivemarket.com/creators/janholinka</a></p>

<p>Short demo videos<br />
<span data-youtube="youtube-CpYIw3sfpdk?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=CpYIw3sfpdk"><img src="https://img.youtube.com/vi/CpYIw3sfpdk/0.jpg" width="640" height="385" border="0" alt="image" /></a></span><br />
<span data-youtube="youtube-7fAy2h7kGQc?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=7fAy2h7kGQc"><img src="https://img.youtube.com/vi/7fAy2h7kGQc/0.jpg" width="640" height="385" border="0" alt="image" /></a></span><br />
<span data-youtube="youtube-t88x9w1zkI4?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=t88x9w1zkI4"><img src="https://img.youtube.com/vi/t88x9w1zkI4/0.jpg" width="640" height="385" border="0" alt="image" /></a></span><br />
<span data-youtube="youtube-e925yY8zD9k?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=e925yY8zD9k"><img src="https://img.youtube.com/vi/e925yY8zD9k/0.jpg" width="640" height="385" border="0" alt="image" /></a></span><br />
<span data-youtube="youtube-6ToPG3T2Ixc?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=6ToPG3T2Ixc"><img src="https://img.youtube.com/vi/6ToPG3T2Ixc/0.jpg" width="640" height="385" border="0" alt="image" /></a></span></p>

<p>Most of these tools started as <strong>small scripts I wrote for my own construction projects</strong>, and they gradually evolved into more structured add-ons.</p>

<p>I'm currently finishing a full <strong>timelapse of the entire workflow</strong>, showing how a construction model for <strong>machine control (UniControl)</strong> is created in Blender.</p>

<p>It should be ready in a few days — if people are interested I can share it here.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
