Status: app version v26.11.250.0
Modeling terrain
Lines that describe the intended terrain form a terrain surface (triangle mesh). It is stored as an object on an area shape in the project and can be applied to a point cloud on request: the points in the region are replaced by points on the surface.
| Topic | Effect |
|---|---|
| Workflow | 1. Draw an area as the boundary and place its edge at the height of the existing terrain, for example with point cloud snapping. 2. Put the floor and the slope edges on a layer as areas or polylines. 3. Choose “Terrain surface…” on the area's card; the area's own layer is preselected, further layers can be ticked. 4. Check the status line and the display. 5. Choose “Apply to point cloud…”, set target cloud A or B and the point spacing, look at the preview with the numbers and click “Apply”. 6. Export as LAS/LAZ. |
| The surface | The outline of the area is both the boundary and a breakline; its heights set the connection to the existing terrain. All visible shapes of the chosen layers are added. The surface is 2.5D, one height per position: if two vertices lie on top of each other in plan, their mean applies, and the card shows the count. “Max. edge length” cuts triangles with long edges at the rim. The surface follows changes to the lines and to layer visibility; only the settings are saved. Locked areas cannot get a terrain surface. |
| Region and points | A position belongs to the region if it lies inside the boundary (the edge counts as inside) and the surface has a height there. All points of the target cloud in the region are removed, regardless of class and return filter, section box and height. New points are created on a grid at the point spacing and along the lines and the outline; their height always comes from the surface. Points outside the region stay unchanged. The new points carry class 2 (ground) and one return of one; other attributes only as far as the target cloud has them. If the class filter hides class 2, the status message says so. |
| Preview | Before applying, the dialog shows how many points are removed and how many are created, and draws the new points in turquoise. The numbers refer to the full cloud. From 2 million new points on, only the display is thinned, not the number. |
| When nothing happens | The dialog names the reason and changes nothing: open move or alignment of the target cloud (bake it first), active DEM projection of the target cloud, active lasso tool or another cloud operation, terrain surface not available, more than 20 million new points (choose a larger spacing). If the surface or the cloud changed since the preview, the preview is recalculated and nothing is applied. |
| After applying | There is no undo. The change is only permanent after a LAS/LAZ export. A DEM built from this cloud is outdated afterwards. The terrain surface remains; the points do not follow later changes to the lines (snapshot), and the application can be repeated after loading the cloud again. |
| Replace in volume A/B | A terrain surface can be chosen as a replacement in volume A/B (“Replace inside terrain surfaces” on the card). The volume then computes inside its outline against its height, without changing the point cloud. Deleting the terrain surface blocks the volumes that use it. |
| Online source | If the target cloud comes from the online source (open-data LiDAR), the link is detached after applying: when opened, the project no longer loads the cloud from the source but asks for a file (↺, for example the LAS/LAZ export). The dialog announces this beforehand. |
| Limits | The new points are a sampling of the surface; volume A/B and the DEM calculate in between as with any cloud. On a test body with flat faces (pit 20 × 20 m, floor 10 × 10 m, 2 m deep) the volume deviated from the analytical value by +0.022 % at 0.1 m, −0.009 % at 0.25 m and −0.036 % at 0.5 m spacing; measured in Node, not in the browser. Nothing is measured for curved terrain. Areas on one of the chosen layers count with their ring as a breakline, including a duplicate of the boundary area. If the target cloud is in a different height system than the terrain surface, applying is blocked. The surface handles up to 200,000 nodes and 100,000 breaklines. The dialog layout, the real preview rendering and large clouds in the browser have not been checked yet. |
Work with your own point cloud.
Open point clouds, trace existing features and export geometry for CAD — directly in your browser, with point cloud data processed locally.
Try free for 14 daysRequest a demo