Import terrain
Import meshes or surveyed points in their source grid.
Use File → Import Terrain... and choose the units and vertical axis before importing. Import replaces the current terrain and clears radar placements; undo can restore the previous study.
| Input | Interpretation |
|---|---|
| OBJ | Vertices and polygon faces; materials and textures are not imported. |
| STL | ASCII or binary triangles; supplied normals and colour attributes are ignored. |
| Vulcan .00t | Plain or vulZ-compressed triangulations supported by the app's parser. |
| XYZ / CSV / TXT | Survey points triangulated in plan; use X,Y,Z or Easting,Northing,Elevation headers, or three unheaded columns. |
Choose metres, feet or millimetres. The app converts to metres and subtracts a local origin before creating Float32 geometry, retaining source-grid precision. Z-up uses east=X, north=Y, elevation=Z; Y-up uses east=X, north=−Z, elevation=Y. No projection or vertical datum conversion is applied.
Point triangulation is 2.5D. It cannot infer breaklines, holes or overhangs. The maximum plan-edge filter removes long triangles across gaps. Conflicting elevations at the same plan position are rejected. Mesh triangles are retained without decimation; zero-area triangles are removed with a warning.
Files are limited to 1 GB and point imports to 100,000 points. Meshes have no fixed triangle-count limit; available memory and GPU capacity constrain practical size. Import progress and cancellation run through the terrain worker. Review the warnings before placing a radar.