Status: app version v26.11.250.0
Height system & DEM
Drone point clouds usually arrive in WGS84 ellipsoid heights, Leica RTK survey points typically in NHN orthometric heights (DHHN2016). The difference is about 47 m in Germany. A geoid file (e.g. GCG2016v2023) converts between both systems at import. A DEM built from the cloud's ground points models the terrain shape; OSM and ortho layers can drape onto it.
| Action | Effect |
|---|---|
| Load geoid file | A geoid grid in GeoTIFF following the PROJ convention, ISG 1.0/1.01/2.0, ESRI ASCII Grid, Lat/Lon/N triples, Trimble .GGF or Carlson .gsf, or the binary formats GTX, NGS BIN, NRCan BYN, Surfer GRD (DSAA/DSBB/DSRB) and — for Australian grids only (AHD71/AVWS) — NTv2 .gsb is detected, registered as a geoid grid and offered as "NHN (via …)" in the height-system display dropdown. Leica .GEM, Topcon/Sokkia .gff, Javad .db3/.dat and CHCNav .cgd cannot be read — the app instead names the manufacturer and a workaround via another export format. |
| Switch project display system | Only the Z-value labels change — no number. If loaded data is then not in the chosen system, the row “Data is in …” below and a ✱ on the slot card show it; “Convert heights…” converts it. |
| Height system in import dialog | When loading a cloud the input system is asked. On mismatch with the display system the geoid offset is baked into Z values once. |
| Heights on DXF/GeoJSON import | DXF/GeoJSON import dialog, section "Heights": shows the project CRS, the display height system, loaded geoids (with "Load geoid…") and the height system of the open cloud. There you state whether the file's Z values are orthometric or ellipsoidal (HAE) heights; the open cloud's height system is preselected, without a cloud the display system (lon/lat GeoJSON: HAE). If they differ, the heights are converted point by point into the open cloud's system on import (without a cloud: the display system) — so shapes and cloud always share the same numbers (this needs a geoid and a project CRS; if the geoid has no value at any point, nothing is converted). Shapes at Z=0 are never converted. With a cloud open, a traffic light compares the file's mean height with the cloud ground; if the offset matches the geoid undulation, orthometric and HAE are probably swapped. If two cloud slots are loaded and they are in different height systems, a warning line says so: heights are converted into the active slot's system, and the shapes will not match the other slot in height. |
| Convert project heights | Height system panel, row “Data is in …” → “Convert heights…” (or “Convert…” on the mismatch row of the slot card): converts the WHOLE project into the chosen height system — every point cloud with its variants, shapes, section box, drawing plane, DEM with contour lines and image poses; afterwards the display is set to the target as well. Clouds, shapes, DEM and image poses are converted point by point via the geoid; section box, drawing plane and A/B planes are shifted rigidly by the offset at their centre. There is no undo (the undo steps of the shapes are cleared); converting back is possible. It is refused — without changing anything — if a geoid or the project CRS is missing, a slot has an unknown height system, a translation/alignment is open, a point lies outside the geoid grid or in NoData, or while something else is running (drawing, DEM build, export, importing or re-attaching a point cloud). If the project's point clouds (loaded or pending) are in different systems or there are none, the dialog asks which system the shapes are in; “Advanced” lets you state it in any other case too (if the shapes are known to be in a different system than the active cloud). Shapes with Z = 0 stay untouched and are counted. If applying itself fails (for example out of memory), everything is rolled back and the project stays unchanged. |
| Relabel heights (no conversion) | In the “Convert project heights” dialog the switch “Relabel only”: sets the height label of all point clouds (loaded and pending), the re-attach marker of a file DEM and the display to the target — WITHOUT converting anything; points, shapes, section box, DEM and image poses stay identical, point for point. Only for the case that the numbers already lie in the target system but the label is wrong (e.g. “NHN via a partial geoid” on a cloud that really is in official NHN). Chosen wrongly, every height ends up off by the geoid undulation (roughly 36–50 m in Germany). An open transform, a missing CRS and missing geoid coverage do NOT block; blocked are an unknown target, a target geoid that is not loaded, and everything that also blocks converting (running drag, foreign dialog, re-attach …). Point clouds with an unknown height system also receive the target label; if only the display differs, it is set to the target too. Way back: run the same action again with the old label as the target. |
| Heights in the file (export) | The export dialogs for LAS/LAZ, DXF, GeoJSON and DEM GeoTIFF show a "Heights in the file" row as soon as a conversion is possible (geoid loaded or data in orthometric heights, plus a project CRS). The default is "As in project" (no conversion, not remembered); alternatively the export converts the heights point by point to NHN or ellipsoidal heights — in the file only, cloud and display stay unchanged. The file itself does NOT state its height system; it appears only in the file name (-nhn / -hae) and in the status line. If even a single point of the data lies outside the geoid grid or on NoData, the export is refused (no file) — the points count, not their bounding rectangle. The contour DXF is not converted; if two slots are in different height systems, the "second slot" checkbox locks the choice. |
| Import preflight (CRS analysis & placement) | Loading a point cloud first shows an analysis in the import dialog: file, format, point count, extent and center in file coordinates, the CRS found in the file (LAS GeoKey or WKT VLR, E57 header, PLY comment) and — if none is present — a guess with a reason. If a cloud is already loaded, a traffic light shows how far the new one would sit from it. The file CRS can be changed; if it differs from the project CRS the cloud is reprojected horizontally (heights stay unchanged; ETRS89 and WGS 84 of the same zone are treated as equal). Placement is selectable: as in the file, into the local origin 0,0,0, or onto the center of the first cloud — the latter two as a slot translation, adjustable in the slot card at any time. With the two centering placements, a purely local cloud (no CRS, small coordinates) adopts the first cloud's frame instead of being computed into it — otherwise the float32 resolution would quantize its points onto a half-metre grid. When merging two clouds into the analysis-active cloud, the same frame rule applies: the georeferenced frame wins (the local side adopts it); two georeferenced clouds stay unchanged and get an accuracy warning instead. |
| Import: local system (no CRS, no geoid) | The switch in the import dialog takes the cloud as it stands in the file: no file CRS, no conversion, height system "Unknown". The CRS, geoid, height system and epoch bridge blocks disappear. On confirm, a set project CRS is removed if the project is otherwise empty; if data is already loaded it stays and the cloud is added without conversion. The switch is preset only if the file names no CRS and the numbers look like a local system. |
| CRS selection (Europe + worldwide UTM zones) | The CRS lists (settings, import dialog, sidebar suggestions) list the official national systems of most European countries (Spain via the ETRS89/UTM zones) plus the United Kingdom, Ukraine and the Balkans as well as the worldwide UTM zones (WGS 84 north/south, NAD83 for North America); also the legacy national datums of North America (NAD27/UTM), Australia (AGD66, AGD84, GDA94) and New Zealand (NZGD49/New Zealand Map Grid). They are grouped: "Recommended" at the top, then DACH, then the countries alphabetically with their zone families, and finally the UTM zone families, Europe and Web. What appears under "Recommended" depends on the place: in the import dialog the CRS found in the file, the current project CRS and — only on the project CRS picker — the UTM zone matching the geographic longitude plus its neighbor zones; in the settings and the sidebar only the current project CRS. Systems on an old national datum (e.g. British National Grid, RD New, S-JTSK, EOV) are converted via a 7-parameter set and are therefore accurate to around 1–5 m — shown as a tooltip on the option and, as soon as such a side is involved in a reprojection, in the reprojection line of the import dialog. The legacy datums outside Europe (NAD27, AGD66, AGD84, NZGD49) carry their own measured figure there instead of the class, because it differs per zone. For some of these systems the official datum grid can additionally be loaded (NTv2 or NADCON5, catalog fetch from cdn.proj.org or file) — the app then computes over it instead of the 7-parameter set and is accurate to the centimeter. |
| Epoch bridge (file is in current ITRF/WGS 84) | In the import preflight, a bridge-eligible target CRS (ETRS89, NAD83(2011) or GDA2020) offers an epoch bridge (default OFF) — it computes the real plate offset to the present via a 14-parameter approach with an epoch (Europe-wide ETRS89 about 0.9 m, NAD83(2011) up to 1.4 m, GDA2020 about 0.4 m), with an epoch suggestion from the file's GPS time. Turn it on for uncorrected RTK raw data (e.g. DJI drones without SAPOS/network correction); do NOT turn it on for already network-/SAPOS-corrected data — it already sits correctly in the target datum, and the bridge would shift it by the same amount in the opposite direction. |
| Trajectory (SLAM) | File → Import → “Trajectory (SLAM)…”: reads lines “time x y z qx qy qz qw” (.txt/.csv/.traj; space, comma or semicolon separated) and creates the path as a locked polyline on its own layer. Points closer than 5 cm are merged. |
| Cancel (status line) | Cancels a running coordinate reprojection; the import is discarded and a restored slot stays pending. |
| Loading failed | If loading a point cloud fails, a window opens in addition to the status line with the cause in plain language (memory/size, unsupported format, damaged file, unreadable), an analysis of the file header (format, points, record length, extent, CRS), the existing limits and concrete suggestions. "Copy analysis" puts the text on the clipboard for support. |
| Load progress | While a point cloud loads, the status line at the bottom shows the step, the share done and — after a few seconds — the estimated time left (reading file, unpacking or parsing); the time left refers to the current step, not to everything. After reading it names the read time. Large clouds appear coarse at first; while the detail levels are built, a small note in the viewport shows the progress. There is no separate window for it. |
| Build DEM | Heightfield mesh from the analysis-active cloud's ground points. "Auto" filter uses classification 2 if present, otherwise lowest-Z per cell. |
| Limit to boundary | If an area is marked as the boundary, the DEM panel shows the "Limit to boundary" checkbox (on by default). The DEM is then built inside that area only — for every ground source, with a shape-accurate edge even at re-entrant corners; the contour lines stop there as well. If the active slot has a pending move/alignment, the limited build is refused (bake it first or uncheck the box). |
| Show triangle mesh | Draws the triangle edges of the DGM as lines over the terrain surface (including filled holes, excluding areas outside the boundary), independent of map, colouring and opacity. If the DGM is hidden, the mesh is hidden too. For very large DGMs at most 600,000 segments are drawn; the mesh then draws only every nth line and every nth diagonal (n is shown below the switch). The choice is per device and not saved in the project. |
| Class filter — ground only | If the cloud carries a ground classification (LAS code 2), the DEM panel shows the "Class filter — ground only" checkbox (on by default). The DEM is then computed from ground points only — independently of the visible class filter and for every ground source; with the "Visible points" source both filters combine. Without class-2 points the row stays hidden. The choice is stored in the project state (format 41); older files build without the pre-filter, unchanged. |
| Per-point height conversion | Heights are converted per point through the geoid (one constant offset at the cloud centre would cost about 1–3 cm over 1 km and up to 20–30 cm over 10 km); the status line names the height-correction range and the run can be cancelled. If the geoid has no value at even ONE point, nothing is converted — the cloud keeps its input height system and the message names the number of affected points. |
| Reload the geoid | The grid geometry is read exactly from the file's origin, step size and registration (not derived from the outer edge envelope, which would sample the geoid up to roughly 2.8 km off). A default geoid stored by an older app version still carries the old geometry and is discarded on start: the app reports "Please reload the default geoid". Load the file once more and the mapping is correct; heights may shift by a few centimetres in the process — that is the fix. Where the grid has no value (NoData, e.g. outside Germany) NO height conversion takes place — the cloud keeps its input height system and the app says so. |
| Drape on DEM | OSM tiles and ortho layers bend along the terrain instead of lying flat. Toggleable per layer. |
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