Status: app version v26.11.250.0

Transformation grids

Load grids … (settings → Geo)Opens the catalogue of official grids from cdn.proj.org: grouped by “Worldwide” and country, each row showing kind (geoid or datum grid), size, licence and status. Clicking “Load” fetches the file with a progress display and verifies its checksum; the run can be cancelled at any time. Loaded grids stay in the browser, are available to every project, and appear in the copyright window under “Loaded grids” with their publisher's attribution.
Datum grid instead of HelmertOfficial datum grids (NTv2, NADCON5) exist for systems on an old national datum: in Europe e.g. British National Grid, DHDN/Gauss-Krüger, RD New, MGI, CH1903, BD72, HD72, and also North America (NAD27/UTM), Australia (AGD66/AGD84, plus GDA94→GDA2020) and New Zealand (NZGD49). Once the grid is loaded, the app computes through it instead of the 7-parameter set — the difference is roughly 1–2 m in Europe and roughly 2–3.5 m for the legacy datums outside Europe (up to roughly 20 m in the NAD27 border band with Canada). A regionally split datum such as NAD27 needs SEVERAL grids per zone; the app only computes through them once all of them are loaded. The reprojection line of the import dialogue states which route applies, the slot card notes “(grid)”, and “Grid … active” appears next to the project CRS. If the grid is missing, that is reported — the Helmert set is then used.
No network: choose fileIf the download fails, the row offers “Choose file” plus a direct link to the file: download it yourself (even on another machine) and attach it here. If the checksum differs from the catalogue the file is still accepted — it may be a newer official edition — but the app says so. A checksum error during the CDN download does NOT lead to the file route: there the file arrived and was faulty.
Load grid now (size)When the app refuses a conversion because a catalogue grid is missing (a geoid on import, re-attach, export or “Convert project heights”; a datum grid for the project CRS), the sidebar section “Height system” shows a tile with the button “Load grid now (size)” — the dialog “Convert project heights” and the import dialog carry the same button right next to the message. ONE click opens the catalogue on that grid and fetches it immediately, with progress, cancel and checksum as usual; the tooltip names publisher and licence. Without that click the app fetches nothing from the network. Nothing continues on its own afterwards, and the message names the remedy: repeat a refused action (export, “Convert project heights”, re-attaching a terrain model); after importing or re-attaching a point cloud whose heights were not converted, run “Convert project heights”; undo a DXF/GeoJSON import and repeat it. Nothing was refused at the project CRS — with the grid it computes more accurately, clouds already converted stay as they are. The tile can be dismissed with “×”; it only returns when a new message names the same grid. There is no offer for your own geoid that does not come from the catalogue.
Catalogue geoids of the national agenciesAll 21 catalogue geoids can be registered. Nine of them are accepted although their horizontal frame differs — GCG2016 (Germany), NLGEO2018 (Netherlands), SWEN17 (Sweden), geoid2021 (Poland), geoid2014 (Hungary), SLO-VRP2016 (Slovenia), RAF20 (France), Icegeoid (Iceland) and LV14 (Latvia): their files name the national ETRS89 realisation as the horizontal frame instead of “ETRS89”. For looking up a geoid these frames are at most 2 m away from ETRS89 or WGS 84 — less than 1 mm in height. A geoid GeoTIFF on an old national datum (e.g. ED50, NAD27) is still rejected; the browser console then names the EPSG code.

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