Transcript
How Do You Correlate a Point Cloud with an Onion?
So how do you get a point cloud and correlate the point cloud with an onion? I just want to give you a quick summary. Similar to what I talked about last episode when we discussed what a point cloud is—a bunch of dots on the screen that formulate into a specific object—it really depends on the type of datasets you have. You have SLAM datasets and various scanners available on the market.
What Does a Client Really Want from a 3D Scan?
So when someone gives you a point cloud dataset—whether structured or unstructured—it becomes something you’ll use down the road. When clients say they want a 3D scan, they often really want a deliverable. That leads to the next question:
What are you hoping to get out of this 3D scan?
Matching the Scanner to the Problem
When I talk to people about point clouds, I ask:
What kind of problem do you have that a 3D scanner could solve?
That helps me decide:
- Do we use SLAM technology?
- GeoSLAM?
- NavVis?
- Flash?
- Structured light?
- Or a terrestrial laser scanner?
Each scanner type outputs different data and accuracy levels. It’s not just about owning every scanner—it’s about choosing the right one for the right use case.
Understanding 3D Scan Deliverables
Once you understand what the deliverables are, you can better interpret the scan data.
Client question: “I need a 3D scan for here.”
Follow-up: “What do you want to get out of that 3D scan?”
That’s a critical question.
Introducing the Onion Method
Let’s bring up the onion. Imagine slicing it open—you’ll see layers. That’s how I explain the depth of scan deliverables to clients.
The Layers of a 3D Scan:
- Layer 1: Raw scan data
- Layer 2: 2D CAD drawings
- Layer 3: 3D model / scan-to-BIM
- Layer 4: Analytical insights (e.g., floor flatness, cloud-to-cloud deviation)
The deeper you go into the point cloud, the more information you can extract. One scan can power multiple deliverables.
Helping Clients Choose 2D, 3D, or Both
When clients are unsure whether they need 2D or 3D, we guide them through the onion method. Some feel more comfortable starting with 2D—even if the dataset supports a full 3D output.
We explain that:
- You don’t have to use the 3D data right away
- You can extract a 2D plan now and later convert to 3D
- Your scan investment keeps working for you over time
Final Thoughts and Community Callout
I love hearing your comments—how do you use 3D scan data? Which “layer” do you rely on the most? The onion method helps people visualize the full potential of their scans, and I’d love to know how you’re leveraging it.
More to Come
Check out the iScano website and The 3D Show page—we’ve got interviews coming from across Canada, the U.S., and even Europe.
Let me know in the comments or by email what you’d like to see next. I do this out of love for the industry, and I appreciate you being here.
My name’s Sebastian. Welcome to The 3D Show. See you in the next episode.
Personal Thoughts:
One of my all-time favorite episodes is the one where we talk about a question I hear all the time: “What do I actually get from a 3D scan?” The truth is, many clients and professionals still kind of see scans as just this neat visualization or some sort of raw data—when there’s really a ton of value hiding deep inside. So, I went with a simple analogy I’ve used in the field. It’s called the onion method, and it’s supposed to help you envision the layers of all the different kinds of value you can find inside a single scan. And if you work your way through the surface and the simple stuff inside, you can even find some pretty challenging comparisons to work with. You know, like figuring out floor flatness or the cloud-to-cloud deviation you can get with some of the fancier scanners.
I firmly maintain that the key to unlocking scan data lies not in the tools one possesses, but in one’s mindset and manner of communicating. In this episode, I attempted to lay that down in simple terms, and I hope it aids more folks working in the AEC realm to make more intelligent decisions regarding point clouds.
