Status: app version v26.11.250.0

Export triangle surfaces (DXF, LandXML)

The surfaces of the app can be written to a DXF file as real triangles (3DFACE), so that CAD programs get them as a surface. There is no separate calculation: the file holds the triangles the display shows. The DTM is in the list as well, in two modes (see below). DXF and LandXML can be chosen as the format.

ProcedureFile menu, Export, “Export triangle surfaces (DXF)…”: the dialog lists all surfaces of the project to tick. Faster: the button “As DXF…” on the card of a terrain surface or “Surfaces as DXF…” on the card of a volume opens the dialog with those surfaces preselected. The selection is not remembered. Each surface gets its own layer named after the surface (umlauts and spaces are replaced as in the shape DXF, equal names get _2, _3). The triangles are in world coordinates with four decimals (0.1 mm), counter-clockwise in plan. DXF version and layer prefix (“where missing”) as in the shape DXF.
What the list containsTerrain surface (TIN). Volume A/B: reference and comparison, with source “Constructed surface (TIN)” also the TIN version of that side, with a layer build-up one “Bottom of <name>” per layer boundary and “Subgrade” at the bottom; the top side carries the suffix “(Top surface)” in the list but appears only once in the file. Classic volume: surface and the layer boundaries. Surfaces without a valid result are greyed out with the reason and cannot be ticked. If a ticked surface changed while exporting, nothing is written and the dialog rebuilds the list.
Raster surfacesReference, comparison, surface and the layer boundaries are the mesh over the calculation raster, with the heights the app calculates with. Inside, the triangles are inclined, between the sample points; at the edge there are pieces per edge cell (cut at the polygon for volume A/B, a stepped edge for the classic volume) whose heights are continued from the neighbouring cells: every position carries exactly one height, there are no steps and no walls at the edge. The edge height is the linear continuation of the surface from the neighbouring cells, not a calculated height: a flat plane continues exactly at the edge, except at strips one cell wide; behind a break line or at a step the continuation can overshoot, and with noisy data it can deviate; the quantities still calculate with the height of the edge cell. Reference and comparison of volume A/B are the common area of both sides. For very fine rasters (over 250,000 cells) the app shows blocks; with “as calculated” the file keeps the finer calculation raster, the row says so.
Terrain surface and TINThe file holds exactly the triangles of the display, also those of the TIN version at volume A/B. That one contains all triangles that touch the volume polygon, uncut, and is never shifted by the subgrade. Vertical display walls (terrain surface, constructed surface) are not written: at a vertical step the file has a gap in height, not a gap in plan. If a layer line runs beyond the outline, triangles outside the outline can occur; one measurement gave 60 m² for an outline of 400 m².
Triangle sizeFor all raster surfaces together: “as calculated”, “double” or “fourfold”. Double and fourfold are the block merge the display uses to coarsen large rasters: a block gets a height only if more than half of its cells have one. Blocks can drop out at the edge, small holes vanish, and for the classic volume the surface can stand out over the polygon by about half a block. In measurements the area of a rotated square deviated by 1.5 % (double) and 5.7 % (fourfold); a square on the cell grid stayed unchanged.
DTM (terrain model)The row “DTM” is in the list as soon as a DTM is built; the button “Export as triangles…” in the DTM panel opens the dialog with it preselected. “Simplified” (default) picks as many grid nodes as needed so that the surface deviates from the grid height by at most the tolerance at every node (0.01 to 5 m, default 0.05 m): flat areas get few large triangles, steep areas many small ones. “Raster” writes all cells as triangles, with step 1, 2, 4 or 8 (every nth node: blocks of n × n cells become two triangles; at a boundary the cells stay single). The calculation runs in the background with progress and can be cancelled. The tolerance holds at the grid nodes, not in between: between the nodes the surface can deviate more from the displayed one, because the choice of the diagonal in a cell changes the height of the cell centre (measured on a synthetic slope terrain: 0.12 to 0.31 m against the display at tolerances of 0.02 to 0.25 m). With a boundary all boundary nodes are kept, nothing is simplified at the edge. In raster mode with a boundary, T-junctions appear where coarse blocks meet single cells, that is small height gaps along the seam; not in “Simplified” mode. An open shift of the source slot is not written, the dialog points it out. If the simplification fails a check of the surface, the app writes the DTM unsimplified (fallback) and says so.
LandXMLSelectable in the dialog: format “LandXML” (.xml file, version 1.2, units metres) instead of DXF. Each surface becomes a surface with points and triangles, shared corners are stored once. The coordinate system is in the file only if the project CRS is an EPSG code. The file does not declare a height system. The sample files are checked against the LandXML 1.2 schema (xmllint); the import of two sample files was checked in DATAFLOR GREENXPERT, large files there were not. In DATAFLOR GREENXPERT the vendor describes the way “Terrain > Import > LandXML”; two sample files (about 800 triangles, with and without EPSG code, in docs/samples/landxml/) were read there as a triangulation, and the position was right. Not checked: large files in GREENXPERT, other programs (Civil 3D, BricsCAD), and several surfaces in one file in GREENXPERT. The file can hold fewer triangles than counted (two equal points after rounding to four places); the status line names the written number.
Classic volumeThe classic volume reads the analysis-active, filtered cloud (class filter, section box), like the number. The file therefore depends on the current filter and slot; without a loaded cloud the surface is not available. “Subgrade” there is only the lowest layer boundary of the display, the calculation does not go to the subgrade.
Size and limitsThe dialog shows the number of triangles and the approximate file size (DXF about 240 bytes per triangle; LandXML measured about 68 bytes per triangle for a grid, including the points). From 250,000 triangles it warns, above 1,000,000 in total it refuses: tick fewer surfaces or choose a larger triangle size. Whether the file can be built is known only after counting; the estimate made in advance can be too high or too low and therefore does not block. Only if the estimate of the ticked surfaces that have not been counted yet is above 4,000,000 is nothing built, and the row then gives only an estimate. The file is written in parts, not as one large string.
Heights in the fileAs in the shape DXF: “As in the project” writes the numbers of the app; “NHN” or “HAE” converts only in the file (points outside the geoid hull or without a value refuse the export). The file declares no height system, it is in the file name (-nhn, -hae). If the ticked surfaces lie in different systems, the conversion is locked. All measured values come from Node (synthetic); opening the DXF file in AutoCAD or DATAFLOR is not tested, the file is checked with ezdxf (0 errors, 0 repairs).

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