Skip to content

Coordinate Systems and Heights ​

Every Lidarvisor project has two values that say where its numbers are on Earth:

ValueWhat it isShown as
Coordinate systemThe horizontal system of the project's results: what its X and Y (or longitude and latitude) are measured inNAD83(2011) / Texas South Central (ftUS) (EPSG:6588)
HeightsWhat the results' elevations are measured from, and in which unitNAVD88 · GEOID18 · US survey feet

The EPSG code in brackets is the standard number of the system, the one your GIS or CAD software asks for. The same two values are used everywhere: in the creation panel, in the viewer, on downloads and in the report.

When you create a project, the Coordinate systems block under your files shows both values, each with a grey line saying where it came from (Stated in your file, Proposed from where your photos are, Chosen by you) and a Change link. Nothing is asked after Import project, except the coordinate system of a LiDAR file that states none.

Every file you add has a coordinate system and heights of its own: what its numbers are in. Lidarvisor reads them from the file when the file states them, asks only when it does not, and converts each file into the project's systems.

Coordinate system ​

The coordinate system of the results is:

  • For a LiDAR file (LAS, LAZ, COPC): the one stated in your file, unless you ask for your results in another system (see Delivering Your Results in Another Coordinate System).
  • For drone photos or raw DJI flights: proposed from where the data is. Near Houston, that is NAD83(2011) / UTM zone 15N; near Toronto, NAD83(CSRS) / UTM zone 17N; near Lyon, RGF93 v1 / Lambert-93. Outside the countries with a national system, it is the WGS 84 / UTM zone of the site. You can choose any projected system instead (a State Plane zone, for example): the photo or raw cloud is computed directly in it.
  • For a LiDAR file and photos together: the LiDAR file's. The photo results are converted to it.

Delivering your results in another coordinate system ​

Your file is in one system and your client wants another (a State Plane zone instead of UTM, a national grid instead of WGS 84)? Click Deliver my results in another coordinate system under the coordinate system of your point cloud, or, after creation, Change on the project card → Convert my results to another system, and pick any projected system.

  • Your point cloud is converted once, when it is read, with the EPSG operation that PROJ (the reference library of GIS software) selects. Every result is then produced in the new system: the classified cloud, the rasters, the vectors, the topographic map and the reports.
  • Heights follow: when your file states them and you choose another height system, they are converted with the geoid grid of your site. When your file does not state them, they are not guessed: only their unit follows your results.
  • A unit change is exact (1 m = 3937/1200 US survey feet).
  • It is free and changes nothing to the price of the run.
  • Your file stays as it is. The Original point cloud download offers Converted (in your results' system) or As uploaded (the whole file, its format and system unchanged).
  • When two datums are related only approximately (WGS 84 and NAD83, for example), a note says so, with the expected order of magnitude: check your file's datum if centimetres matter.
  • A target in a Mercator system shows that lengths and areas are distorted in it, and offers the national or UTM system of the site instead.

It is set before processing: once a project is processed, its systems are read-only. A cloud placed by local coordinates or by Find it for me is not converted; its results stay in the system found for it.

Change on the project card offers the other case too: My file is in another system, for a system read from your file that is wrong. Nothing is moved: the file is read again in the system you name.

When the file states no system ​

The coordinate system picker opens, titled with the file's name. Search by name, code or region, or use Find it for me: enter a city, an address or GPS coordinates of the survey and the system is found while processing. It tries every EPSG projected system, and the regional grids that EPSG lacks (some Hawaii State Plane zones in US survey feet, for example), and keeps the systems that place your cloud within 50 km of that place; an EPSG system is preferred when both fit. A file whose coordinates are near 0, 0 is in local coordinates: tick the local coordinates box and enter where the centre of the cloud is; it is placed there in the WGS 84 / UTM zone of that place, in metres, with no rotation. A file in degrees (longitude and latitude) is never treated as local coordinates.

"Find it for me" and local coordinates are for LiDAR files only. The results of photos and raw flights need a system you choose.

When the system does not fit the data ​

Lidarvisor checks where your data lands in the system it is given. When it lands outside the area where that system is used, or its coordinates are near 0, 0 although the file states a projected system, you see a warning with what was found and, when it can, the systems that place your data where they are used. It is a warning, not a refusal: if you are sure of the system, confirm it.

Tile sets ​

A tiled survey must be in one coordinate system. Two codes that describe the same grid with the axes in a different order (for example Gauss-Kruger zone 4 stated northing first, EPSG:31468, and easting first, EPSG:5678) count as one system. When only some tiles state a system, you are asked to confirm it for the whole set, with the stated one selected.

Heights ​

A height is only meaningful with what it is measured from:

  • Ellipsoidal heights come straight from GNSS: heights above the ellipsoid of the coordinate system's datum, with no geoid applied. They are in the coordinate system's unit.
  • Geoid heights (NAVD88, CGVD2013, NGF-IGN69, ODN…) are altitudes above sea level, computed from ellipsoidal heights with a geoid model, a grid of the geoid's height over the ellipsoid (GEOID18 in the contiguous United States, GEOID12B in Alaska, CGG2013a in Canada, RAF20 in mainland France).

The two can differ by tens of metres: the geoid is about 27 m below the ellipsoid in Texas and 50 m above it in France. A wrong height system leaves no visible symptom (the cloud looks right and sits 30 to 50 m off), which is why Lidarvisor always says which one it uses.

Why only some height systems are listed ​

A height system is offered only where it can be applied: each entry of the list is a height system, the geoid grid that converts to it and its unit, and it is listed only when that grid covers your whole site. Ellipsoidal heights are always listed. A height system with no grid-based conversion (DHHN92, EVRF2007, NGVD29…) can still be stated by a file and is shown by its name, but results cannot be computed in it.

When the coordinate system is in US survey feet, the feet variants come first: NAVD88 · GEOID18 · US survey feet before NAVD88 · GEOID18 · metres.

US survey feet and feet ​

The US survey foot (1200/3937 m) and the international foot (0.3048 m) differ by 2 parts per million: 2 mm per 1,000 ft. Lidarvisor never writes both as "ft": US survey feet are ftUS on screen and USSurveyFoot in LandXML, feet are ft. State Plane systems are mostly in US survey feet (Texas, California, New York); some states use international feet (Arizona, Michigan, Oregon).

Heights not stated ​

When a LiDAR file does not state its heights, you can say what they are, or answer I don't know. "I don't know" is accepted for a LiDAR-only project: elevations are shown as they are in the file, and the heights of control points and photos can then be compared with the cloud, not converted. Beside photos, the LiDAR heights are needed, because the photo cloud must be converted to them.

Inputs ​

Point clouds ​

Lidarvisor reads the coordinate system and the heights a LAS or LAZ file states: a compound coordinate system (for example NAD83(2011) / Texas South Central (ftUS) + NAVD88 height (ftUS)), the GeoTIFF keys of the file, or a compound EPSG code (EPSG:7405, British National Grid + ODN height).

Drone photos ​

Photo altitudes are read automatically: RTK-tagged photos carry ellipsoidal heights; other photos carry heights above a global geoid. The photo cloud is written in the coordinate system and heights of the project, and it carries what was actually applied: if a geoid grid could not be applied, the heights stay ellipsoidal and are labelled ellipsoidal.

Raw DJI flights ​

The coordinate system and heights are proposed from where the flights are, from the same list as photos. The heights offered follow the coordinate system you choose.

Control points ​

A control-point file has its own coordinate system and heights. The horizontal system is stated in the file (a WKT comment line, an Emlid export), found by matching your point cloud, or chosen by you. When both the control points' heights and the cloud's are known, the control points are converted to the cloud's heights with your site's geoid grid before they are compared. When one side is not known, a constant difference close to the geoid separation at your site is named as a height-system difference, never reported as an accuracy figure. See Ground Control Points.

Imported files ​

Add data shows the coordinate system a GeoTIFF states before you import it, as it shows a shapefile's .prj. An elevation model in another system than the project's is converted to it on import. Its Heights are read from the file when it states them, otherwise you choose them (or leave I don't know: they are then read the way the file is written); they are converted to the project's heights. If an imported model's heights differ from your point cloud, click the heights warning on its row to set them.

An imported vector layer is drawn on the ground. One exception: a GeoJSON or shapefile layer whose heights, in metres, sit within your point cloud's is drawn at its own heights. That is the case of a Lidarvisor layer you downloaded and added back. KML and KMZ layers are always drawn on the ground.

Trajectories ​

Trajectory files are read in WGS 84 and used for the checks only. They do not change the project's systems.

Results ​

  • Elevations are shown in the heights' unit, with the height system's name when it is known: Elevation 214.63 m · NGF-IGN69 in the viewer, 702.15 ftUS NAVD88 on a copied point. Lengths, relative heights, clearances and areas stay in the coordinate system's unit. The same point shows the same elevation unit in the readout, the feature card and the measure tool.
  • Deliverables state the systems actually applied: LAS, LAZ, COPC and E57 carry the compound coordinate system; GeoTIFFs carry the vertical key and the band unit; shapefiles carry VERTCS in the .prj; LandXML carries the vertical datum and USSurveyFoot when it applies; DXF sets $INSUNITS to 21 for US survey feet.
  • The report states both values and never prints an accuracy figure from a height-system difference.

Examples ​

SiteCoordinate systemHeights
Houston, Texas, LiDAR in State PlaneNAD83(2011) / Texas South Central (ftUS) (EPSG:6588)NAVD88 · GEOID18 · US survey feet
Houston, photos onlyNAD83(2011) / UTM zone 15N (EPSG:6344)NAVD88 · GEOID18 · metres
Toronto, raw DJI flightsNAD83(CSRS) / UTM zone 17N (EPSG:2958)CGVD2013a(2010) · CGG2013an83 · metres
Lyon, photos onlyRGF93 v1 / Lambert-93 (EPSG:2154)NGF-IGN69 · RAF20 · metres
Mid-ocean or a site spanning two countriesWGS 84 / UTM zone of the siteEllipsoidal heights · metres

Questions ​

My cloud sits 30 m below the terrain. The heights are probably ellipsoidal while the terrain (or the control points) is in geoid heights, or the reverse. Check Heights for the file that differs.

Can I change a project's coordinate system or heights? Yes, until processing starts: click Change next to them in the project's details (the project list). A point cloud whose coordinate system changes is read again in the new one, which takes a few minutes. After processing the values are read-only: a project is processed once in its systems.

Can I get my results in a different system from my file's? Yes, free, before processing: see Delivering Your Results in Another Coordinate System.

Is GeoJSON in my coordinate system? No. GeoJSON is always written in WGS 84 longitude and latitude (EPSG:4326), as the GeoJSON standard requires. Shapefile, DXF, LandXML, GeoTIFF and the point clouds are in your project's system.

Lidarvisor — Process LiDAR in Minutes, Not Hours