Appearance
Raw DJI Zenmuse Data
If you fly a DJI Zenmuse L1 or L2, you do not need DJI Terra to get a point cloud. Upload the flight folders exactly as the drone wrote them on its SD card, and Lidarvisor computes the point cloud itself during processing: precise positioning (PPK) against a base station, the trajectory, flight line alignment and colour from the photos the payload took. The cloud then goes through every option you tick, in the same run and for one charge.
What to Upload
- Zenmuse L1 and L2. The Zenmuse L3 is not supported yet.
- One folder per flight, copied whole from the SD card, with its .LDR, .IMU, .RTK, .RTL and .CLI files.
- The base station file (.RTB) is optional. Without it, Lidarvisor uses a public base station near your site.
- Your own recording of the base station, when you have one. If your base logged its observations (a RINEX observation file:
.obs,.rnx,.crx, or.26ostyle names), leave that file in the flight folder or beside the flight folders (with a zip, put it beside the zip, not inside it). It is listed under Base station recording and uploaded with the flights. The .RTB only holds the corrections that reached the drone: when the radio or network link dropped during a flight, your recording fills the gap. Each flight is computed with whichever gives the better positions; a recording that does not cover a flight is simply not used for it. - The photos the payload took during each flight are part of the folder: they colour the cloud and can feed the photo products (see Photos).
You can select the survey folder that holds the flight folders, the flight folders themselves, or a zip. Every flight in the selection is found; the other files are left out.
Limits per project: the source's tooltip shows the current maximum number of flights and total size (by default 20 flights and 100 GB). Above that, split the flights into several projects. The raw files do not count against your plan's storage; the computed point cloud does.
Creating a Raw Project
- Click Create a project and name the project.
- Choose DJI Zenmuse raw folder (L1 / L2).
- Click Select folders or Select a zip, or drop the survey folder, mission folders, zips or files into the area. The files are read in your browser before anything is uploaded ("Reading the mission files...").
- Check the list of flights. Each row gives the flight's duration, whether a base station file is in the folder ("base station in the files", or "no base station: a public station will be used") and how many photos will colour the cloud. A flight flown with the camera tilted (an oblique flight) says "camera tilted: not used to colour the cloud": its photos are uploaded and feed the photo products, but only photos taken looking down colour the points. A flight that cannot be used says why under its row; Remove this flight takes it out of the selection.
- Check the Coordinate system (see below).
- Optional: add a separate photo flight, ground control points, an area of interest.
- Click Import project.
When a Flight Is Refused
| Message | What to do |
|---|---|
| No .LDR file in this folder | It is not a LiDAR mission folder, or the copy is incomplete. |
| Several .LDR files in one folder | Keep one flight per folder, as the drone writes them. |
| Missing (file names given) | Copy the whole folder again from the SD card. |
| Zenmuse L3 is not supported yet | Send us one mission at contact@lidarvisor.com and we will add it. |
| This .LDR file comes from a payload we do not read yet | Only Zenmuse L1 and L2 are read. Send us one mission and we will look at it. |
| Another flight in this selection has the same name | Keep one copy of each flight. |
| A mission file is unreadable or truncated | Copy the folder again from the SD card. |
Coordinate System and Heights
The coordinate system is proposed from where the flights are (the UTM zone, or a national system where one is used). Click Change to pick another one in the Coordinate system of your results picker. It must be a projected system, in metres or feet: the cloud is written in it. If the system you pick is not used where the flights are, the panel warns you with the distance.
Heights sets what the cloud's elevations are measured from: Ellipsoidal heights, or a height system whose geoid grid covers every flight, for example NAVD88 · GEOID18 · metres in the contiguous United States, CGVD2013a(2010) · CGG2013an83 · metres in Canada or NGF-IGN69 · RAF20 · metres in mainland France. The list follows the coordinate system you choose. See Coordinate Systems and Heights.
Photos
- The payload's photos are already included. The photos your L1 or L2 took during each flight colour the LiDAR cloud automatically, so the Colorize Point Cloud option is not offered. A flight without photos gives points without colour.
- A separate photo flight (an M3E, M4E, P1...) can be added in the Drone photos (folders) field under the flights. When your selection holds photo folders that are not flight folders, they are listed under Photo folders found in your selection: a folder is ticked when its photos are over the flights, and left unticked otherwise (for example photos of another site). Tick or untick each one.
- All the photos (the payload's and the ones you added) make one photo set, with its Photos row and photo panel, exactly as described in Drone Photos and Photogrammetry. Only the payload's photos colour the LiDAR cloud.
- The payload's photos belong to the raw data: they cannot be deleted on their own. Leaving photos out in the photo panel affects the photo products only, never the colour of the LiDAR cloud.
After Upload: the Flights in the Viewer
No point cloud is computed at import. Within seconds of the upload ("Reading the flights"), the viewer shows:
- a Raw LiDAR data row in the project tree, with the number of flights and photos and whether a base station is in the files, and the line "The point cloud will be computed when the project is processed.";
- the flight lines: where the drone flew while the LiDAR was recording, one colour per flight;
- the cameras: one point per payload photo, where it was taken.
When the project also has photos to read, Lidarvisor then reads them as on any photo project (thumbnails, photo check, the photos that should show each control point). Start Processing becomes available once the flights and the photos are read.
Processing a Raw Project
The Point Cloud Options category starts with Compute the point cloud from the raw LiDAR data. It is ticked and locked: "Always on for this project: its data is raw, and every other option needs the point cloud this computes." It positions every flight precisely (PPK), computes its trajectory, aligns its flight lines and writes the point cloud, then runs the options you tick on it.
- Thin Point Cloud sets the density of the cloud. It is ticked by default at 10 cm, about the density DJI Terra exports. The grid (5 to 100 cm) is applied to each flight before the flights are merged, so where flights overlap the cloud keeps one point per cell per flight. Untick it for full density: every return kept, several times larger and slower to process. The estimated cloud size is shown under the option; a size larger than your plan's storage can take is said there and refused when you start.
- Every other option works as on any cloud: classification, power lines, terrain models, vectors, reports.
- Photo products (Compute orthophoto from your photos, Compute photogrammetric point cloud) are offered when the project has photos. The photogrammetric point cloud is unticked by default: the LiDAR cloud is the project's cloud.
- You can also compute only the point cloud: untick every other option. The confirmation then reminds you that the project's processing is done once the cloud is computed (a project is processed once).
During the Run
The conversion is the first part of the run's progress: reading the raw files and the GNSS data, computing the base corrections (PPK), fetching a public base station when needed, computing the trajectory, aligning the flight lines, writing and saving the point cloud, flight by flight ("flight 2 of 8"), then merging the flights. When the project has photos, their steps run beside it ("Photos: Aligning the photos..."). Then the options you ticked run on the cloud.
- Waiting for public base station data. A public network publishes its data some time after your flight. If it is not out yet, the run waits and continues automatically.
- Storage. If the computed cloud is larger than the storage your plan has left, the run stops there and asks you to upgrade. Nothing is deleted for 30 days.
The Conversion Report
After the conversion, the Raw data conversion report opens from the badge on the Raw LiDAR data row (and on the computed cloud's row). One block per flight, marked OK, Note, Warning or Failed, says for example:
- the share of the flight positioned with precise GNSS corrections, and where the drone's own RTK had to bridge a gap;
- which base station was used: yours, your own recording of it (RINEX), a public station with its network and distance, or none (the drone's own real time RTK, with lower accuracy);
- when your recording is used and its station is not the one the drone received, that its position is the one written in the file's header (approximate unless you set it there);
- when your base station's declared position disagrees with its measured position, by how much, and whether the flight was positioned from the measured one;
- whether the flight lines were aligned, and the share of points removed as isolated noise;
- whether the points were coloured from the payload photos.
Warnings never stop the run.
When a Flight Cannot Be Converted
A flight that cannot be converted holds the run; it does not fail it. Our team is notified and will contact you. When the other flights can still make the cloud, the report also offers Continue without flight: the cloud is then made from the other flights only. You can also wait for our team to try to recover the flight. If neither happens, the run is eventually failed and your credits are refunded automatically.
Credits
1 credit per hectare of the area the LiDAR recorded, at least 5 credits per run, one charge for the conversion and everything you tick. This area is estimated from the flights when they are read, before you process; the confirmation dialog shows the exact number. An area of interest crops the results but does not lower the price: every flight is converted.
When you added a separate photo flight and tick a photo product, the area also includes the part of the added photos that lies outside the LiDAR area. The payload's own photos never add to the area.
Next Step
The photo set of a raw project works like any other: see Drone Photos and Photogrammetry for the photo panel, control points on the photos and the accuracy report.