Point in Case
One Scan, 900 Files?!
Real-world support cases explained – one point cloud at a time.
In this series, we take a closer look at real questions and challenges that come up when working with point cloud data. Each post is based on an actual support case and breaks down what happened, why it happened, and how to solve it, step by step.
But we don’t stop at troubleshooting. Along the way, we explain the background behind the tools, terms, and technologies involved.
The Question That Sparked This Post
“I imported just one scan… why do I have over 900 files now?”
If that sounds familiar, you’re not alone, and no, PointCab isn’t secretly duplicating your data. This exact situation came up in a recent support case, and it gave us the perfect opportunity to explain what’s really going on behind the scenes.
Let’s just say: it’s not a bug – it’s a feature. And a smart one at that.
The Key Context: Structured vs. Unstructured Point Clouds
Before diving into what happened, it helps to understand how point clouds are stored and why that matters when you import them into PointCab Origins.
Structured Point Clouds
- Come directly from scanners in their native formats
- Include metadata like scan positions and orientations
- Organized into scan stations or lines, each with a defined perspective
- Ideal for clean segmentation and accurate scan-to-scan alignment
Structured Point Clouds
- Formats like E57, LAS, or LAZ (especially when exported generically)
- Contain just the point data—no scan position, no segmentation
- All points are merged into a single cloud, with no “origin story”
- Often include stray points far outside the area of interest
Unstructured formats are great for software compatibility and flexibility, but they don’t tell the full story. That means software like Origins needs to rebuild structure to make the data usable.
We explain this in more detail in our webinar on structured vs. unstructured point clouds, including why this difference affects file handling and performance.