Appearance
Processing Your Data
One click. All your deliverables. Lidarvisor's AI classifies every point in your cloud and generates the terrain models, vectors, and reports you need — typically in minutes, not the hours required by desktop tools.
First time? You do not need to understand every option below. For your first processing run, just pick the preset that matches your job at the top of the panel (or keep the default) and click Start Processing, the AI classification runs automatically. A project is processed once, so tick every output you might need: the credit cost is the same regardless of how many options you enable (Precision mode excepted, see below).
Before You Start
Before processing, verify:
- Your project has finished uploading and tiling (the status should show the project is ready)
- Metadata extraction is complete (Lidarvisor automatically reads your file's properties after upload)
- Your point cloud looks correct in the 3D viewer — check that it appears in the right geographic location and the points look reasonable
- You have enough credits for your dataset: 1 credit per hectare processed (about 2.5 acres), with a minimum of 5 credits per run
How to Start Processing
- Load your project in the 3D viewer by clicking View in the project list.
- Look at the left panel — below the project tree, you will see the Processing Options section: a preset picker at the top, followed by collapsible option categories.
- Pick a preset that matches what you are surveying (see Processing Presets below).
- Fine-tune your options if needed (see below for details on each one).
- Click the Start Processing button at the bottom of the left panel.
- A confirmation dialog will appear showing how many credits will be consumed. Confirm to start processing.
Processing Presets
At the top of the Processing Options panel, Lidarvisor asks "What are you surveying?" and offers five presets. A preset simply ticks the right options for a common type of job — it is a starting point, not a lock. Every option stays visible and editable below, so you can always see exactly what a preset selected and change any part of it.
| Preset | What it sets up |
|---|---|
| Classification only | Classify the point cloud and stop there — no derived layers. Good for a first look at a new dataset. |
| Topographic survey (default) | The survey plan: major contours, breaklines, grid, buildings, bridges, roads, rails, power lines and towers, vegetation areas, parcels, an orthophoto and the topographic map. Water, shoreline and minor contours are not included: tick them if your site needs them. |
| Forestry & vegetation | Canopy height, tree crowns and tops, and a forest inventory. |
| Power line inspection | Conductors, towers, clearance, and encroachment along the corridor. |
| Site & infrastructure | Buildings, roads, rails, bridges, overhead utilities, and parcel boundaries. |
How the picker behaves:
- Selecting a preset ticks the matching options. Each category header shows a count of enabled options (for example, "2/5"), so you can see what changed without expanding anything.
- Nothing is locked. Change any option and the preset label becomes "Custom, based on ..." — the run uses exactly what is ticked, not the preset name.
- Re-selecting a preset resets to it, discarding your manual edits.
- Save your own presets. Click "Save current settings as a preset" to store the current configuration under a name of your choice. Your saved presets appear below the built-in ones and can be deleted at any time.
- Presets never change the credit cost. Pricing is based on area only (at least 5 credits per run), no matter which preset or options you choose. Only Precision mode adds credits.
Processing Options Explained
The options are organized into collapsible categories: Point Cloud, Imagery, Terrain, five vector categories (Topography, Infrastructure, Hydrography, Vegetation, and Power Line), and Reports. You can enable or disable each option independently.
A project is processed once. After the run, the panel shows its result and no longer offers Start Processing, so choose every output you need before you start. No option changes the credit cost, except Precision mode (see Precision Mode).
AI classification is always included — it runs automatically every time you process. You do not need to enable it separately. This alone is a major time-saver: traditional desktop tools require you to configure classification parameters manually, which can take hours to get right.
Flat pricing: Enable as many outputs as you want — DTM, DSM, contours, buildings, trees, reports — the credit cost is based only on the area of your dataset (at least 5 credits per run), not the number of outputs. There is no reason to hold back. Precision mode (paid plans) is the one exception: it adds a price per hectare for the layers you switch it on for, shown before you confirm.
Photogrammetric Point Cloud Options
Shown first when the project has drone photos:
- Compute photogrammetric point cloud: builds a coloured point cloud from your photos. Ticked by default on a project with photos only, where every other option runs on it. With a LiDAR cloud as well, it is delivered beside the LiDAR cloud and is not classified.
- Photogrammetric cloud quality: Low, Medium (default) or High, shown while the cloud is ticked. A higher level computes depth more finely, for more detail on edges and small objects, and takes longer. Same price at every level.
See Drone Photos and Photogrammetry for the details.
Point Cloud Options
On a project with LiDAR and drone photos, this category is titled LiDAR Point Cloud Options: its options apply to the LiDAR cloud.
These options modify your point cloud during processing.
Photogrammetric Point Cloud
If your point cloud comes from photogrammetry — drone photos processed into a point cloud in a tool like Metashape, Pix4D, or RealityCapture — turn on the Photogrammetric Point Cloud toggle under the classification checkbox. Lidarvisor also tries to detect this automatically from your file's properties when you upload it.
Why it matters: a photogrammetric cloud only captures surfaces the camera can see. It does not see the ground under dense vegetation, and it does not reconstruct thin wires. Lidarvisor adapts the available options accordingly:
- The power line options and the vegetation encroachment report are disabled — photogrammetry cannot reconstruct power line conductors, so these results would come back empty.
- Photogrammetric clouds always carry colors, so colorization is unnecessary (the option is hidden) and the orthophoto can be generated directly from your points (see Imagery Options below).
- Align Flight Lines is not offered: a cloud built from photos has no LiDAR flight lines to align.
Everything else — classification, terrain models, contours, buildings, trees, and reports — works the same way as for a LiDAR point cloud.
If you uploaded the drone photos rather than a cloud computed elsewhere, Lidarvisor computes the photogrammetric cloud itself, and this switch is on and locked. See Drone Photos and Photogrammetry.
Compute the Point Cloud from the Raw LiDAR Data
On a project created from raw DJI Zenmuse L1 or L2 folders, this option comes first in the category, ticked and locked: the point cloud is computed from the raw flights at the start of the run, then every other option runs on it. Its density is set by Thin Point Cloud (10 cm by default). See Raw DJI Zenmuse Data.
Align Flight Lines
A survey is flown as several overlapping passes, called flight lines. When one of them is offset from its neighbours (a few centimetres up or sideways, for example), every product built on it inherits the step. Align Flight Lines finds the lines, checks how well each one fits its neighbours, and corrects only the ones that are clearly off, on the axis where they are off.
- It runs before classification, so the classified cloud, terrain models, contours and vectors are all built from the corrected data. Your uploaded file is never modified.
- Lines that already fit are left untouched. Lines whose offset is borderline, or whose overlaps disagree with each other, are reported but not moved.
- It needs at least three overlapping lines: with only two, there is no way to tell which one is off.
- The lines are found from the GPS time of your points. If your cloud carries no GPS time, the panel says so under the option, and ticking it changes nothing.
- If you added the flight trajectory when creating the project, the option is ticked for you, and the trajectory is also used to tell whether a bad line comes from the aircraft's positioning, in which case it needs flying again rather than correcting.
- If alignment is not possible on your data, processing continues on the cloud as delivered.
Drop unrecoverable lines (off by default) removes the lines that alignment cannot repair, usually because the navigation solution was poor for the whole flight. This deletes their points from your delivery and reduces coverage, and the report states exactly which lines were dropped. Telling these lines apart needs the trajectory accuracy files (smrmsg) uploaded with the trajectory. With the option off, those lines are kept and the report lists their PointSourceId, so you can filter them out in your own software.
After processing, a Flight Lines layer shows one line per pass, coloured by its verdict (CLEAN, BAD-X / BAD-Y / BAD-Z, Borderline, Inconsistent, or an edge line with a single neighbour), and the project report gains a flight line consistency section. If you uploaded a trajectory, a Trajectory layer draws the recorded flight path in cyan.
Colorize Point Cloud
Adds natural RGB colors to your point cloud using satellite imagery. This is useful if your LiDAR sensor did not include a camera, so your points have no original color. After colorization, your points will look similar to a satellite photo when viewed in RGB mode.
When the project also has your drone photos, the cloud is coloured from them, and from satellite imagery only where no photo covers it (see Drone Photos and Photogrammetry).
This option only appears when your point cloud has no colors — if your points already carry RGB values, there is nothing to add and the option is hidden.
Thin Point Cloud
Reduces the number of points in your dataset by keeping only one point per grid cell. This is useful when your data is extremely dense and you want smaller file sizes or faster viewing.
- Grid size (5 to 100 cm): The smaller the grid, the more points are kept. A 10 cm grid keeps high detail; a 50 cm grid creates a significantly lighter dataset.
On a project with LiDAR, it applies to the LiDAR point cloud; on a project made from drone photos only, to the photogrammetric point cloud. The tooltip names the cloud it applies to.
Smooth Point Cloud
Reduces noise in your point cloud by slightly adjusting point positions to create smoother surfaces. Useful for noisy LiDAR data where points "jitter" around the true surface.
- Soft — Gentle smoothing. Best for already clean data where you just want a small improvement.
- Medium — Moderate smoothing. Good for typical aerial LiDAR data.
- Aggressive — Strong smoothing. Use for very noisy data, but be aware that fine details may be softened.
Your acquisition timestamps are preserved. The classified point clouds you download keep the original GPS timestamps recorded by your sensor, in the original time format, along with the original file creation date. If your source file has no timestamps, none are invented.
Imagery Options
Which options this category shows depends on your project: Generate Orthophoto when you have not uploaded your own orthophoto (Compute orthophoto from your photos when the project has drone photos), and Repair Orthophoto when you uploaded an orthophoto.
Generate Orthophoto
Creates an orthophoto — a top-down, georeferenced aerial image of your survey area — that you can view as an image layer and download with your results.
- If your point cloud has colors (RGB), the image is built by rasterizing your points.
- If your point cloud has no colors, open-source satellite imagery of the area is used instead.
This option turns on automatically when road extraction is enabled (roads need an orthophoto), but you can still toggle it yourself.
Common uses: Base maps for plans and reports, visual context for deliverables, sharing a recognizable image of the site.
Compute Orthophoto from Your Photos (Projects with Drone Photos)
When the project has drone photos, Compute orthophoto from your photos takes the place of Generate Orthophoto: it assembles your photos into one orthophoto. Roads, road markings, water and rails read it. Not offered when you uploaded your own orthophoto. See Drone Photos and Photogrammetry.
Repair Orthophoto
Offered when you uploaded your own orthophoto, unticked by default. It fills the holes of your orthophoto and, where your LiDAR scan is dense and coloured, replaces the tree canopy with the scan's real colours, which removes the smeared or "melted" trees that some photogrammetry software produces. Sharper trees in your orthophoto will become slightly softer.
- Nothing is invented. Every repaired pixel comes from a measurement: the colours of your LiDAR points. A small hole (under about 2 m wide) where the LiDAR has no colours is interpolated from its edges; a larger one is left as it is. Gaps that open onto the edge of the mosaic are not filled.
- Your original is kept. After processing, an Orthophoto (repaired) layer appears below the original and is shown in its place, and a Repaired zones layer outlines every area that was changed, with its type (hole or tree canopy), its source (your LiDAR scan's colours, interpolated from its edges, or none) and its effective resolution. Every pixel outside these outlines is the original. A summary on the layer reads, for example, "12 holes filled, 3.4 ha of tree canopy replaced with your LiDAR scan's colours (5 cm)".
- When the canopy is left untouched, the summary says why: the project has no LiDAR scan, the point cloud was computed from photos, the scan carries no colours, or it is too sparse to replace the canopy faithfully. Holes are still repaired.
- Like every option, it adds nothing to the credit cost. The repaired orthophoto downloads as a GeoTIFF and the repaired zones in the vector formats.
Terrain (Raster) Options
These options generate terrain model images (rasters) from your classified point cloud. Each one is a map-like image where every pixel represents a value (elevation, height, slope, etc.). All raster outputs are in GeoTIFF format.
For detailed explanations of each terrain model type (with visual descriptions and use cases), see Terrain Models. Below is a quick summary of each option.
Generate DTM (Digital Terrain Model)
Creates a map of the bare ground surface — as if all trees, buildings, and other objects were removed. The DTM shows what the natural terrain looks like underneath everything. It also generates a hillshade visualization, which adds simulated sunlight and shadows to make the terrain shape easier to see.
- Resolution (10 to 3000 cm): The size of each pixel. A 50 cm resolution means each pixel covers 50 cm on the ground. Lower values = more detail but larger files.
Common uses: Topographic mapping, flood modeling, construction planning, volume calculations.
Generate DSM (Digital Surface Model)
Creates a map of the top surface — including treetops, rooftops, and other elevated features. Unlike the DTM which shows bare ground, the DSM shows the highest point at each location.
- Resolution (10 to 500 cm): Same as DTM.
Common uses: Urban planning, line-of-sight analysis, building height estimation.
Generate CHM (Canopy Height Model)
Creates a map of the height above ground of vegetation, buildings and other structures. It is close to the difference between the DSM (top surface) and the DTM (bare ground). Bare ground shows about zero height; tall trees show their actual height. Unlike the DSM and DTM it is not gap-filled (no value where there is no point) and it keeps the noise classes; see Terrain Models.
- Resolution (10 to 500 cm): Same as DTM.
Common uses: Forestry (tree height mapping, canopy analysis), vegetation management, habitat assessment.
Generate Slope Map
Creates a map showing how steep the terrain is at every point. The result is color-coded from flat (level terrain) to very steep. It uses an international classification system:
| Category | Slope |
|---|---|
| Level | 0 – 0.5% |
| Nearly Level | 0.5 – 2% |
| Very Gently Sloping | 2 – 5% |
| Gently Sloping | 5 – 10% |
| Moderately Sloping | 10 – 15% |
| Strongly Sloping | 15 – 30% |
| Steeply Sloping | 30 – 45% |
| Very Steeply Sloping | > 45% |
- Resolution (10 to 500 cm): Same as DTM.
Common uses: Erosion risk assessment, construction suitability, accessibility planning, agriculture.
Generate TIN (Triangulated Irregular Network)
Creates a faceted 3D terrain mesh by connecting ground points into triangles. Unlike the smooth DTM, a TIN preserves the angular, faceted look of the triangulation. It is commonly used in CAD and civil engineering workflows.
- Resolution (10 to 500 cm): Controls the density of the triangulation.
Common uses: CAD integration, civil engineering design, cut-and-fill calculations.
Flow Accumulation
Shows where water concentrates when it runs off the ground: the deeper the blue, the larger the area draining to that spot. It is part of the hydrology options, together with the drainage axes, depressions and sub-basins described under the vector options below. Each of the four can be ticked on its own.
- It is built from the ground points, so it does not need the DTM option.
- It comes with a conditioned terrain: the terrain with its depressions breached, then filled, so every cell drains. This terrain is downloadable, ready for a flood model.
- There is no threshold to set: every threshold is derived from your data and written into the results.
See Terrain Models for what you get.
Common uses: Drainage design, flood risk, erosion, locating wet spots and culverts.
Vector Options
These options generate vector deliverables — points, lines, and polygons that represent specific features detected in your data. All vectors are available in three formats: GeoJSON, Shapefile, and DXF.
In the panel, the vector options are split across five categories: Topography Vectors (contours, grid, breaklines, cadastral parcels), Infrastructure Vectors (buildings, bridges, roads, road markings, rails), Hydrography Vectors (water body, shoreline, drainage axes, depressions, sub-basins), Vegetation Vectors (tree crowns, tree tops, vegetation areas), and Power Line Vectors (power lines, towers). The most common options are described below.
For detailed explanations of each vector type (with attribute descriptions and use cases), see Vectorization. Below is a quick summary of each option.
Generate Contours
Creates elevation contour lines — lines that connect points of equal elevation, like the curves you see on a topographic map.
- Major interval (10+ cm): The spacing between main contour lines (e.g., every 5 meters). Major contours are typically drawn with thicker lines and labeled with elevations.
- Minor interval (10+ cm): The spacing between secondary contour lines (e.g., every 1 meter). Minor contours add detail between the major lines.
Common uses: Topographic maps, terrain visualization, engineering surveys.
Generate Grid
Creates a regular grid of elevation points sampled from the terrain model. Each point has X, Y, and Z coordinates.
- Resolution (50 to 10,000 cm): The spacing between grid points. For example, 500 cm means one point every 5 meters.
Common uses: CAD import, volume calculations, spot elevation maps.
Extract Buildings
Detects and outlines building footprints — the shapes of buildings as seen from above.
- Simplification mode:
- Rural — Produces clean, simplified outlines. Best for isolated buildings in rural areas.
- Urban — Produces more detailed outlines that follow complex building shapes. Best for dense urban areas.
- Natural — Follows the detected shape closely with minimal simplification.
Common uses: Cadastral mapping, urban planning, 3D city modeling.
Extract Roads (Beta)
Detects road surfaces and extracts their outlines. This feature uses AI-powered image recognition to identify roads in the data.
- Mode:
- Rural: Optimized for paved country roads. Dirt tracks and field paths are not roads: they are the Tracks layer, which comes from map data (see Vectorization).
- Urban — Optimized for paved streets, intersections, and urban road networks.
Note: Road extraction is a beta feature. Results may vary depending on the complexity of the road network and the quality of the data.
Common uses: Infrastructure mapping, road inventory, transportation planning.
Extract Road Markings (Beta)
Outlines every painted marking on the paved ground (lines, dashes, crossings, hatching, arrows, symbols, parking lines) in a single layer, each outline carrying its type. It does not need the road option.
The markings are found on an image of the site: your uploaded orthophoto, or else one generated from your point cloud's own colours. It works best with an orthophoto of 10 cm or finer. A cloud whose colours were added from 30 cm satellite imagery is not sharp enough, and the layer then says so. Ticking the option also turns on the DTM, which the outlines are draped on.
Common uses: Road inventory, marking renewal plans, base plans for traffic studies.
Extract Water Body
Detects enclosed water surfaces — lakes, ponds, reservoirs — and delivers them as filled polygons.
Note: Water extraction is a beta feature. Uploading a high-resolution orthophoto (5 cm to 20 cm) is strongly recommended for best results. If your project has no orthophoto, Lidarvisor downloads open-source satellite imagery of your project area to guide the detection — a notice in the panel tells you when this will happen.
Common uses: Hydrographic mapping, flood risk studies, water resource management.
Extract Shoreline
Detects the edge between land and water — river banks, canal edges, coastline — and delivers it as lines. The lines are left open where the water leaves the surveyed area, so a river crossing your site does not get a fake bank drawn across the survey boundary.
Note: Shoreline extraction is a beta feature. The same imagery guidance as the water body option applies.
Common uses: Riverbank surveys, coastline monitoring, hydraulic studies.
Drainage Axes, Depressions and Sub-Basins
Three hydrology layers, each ticked on its own, built from the ground points:
- Drainage axes: the lines along which runoff concentrates (thalwegs, ditches, stream paths), as 3D lines draped on the terrain, each with its stream order and the area draining into it.
- Depressions: the closed hollows where water ponds before it overflows, as polygons with their depth, area, storage volume and spill level.
- Sub-basins: the catchment feeding each drainage reach, as polygons with their area.
When Drainage axes is ticked, a Network density choice appears: Finer shows smaller gullies and more, smaller sub-basins; Coarser keeps the main axes; Balanced is the default. Sub-basins follow the same density. See Vectorization for the attributes.
Common uses: Drainage design, culvert and ditch sizing, flood and ponding studies.
Water in the classified point cloud: when either water option is enabled, the points on the detected water surface are also relabeled as water in your classified point cloud. The point cloud you download therefore agrees with the water outlines in the same delivery — filtering the water class in your own tools gives you the water we drew, and stray "water" mislabels elsewhere in the scene are cleaned up.
Extract Tree Crowns
Detects individual tree canopies and creates a polygon for each tree crown — the boundary of the tree as seen from above.
Detection sensitivity is automatic: the algorithm adapts to the local canopy structure, so tall conifers, broad deciduous crowns, and low vegetation in the same survey each get appropriate treatment. There is no sensitivity setting to configure.
Crown Geometry — how crowns are drawn in the viewer and in the exported files:
- Circle (default) — each crown as a circle of equivalent area (same crown radius). Cleaner and lighter, ideal for CAD.
- Polygon — the true canopy outline traced from the point cloud.
The choice does not change any measured value (area, crown radius, carbon).
Common uses: Forest inventory, tree counting, canopy analysis, urban tree management.
Extract Tree Tops
Detects the location and height of individual trees — each tree is represented as a single point at its highest position.
Common uses: Forest inventory (tree count), tree height measurement, plantation management.
Minimum Tree Height
A single height threshold that applies to all tree detection: trees shorter than this value are not reported as individual trees. It always applies — there is no checkbox to enable.
- Range: 2 to 10 meters. The default is 4 meters (13 ft on projects measured in feet), which suits most forest and vegetation surveys.
- Lower it for young plantations, regeneration surveys, or orchards.
- Raise it to count only mature stems.
Note: Lowering the value increases the number of trees found, which makes processing and the reports take longer. Inventory totals are not comparable between two runs that used different values.
Extract Power Lines
Not working with power lines? Skip this section and the next one (Extract Towers). These options are designed for utility vegetation management and power line inspection professionals. If your survey area does not contain overhead power lines, these options will not produce useful results.
Not available for photogrammetric point clouds. Photogrammetry cannot reconstruct the thin conductor wires, so these options (and the vegetation encroachment report) are disabled when your point cloud is photogrammetric — the results would come back empty.
Detects power line cables and creates 3D line geometries that follow the shape of the wires, including the natural sag (droop) between poles.
When you enable this option, additional sub-options appear:
Buffer Zone 1, 2, 3 (0.5 to 100 m): Up to three distances from the conductors. A buffer zone holds the vegetation within that distance of a conductor, measured in 3D from the wire, so the zones are nested: zone 3 contains zones 2 and 1. Each finding is a connected mass of vegetation, reported once per conductor it is close to and counted once, in the innermost zone that holds it. A span where nothing was found reads "none within" the largest distance examined. You can set different distances for different risk levels (e.g., Zone 1 = critical, Zone 2 = warning, Zone 3 = monitoring).
Clearance Zone (0.5 to 100 m): Defines the minimum safe distance between vegetation and power lines. Trees or vegetation closer than this distance are flagged as encroaching.
Right-of-Way Zone (on by default, half-width 1 to 50 m, 15 m by default): flags the vegetation inside a flat corridor of that half-width on each side of the line axis, whatever its height. It serves legal clearing obligations (right-of-way, franja de seguridad) and is delivered as its own findings layer. It differs from the buffer zones (a 3D distance to the conductor) and the clearance zone (a prism below the conductor): a point can be caught by one and not the others.
Tree Fall Risk (0.5 to 10 m): Identifies trees that are tall enough to hit a power line if they were to fall. Every tree within 50 m of a conductor is checked: it is flagged when its height plus this safety margin reaches the nearest conductor from the tree's base. The fall-risk table also gives each tree's canopy-to-conductor distance and the zone it falls in.
Common uses: Utility vegetation management, power line inspection, regulatory compliance.
Extract Towers
Finds every support of the corridor in the classified point cloud (the Transmission Tower class): lattice towers, poles and double poles. For each one you get its type, its height and where that height came from, its lean from vertical with a quality flag, how it was found (detected, inferred from the conductors, or added by hand), the spans attached to it and the nearest vegetation findings. A support that could not be measured is left empty with the reason, never given a default value passed off as a measurement.
With both power lines and towers extracted, the viewer's Towers panel lists every support and every span. See Tower and Span Inventory.
Common uses: Infrastructure inventory, power line inspection, lean monitoring, telecom asset mapping.
Report Options
These options generate professional documents and multi-layer exports.
Generate Topographic Map
Creates a finished topographic map sheet, delivered as a layered DXF drawing for CAD and a printable PDF sheet at true scale, that combines multiple elements:
- Contour lines (major and minor)
- Elevation grid points
- Building footprints
- Tree positions and crowns
- Power lines and towers
- Roads
The DXF file has separate layers for each element, making it easy to toggle them on and off in CAD software. Title block, paper size, scale and orientation are set in Report settings: see Topographic Maps.
Common uses: Delivering survey results to clients, civil engineering planning, permit applications.
Generate Digital Forest Inventory
Creates a comprehensive tree-by-tree report with:
- A PDF document containing maps, charts, and statistics
- A CSV spreadsheet with per-tree measurements (height, crown area, position)
Additional sub-options:
- Carbon Estimation — if enabled, the report includes carbon stock calculations for each tree (above-ground biomass, below-ground biomass, carbon, CO2 equivalent). This is based on peer-reviewed allometric equations.
- Allometric Region — select the region closest to your survey area for the most accurate biomass estimates:
- Europe, Canada, USA, Tropical, Australia, Boreal/Russia, East Asia, African Dryland
- Dominant Tree Species — select the most common tree species in your area. The list changes based on the selected region and includes dozens of species (e.g., Scots Pine, Norway Spruce, Douglas Fir, European Beech, etc.).
Common uses: Forest management, timber inventory, carbon credit projects, environmental assessments.
Generate Vegetation Encroachment Report
Creates a report specifically for utility vegetation management — identifying trees and vegetation that pose a risk to power line infrastructure.
The report includes:
- Buffer zone analysis (vegetation within defined distances of power lines)
- Clearance violations (vegetation too close to wires)
- Fall-risk trees (trees tall enough to reach power lines if they fell)
- Maps and GPS coordinates for each risk area
This report requires the extracted power lines, so it is not available for photogrammetric point clouds.
Common uses: Utility vegetation management programs, NERC FAC-003 compliance, post-storm damage assessment.
During Processing
After you click Start Processing and confirm:
- The status changes to PENDING while the job is queued.
- It then moves to PROCESSING with a progress indicator showing the percentage and current step.
- When complete, the panel shows Processing completed with the elapsed time.
How long it will take. Before you start, under the surface area, the panel usually shows an estimate such as "Estimated processing: about 25 min · usually under 40 min". It is a range drawn from comparable runs, not a promise. During the run, the line becomes the remaining time, and if the run goes past the usual bound it says Taking longer than usual. When there is not enough data to estimate a run, no line is shown.
On a large cloud processed in tiles, the percentage is the average progress of all the tiles, so it moves steadily and never goes backwards.
Right after completion, some layers may still be prepared for display for a few minutes; the panel says how many are in progress, and they become available as soon as they are ready.
You can close your browser during processing. The work continues on Lidarvisor's servers. When you come back and load the project, the results will be there. You will also receive an email notification when processing finishes, unless you turned it off in Account → Settings → Emails.
If Processing Fails
If processing encounters an error, the panel names the step that failed and says that our support team has been notified automatically and will get back to you within 24 hours. If this happens:
- Your credits are automatically refunded within seconds
- You cannot restart a failed run yourself: running it again unchanged would repeat the same failure. Our team reviews every failed run and relaunches it once the cause is fixed
- A relaunched run resumes from the step that failed rather than from zero: the steps that already completed (classification, terrain models, ...) are reused, so a job that failed near the end finishes in minutes instead of hours. On a large cloud processed in tiles, only the tiles that did not finish are run again
- You are never charged twice for the same processing: between the automatic refund and the relaunch, you only ever pay once for a completed result
- If you have not heard back, write to contact@lidarvisor.com
Processing Credits
Processing consumes credits based on the area of your dataset measured in hectares: 1 credit per hectare processed (about 2.5 acres), with a minimum of 5 credits per run. The number of credits is the same regardless of how many options you enable. Precision mode (paid plans) is the one exception: it adds a price per hectare for the layers you switch it on for, shown before you confirm.
If your project has an area of interest boundary (see Creating a Project), credits are counted on the area inside your AOI, not on the whole file (at least 5 credits per run).
Projects with drone photos or raw DJI data count their area differently (the area the photos cover, or the area the LiDAR recorded), see Drone Photos and Photogrammetry and Raw DJI Zenmuse Data. It is still one charge per run.
Before processing starts, a dialog shows you how many credits will be used and how many you have available.
See Account and Subscription for details on how credits work and how to get more.
Providing Feedback
After processing completes successfully, a small feedback prompt appears. Lidarvisor's team uses this feedback to improve the AI classification and processing quality. Your input is valuable — share what worked well and what could be better.
Next Step
Processing is complete and your results are in the project tree. Let's understand what each result is. Head to Understanding Your Results.