Appearance
Creating a Project
A project in Lidarvisor is a container for one dataset (a LiDAR point cloud, drone photos, or both) and all the products generated from it (classified point cloud, terrain models, vectors, reports). This page explains how to create a project by uploading your data.
Supported File Formats
Lidarvisor accepts the following file types for point cloud data:
| Format | Extension | Description |
|---|---|---|
| LAS | .las | The standard LiDAR point cloud format. Contains 3D coordinates and attributes for each point. |
| LAZ | .laz | A compressed version of LAS. Same data, smaller file. Recommended for faster uploads. |
| COPC | .copc.laz | Cloud-Optimized Point Cloud. A modern format designed for efficient streaming. |
A survey delivered as several tiles — multiple LAS, LAZ, or COPC files covering one area — can be uploaded together into a single project. See Uploading a Tiled Survey below.
Point clouds produced by photogrammetry (drone imagery processed in tools like Metashape, Pix4D, or RealityCapture) are accepted in the same formats. Mark them as photogrammetric when you process — see Processing Your Data for how they are handled.
You can also upload the drone photos themselves, as JPEG files, instead of a point cloud or beside it. Lidarvisor then computes the photogrammetric point cloud and an orthophoto from them during processing. See Drone Photos and Photogrammetry.
If you fly a DJI Zenmuse L1 or L2, the raw flight folders from the drone's SD card can be uploaded directly: Lidarvisor computes the point cloud. See Raw DJI Zenmuse Data.
You can also optionally add an orthophoto (aerial image) to your project:
| Format | Extension | Description |
|---|---|---|
| GeoTIFF | .tif / .tiff | A georeferenced image file. You can upload up to 100 TIFF files per project. Their size is limited in pixels, see below. |
| ECW | .ecw (with its .prj if it has one) | A compressed georeferenced image, common for national and commercial orthophotos. It is decoded once into a tiled GeoTIFF for processing and display; the original ECW stays downloadable. An ECW that cannot be read, has no georeferencing or no known coordinate system is refused with the reason. |
File Size Limits
The maximum file size depends on your subscription plan:
| Plan | LAS Limit | LAZ Limit |
|---|---|---|
| Freemium | 5 GB | 1 GB |
| Lite | 10 GB | 2 GB |
| Premium | 25 GB | 5 GB |
| Advanced | 250 GB | 50 GB |
Why is the LAZ limit lower? LAZ is a compressed format — a LAZ file typically expands to about five times its size as LAS. The LAZ limit is the LAS limit divided by five, so both formats allow roughly the same amount of actual data.
For a multi-tile upload, the limit applies to the combined size of all the tiles — there is no separate per-tile allowance.
The factor of five applies to the file size limit only. Against your plan's total storage, a LAZ file counts at its real size.
Orthophoto Size Limit
An orthophoto is limited by its number of pixels (width × height, added up over all its TIFF files), not by its size on disk:
| Plan | Orthophoto limit |
|---|---|
| Freemium | 1 gigapixel |
| Lite | 4 gigapixels |
| Premium | 10 gigapixels |
| Advanced | 40 gigapixels |
The file picker reads the TIFF headers and shows the total in gigapixels (Gpx) beside the file size, before anything is uploaded. An orthophoto at or above your plan's limit is refused with both figures, followed by an offer to upgrade. The TIFF files also count, at their real size, against your plan's file size limit and storage.
Step-by-Step: Create a Project
1. Open the Create Project Panel
Click the Create a project button in the top toolbar. A panel will slide open on the right side of the screen.
2. Name Your Project
Type a name for your project. This can be anything that helps you identify it — for example, the site name, date, or client name.
3. Select Your LiDAR File(s)
Click the file picker labeled "LiDAR file(s) — .las, .laz, .copc.laz" to browse for your point cloud, or drag and drop it into the area. You can select a single file, or multi-select several tiles if your survey was delivered pre-split — see Uploading a Tiled Survey below. The selected files are listed with their count and total size.
The point cloud is optional when you upload drone photos (next step), but the project needs one or the other: "Choose a point cloud, drone photos, or both."
When the raw DJI source is available on your account, the panel first asks which source you have: Point cloud file (LAS / LAZ) or DJI Zenmuse raw folder (L1 / L2). Pick the second one to upload raw flight folders instead of a LAS file, see Raw DJI Zenmuse Data.
4. (Optional) Add Drone Photos
If you have the photos your drone took over the site, pick the folder of each flight in Drone photos (folders), or click Choose JPEG files instead. Only the JPEG photos are kept. With photos, the processing panel offers a photogrammetric point cloud and an orthophoto computed from the photos, and your control points are placed on the photos automatically during the run. On a project with photos only, a Coordinate system block appears under the field: the system is proposed from the photos, and you choose the Heights reference. See Drone Photos and Photogrammetry.
5. (Optional) Add an Orthophoto
If you have aerial imagery of the same area, check the Add an orthophoto (optional) box. A second file picker will appear where you can select one or more GeoTIFF or ECW files.
An orthophoto is not required for processing, but it provides a satellite-like image layer that you can overlay on your point cloud in the viewer, and it improves the results of some detections (roads, water).
6. (Optional) Add an Area of Interest
If you only want to process part of the surveyed area, check the Add an area of interest (optional) box and upload a boundary file. Processing will be cropped to your boundary, and credits are counted on that area only. See Cropping to an Area of Interest below for details.
7. (Optional) Add the Flight Trajectory
If your processing software gave you a trajectory file for each flight, check Add the flight trajectory (optional) and select the files. Lidarvisor uses the trajectory to separate your flight lines, and ticks the flight-line option for you when you start processing. A project without a trajectory processes normally: the flight lines are then worked out from the point cloud. See Trajectory Files for which files are read.
8. Click "Import project"
Lidarvisor will begin uploading your file. You will see a progress bar showing the upload status.
What Happens During Upload
Upload — Your file is sent to Lidarvisor's cloud servers. The upload is resumable: if your internet connection drops, the upload will automatically resume from where it left off when you reconnect. You can also manually pause and resume the upload. In a multi-tile project, the tiles upload one after another, each with its own progress.
Merging (multi-tile projects only) — Your tiles are merged into a single point cloud. You will see a "Merging tiles..." step in the progress messages.
Tiling — Once the upload finishes, Lidarvisor converts your point cloud into a format optimized for 3D viewing (called "3D Tiles"). This allows you to explore even very large datasets smoothly in the browser.
Metadata extraction — The platform reads your file to determine its geographic location, coordinate system, number of points, area, and other properties.
When these steps are complete, your point cloud appears in the 3D viewer and you can start exploring it.
Uploading a Tiled Survey
Aerial LiDAR surveys often arrive from the provider split into flightline or grid tiles. You do not need to merge them on your own machine — select all the tiles together in the LiDAR file picker and Lidarvisor merges them for you on the server.
The rules for a tile set:
- Up to 50 tiles per project.
- Same format: all
.las, all.laz, or all.copc.laz— mixed sets are refused before any upload starts. - Same coordinate system: all tiles must be in one coordinate system. A mismatched set is refused up front, before you spend time uploading, with the systems it found. Two codes for the same grid with the axes in another order count as one.
- Unique filenames: two tiles cannot share the same name.
- The combined size counts toward your plan's file size limit.
How it works:
- Tiles upload one at a time, each with per-tile progress. A tile that fails can be retried without re-uploading the ones that already finished, and an interrupted upload resumes where it left off.
- After upload, the tiles are merged into one point cloud. From then on, your project behaves exactly like a project created from a single file: one point cloud in the project tree, one set of statistics (size, point count, area) computed from the merged cloud, and all processing results produced from the merged cloud.
- The project's area — and therefore its credit cost — is measured on the merged point cloud.
Cropping to an Area of Interest (AOI)
An area of interest is a boundary polygon that restricts processing to a sub-area of your point cloud. It is useful when your LiDAR file covers more ground than you actually need — a whole flight when you only care about one parcel, for example. Processing is cropped to the boundary before it starts, which saves time, and credits are counted on the AOI area instead of the whole file.
To add one at project creation, check Add an area of interest (optional) and upload a boundary file. Supported formats:
| Format | How to upload |
|---|---|
| KML / KMZ | Single file (e.g. drawn in Google Earth) |
| GeoJSON | Single file (.geojson or .json) |
| Shapefile | Either a single .zip, or multi-select the loose sibling files together: .shp + .shx + .dbf + .prj |
You can also set an optional buffer — an outward expansion of your boundary, entered in meters or feet (up to 10,000 m). Use it to include a margin around your shape, such as a skirt around a parcel boundary or a forest plot. 0 means no buffer.
A few things to know:
- The AOI crop is applied at processing time. Until then, the full point cloud is uploaded and shown in the viewer.
- If you skip this at creation, you can still crop the point cloud later from the crop icon in the viewer toolbar — as long as processing has not started.
- The AOI works the same on single-file and multi-tile projects.
- If your boundary does not overlap the point cloud at all (usually a wrong coordinate system, or a shape drawn elsewhere), the processing confirmation says so, and the whole cloud is processed and charged.
Trajectory Files
A trajectory is the aircraft's own position through a flight, after post-processing. Add one file per flight.
Files we read:
| File | Where it comes from |
|---|---|
POSPac SBET (sbet.out) | Applanix POSPac, the binary trajectory |
POSPac text export (sbet.txt) | The same trajectory as text. Its header must name the Time, Latitude and Longitude columns, with a units line saying radians or degrees |
DJI Terra POS (…mission_0.out) | DJI Terra, the binary POS file written beside the point cloud |
Accuracy files (optional): the smrmsg files stored beside POSPac trajectories hold accuracy figures, not positions. You can add them with the trajectory: they are listed as an accuracy file, used for the flight quality check. Align Flight Lines reads them to tell a line spoiled by a poor navigation solution apart, and Drop unrecoverable lines needs them. See Processing Your Data.
Not read yet:
- DJI Terra's text copy of the trajectory (
…mission_0.txt). Pick the.outfile beside it instead. - Other text layouts, CSV files, and trajectories written in projected X/Y coordinates rather than latitude and longitude (for example a
Time X Y Elevationexport). You will see the file's first line quoted back, so you can tell which layout was not recognised.
How a trajectory is matched to your point cloud. By time first: the trajectory's timestamps must overlap at least half of the shorter of the two time spans. A trajectory of a whole flight or a whole day is therefore fine for a point cloud that covers only part of it. We try GPS week time, GPS time, adjusted GPS time and Unix epoch time, so you do not need to convert the clock. Then by position: the trajectory must follow the flight path the point cloud itself records, within 15 m. A trajectory from a different flight is set aside, the report says so, and the flight lines are worked out from the point cloud instead.
When two files cover the same stretch of time, the one that matches the point cloud's flight path more closely is used for it.
Limits: up to 60 files per project, 512 MB each.
Coordinate Systems and Heights
Under your files, the Coordinate systems block shows the project's coordinate system and heights before you import, each with where it came from and a Change link: the file's when it states them, proposed from where your photos or flights are otherwise. A LiDAR file that does not state its heights offers I don't know; beside drone photos its heights must be chosen, because the photo cloud is converted to them.
Every LiDAR file is captured in a coordinate system, the rules that turn its X and Y into positions on Earth, and its elevations are measured from a height system (its heights). A coordinate system is named with its standard EPSG code in brackets, for example NAD83(2011) / Texas South Central (ftUS) (EPSG:6588). See Coordinate Systems and Heights for the whole model.
Automatic Detection
Lidarvisor automatically reads the coordinate system from your file's metadata, and the heights when the file states them (a compound coordinate system such as RGF93 v1 / Lambert-93 + NGF-IGN69 height, or the file's GeoTIFF keys). In most cases, this works without any input from you.
In a multi-tile project, the coordinate system is read from each tile. All tiles must be in one system — a mixed set is refused before the upload starts. If none of the tiles states a coordinate system, you are asked to choose one once, and your choice applies to the whole set. If only some tiles state one, you are asked to confirm it for the whole set, with the stated one selected.
Manual Selection
If the coordinate system cannot be detected automatically (for example, if the file was created without proper metadata), Lidarvisor will ask you to specify it. You have two options:
Search: if you know the coordinate system or its EPSG code, search for it in the table that appears. You can filter by name, code, or region. The list comes from the EPSG database; a system that has been superseded is marked No longer in use, with the code that replaces it.
Find it for me: if you do not know the coordinate system, switch to the Find it for me tab and enter a city, an address, or GPS coordinates of the survey area. Lidarvisor works out the best matching coordinate system during processing.
When the Cloud Would Land Somewhere Else
Lidarvisor checks where your cloud lands in the coordinate system it is given. When a file declares a system, or you pick one, that would put the cloud outside the area where that system is used, you see a warning next to the picker. It says where the cloud would land (for example a named country, or a latitude and longitude), the area where the system is used, and, when it can, the coordinate systems that place your cloud inside their own area.
This is a warning, not a refusal. If you are sure of the system, you can still confirm it. The same warning appears on the point cloud's row in the project tree and in the processing confirmation dialog, so a wrong system is caught before you spend credits on it.
Tip: If you are unsure which coordinate system your data uses, ask the person who collected the LiDAR data, or check the documentation that came with the dataset.
Files with Local Coordinates
Some LiDAR files use "local" or "arbitrary" coordinates: X and Y values near 0, 0 that are not tied to a standard geographic reference. Lidarvisor detects this situation, opens the Find it for me tab, and asks you for the location of the survey. Tick My data uses local/arbitrary coordinates (not geo-referenced) and enter the GPS coordinates (latitude, longitude) of the centre of your point cloud: the data is then placed at that location in the WGS 84 / UTM zone of that place, in metres, with no rotation, during processing. A file whose numbers are longitude and latitude in degrees is not treated as local coordinates.
A file that states a projected coordinate system but whose coordinates are near 0, 0 gets a warning: its numbers look like local coordinates, not a position in that system.
Adding Your Own Files After Creation
Add data in the project tree adds your own files to an existing project:
| Kind | Formats | What it is used for |
|---|---|---|
| Orthophoto | GeoTIFF or ECW | Shown as an image layer. If the project is processed later, processing uses its most recent orthophoto instead of generating one. |
| Elevation model (DTM or DSM) | GeoTIFF | Shown in 3D only: never used for contours, slope or any other product. You say whether it is a terrain (bare ground) or a surface model. |
| Vector layer | Shapefile (.shp with .shx, .dbf, .prj, or zipped), GeoJSON, KML or KMZ | Shown in the viewer, filed in the tree category you choose. It is for viewing: it does not become one of Lidarvisor's layers. |
The coordinate system each file states (a GeoTIFF's own, a shapefile's .prj) is shown before you import, and an elevation model in another system is converted to the project's. Imported files count against your storage. See Coordinate Systems and Heights.
Finding Free LiDAR Data
Don't have your own LiDAR data yet? Lidarvisor provides a link to a guide on finding free, open-source LiDAR datasets. You can find it in the Create a project panel — look for the "Find free LiDAR data" button below the file picker.
Many countries and regions publish free aerial LiDAR data that you can download and upload to Lidarvisor to try the platform.
Managing Your Projects
Viewing Your Projects
Click My projects in the top toolbar to see a list of all your projects. Each project shows:
- Its name
- Its status (Uploading, Tiling, Processing, Ready, Error)
- A View button to load it in the 3D viewer
Click the arrow next to a project name to expand it and see details from the LAS file header (number of points, area, etc.).
Renaming a Project
Click the pencil icon next to a project name in the project list, or next to the project name in the left panel when the project is loaded.
Deleting a Project
Click the trash icon next to a project in the project list. A confirmation dialog will appear. Deleting a project removes all associated data — the original file, all processed results, and all generated deliverables. This action cannot be undone.
Loading a Project
Click View next to any project to load it in the 3D viewer. The project's assets will appear in the left panel (the project tree), and the point cloud will be displayed in the viewer.
Upload Troubleshooting
| Issue | Solution |
|---|---|
| Upload seems stuck | Check your internet connection. The upload is resumable — it will continue automatically when the connection is restored. You can also try pausing and resuming manually. |
| My survey came as many separate tiles | Select them all together in the LiDAR file picker (up to 50 tiles of the same format) — Lidarvisor merges them into one point cloud for you. See Uploading a Tiled Survey. |
| "All tiles must be the same format" or "Your tiles are in different coordinate systems" | Your tile set mixes formats (e.g. .las with .laz) or coordinate systems. Re-export the odd tiles so the whole set matches, or upload only the matching subset. |
| One tile failed during upload | Retry just that tile from its row in the list — tiles that already finished are not re-uploaded. |
| "File too large" error | Your file exceeds the size limit for your plan. Compressing LAS to LAZ does not help: a LAZ file counts five times its size against the limit. Crop the file to the area you need, or upgrade your plan. |
| "…is not a LAS or LAZ file, whatever its extension says" | The file was renamed rather than exported (a CloudCompare .bin renamed .las, for example). Export the cloud as LAS or LAZ from your software and select it again. |
| "The orthophoto cannot be imported because its size in pixels exceeds the current plan limit" | Your orthophoto has more pixels than your plan allows (see Orthophoto Size Limit). Resample it to a coarser resolution, crop it, or upgrade your plan. |
| "Storage limit reached" | You have used all available storage on your plan. Delete old projects you no longer need, or upgrade your plan. |
| "Choose a point cloud, drone photos, or both." | The project has no data yet. Pick a LiDAR file, the folders of your drone photos, or both. |
| "Project limit reached" | Freemium accounts are limited to 5 projects. Delete an old project or upgrade to any paid plan (Lite, Premium or Advanced) for unlimited projects. |
| Point cloud does not appear after upload | The tiling step may still be in progress. Check the status indicator in the project list. If it shows an error, try creating a new project with the same file. |
| Point cloud appears in the wrong location | The coordinate system was likely stated incorrectly in the file, or your file uses local coordinates. Delete the project and upload the file again — when prompted, choose the correct coordinate system or use Find it for me. If you are unsure of the correct code, ask the person who collected the data or check your drone/sensor software settings. |
| Not sure how many credits I need before uploading | Upload the file first — Lidarvisor calculates the area automatically during metadata extraction. You will see the exact credit cost before confirming processing. Uploading itself does not consume credits. |
Preparing Files from Common Drones
If you just collected LiDAR data with a drone and are not sure how to get a LAS or LAZ file, here are common workflows:
| Drone / Sensor | Software | How to Export LAS/LAZ |
|---|---|---|
| DJI Zenmuse L1 / L2 | DJI Terra, or none | Process the flight, then export as LAS or LAZ from the point cloud panel. Or upload the raw flight folders and let Lidarvisor compute the cloud, see Raw DJI Zenmuse Data |
| Livox Mid-360 / Avia | Livox Viewer or Livox Mapping | Convert recorded data to LAS using the built-in export tool |
| ROCK Robotic R3Pro | ROCK Cloud / PCMaster | Download the processed LAS file from your ROCK dashboard |
| YellowScan | YellowScan CloudStation | Export the processed trajectory as LAS |
| RIEGL miniVUX / VUX | RiPROCESS | Export point cloud as LAS from the project |
| Emlid / generic PPK drone | Emlid Studio + CloudCompare | Post-process the trajectory, then export the georeferenced point cloud as LAS |
Tip: If your drone software does not directly export LAS/LAZ, you can often export to a text file (CSV with X, Y, Z columns) and convert it to LAS using the free tool CloudCompare.
Next Step
Your data is uploaded and visible in the viewer. Let's learn how to explore it. Head to The 3D Viewer.