Terrasolid Spatix

If you have ever tried to open a 500 million-point LAS file in a standard CAD environment, you have likely experienced crashes or minute-long freezes. Terrasolid built Spatix to solve three specific bottlenecks:

The most common entry point for new users is the conversion process. Terrasolid does not require you to abandon LAS; rather, it encourages converting to Spatix as a "working format."

The Workflow:

Pro Tip: Always keep your original LAS files as an archive. Convert a working copy to Spatix for daily editing. When you need to deliver data to a client who does not use Terrasolid, you can export a subset back to LAS.

1. The "Lasso-to-Vector" Workflow This is Spatix’s killer feature. In legacy software, extracting a powerline required classification, thinning, and manual tracing. In Spatix, you draw a rough lasso around the object, and the AI engine instantly snaps a 3D vector line precisely through the center of the points. Processing time for linear assets drops by an estimated 70–80%. terrasolid spatix

2. Native 3D Grid Engine Where older software chokes on 1 billion+ point datasets, Spatix uses a dynamic octree grid. Zooming, panning, and rotating in a dataset of 2 billion points feels like working with a 50 MB file. There is no perceptible lag on modern NVMe hardware.

3. Semantic Intelligence If you extract a "Light Pole" as a feature, Spatix understands it has a base, a shaft, and an arm. You can apply rules (e.g., "attach the arm 5m above ground, pointing at 45 degrees"). This allows for parametric editing—change the pole’s height, and the attached wires update automatically.

4. Hybrid Interface Hardcore Terrasolid users feared a simplified "paint-by-numbers" tool. Good news: Spatix keeps the powerful TerraScan macro engine and batch processing. However, it overlays a context-sensitive ribbon and a much-improved properties panel. New users can finally learn Terrasolid without memorizing 200 keyboard shortcuts.

LiDAR processing is rarely a "one-click" solution. It involves classification (ground, vegetation, buildings), noise removal, and thinning. In a LAS file, editing a point requires rewriting large portions of the file. Spatix allows "in-place" editing. When you change a point’s classification from "medium vegetation" to "low vegetation," the Spatix engine updates only that specific block of data without re-saving the entire cloud. If you have ever tried to open a

Many people confuse Spatix with other TerraSolid names:

| Name | Type | User Level | |------|------|-------------| | TerraScan | Desktop application (runs inside MicroStation/Bentley) | End-user (LiDAR classification, editing) | | TerraModeler | Desktop application (surface modeling, contours) | End-user | | TerraPhoto | Desktop application (aerial photo orientation) | End-user | | TerraSlave | Distributed processing manager | Administrator | | TerraSolid Spatix | Developer SDK (library) | Programmer / Automation expert |

To truly appreciate Spatix, it is helpful to see where it sits in the ecosystem.

While LAZ (compressed LAS) is excellent for sharing via FTP or cloud storage, it is terrible for active work because decompression happens on the fly. Spatix remains compressed on disk but is seekable—meaning the software can decompress only the tiny portion of points you are currently viewing.

TerraSolid Spatix is a software module within the TerraSolid product suite designed for advanced point-cloud processing and automated feature extraction from airborne and mobile LiDAR data. It integrates with TerraScan/TerraModeler workflows to classify points, detect linear and planar features, and generate GIS-ready vector outputs.

A pseudo-code example (C++):

#include <spatix.h>
int main() 
    SpatixContext ctx = spatix_init();
    PointCloudHandle pc = spatix_load_pointcloud("data.las", NULL);
    if(pc) 
        printf("Points: %lld\n", spatix_get_point_count(pc));
        spatix_close(pc);
spatix_done(ctx);
    return 0;