Skip to content

Vectorization: Contour Lines, Buildings, Trees, Power Lines, and More ​

Lidarvisor automatically extracts real-world features from your point cloud (building outlines, contour lines, terrain breaklines, individual trees, wooded areas, road and railway lines, road markings, bridges, water bodies, drainage networks, power line cables and their supports) and delivers them as clean, ready-to-use vector files for CAD and GIS. It can even fetch property boundaries from national open-data cadastres to give your survey legal context.

All vector outputs from Lidarvisor are available in three formats:

  • GeoJSON — a web-friendly format viewable in any browser or GIS application
  • Shapefile (.shp) — the most widely used GIS vector format, compatible with QGIS, ArcGIS, etc.
  • DXF — a CAD format compatible with AutoCAD, Civil 3D, and other engineering software

This page explains each vector output in detail.


Contour Lines ​

What Are Contour Lines? ​

Contour lines are curves drawn on a map that connect points of equal elevation. If you have ever seen a topographic map with wavy lines going up a hillside, those are contour lines.

Where contour lines are close together, the terrain is steep. Where they are far apart, the terrain is flat. Contour lines never cross each other.

What Lidarvisor Generates ​

Lidarvisor generates two sets of contour lines:

  • Major contour lines — spaced at a wider interval (e.g., every 5 meters), typically drawn with thicker lines and labeled with the elevation value. These give you the overall shape of the terrain.
  • Minor contour lines — spaced at a narrower interval (e.g., every 1 meter), providing detail between the major lines.

You set the intervals when configuring processing. For example, Major = 500 cm (5 m) and Minor = 100 cm (1 m) means you will get a bold contour line every 5 meters with four thinner lines between each pair.

Choosing Intervals ​

Terrain TypeSuggested MajorSuggested Minor
Flat terrain (less than 10 m elevation change)1 m0.25 m
Gently rolling hills5 m1 m
Hilly terrain10 m2 m
Mountainous terrain25 m5 m

In the Viewer ​

Major and minor contour lines appear as separate layers in the project tree. You can toggle each independently to reduce visual clutter — for example, show only major contours for an overview, then add minor contours when you need detail.

Common Uses ​

  • Topographic maps and survey deliverables
  • Engineering site plans
  • Flood zone delineation
  • Landscape architecture

Elevation Grid ​

What It Is ​

An elevation grid is a regular pattern of points placed across your terrain model, each labeled with its elevation. Think of it as a net of evenly spaced dots, where each dot has a height value.

What You Configure ​

  • Grid spacing (50 to 10,000 cm): The distance between points. A 500 cm (5 m) spacing means one elevation point every 5 meters in both directions.

Common Uses ​

  • CAD spot elevation maps
  • Volume calculations in engineering software
  • Quick reference for terrain heights at regular positions

Breaklines ​

What They Are ​

Breaklines are 3D lines that follow abrupt changes in terrain slope — the top and bottom edges of embankments, ditch sides, terraces, banks, road shoulders, and field edges. On a traditional survey plan these are the lines a surveyor traces by hand over the hillshade, which is one of the most time-consuming steps of terrain drafting. Lidarvisor detects them automatically from your terrain model.

Each breakline carries elevation values along its length, so it can be used directly in terrain modeling software.

The Three Density Tiers ​

Terrain varies enormously in how many breaklines it contains — a flat field has a handful, a terraced vineyard has hundreds. Instead of a single all-or-nothing output, Lidarvisor delivers breaklines as three complementary layers:

LayerWhat It AddsBest For
Main BreaklinesThe most prominent, longest breaklinesFirst overview, clean cartography
Detailed BreaklinesSecondary features: short benches, internal terraces, field edgesMost survey and analysis work
Exhaustive BreaklinesAll remaining detectable breaklines, including faint onesQuality control; may include extra noise on flat terrain

The three layers do not overlap — each denser tier only adds lines the previous tier does not already contain. The toggles are linked so you always see a coherent picture: turning on Detailed automatically turns on Main, and turning on Exhaustive turns on both. By default, Main and Detailed are enabled and Exhaustive is off.

In the Viewer ​

Breaklines render as cyan lines, with Main drawn thickest and Exhaustive thinnest so the structural lines always stand out.

Common Uses ​

  • CAD linework for survey deliverables (embankments, ditches, terraces)
  • Enforcing slope discontinuities when building a TIN or terrain model
  • Hydrology and drainage analysis
  • Volume and earthworks calculations

Cadastral Parcels ​

What They Are ​

Cadastral parcels are property boundary polygons fetched from your country's official open-data cadastre. This layer is different from every other vector output: it is not derived from your point cloud. It is reference data — the boundaries as published by the national land registry — overlaid on your survey so you can read your results against property lines.

What Each Parcel Contains ​

  • Parcel reference — the official identifier of the parcel
  • Area — the parcel area
  • Source — which national service the data came from

No ownership information (names, addresses, titles) is ever fetched or delivered — only geometry, reference, and area.

Important: Indicative Boundaries Only ​

Cadastral boundaries are legal and fiscal records, not survey measurements. They routinely differ from the physical features your LiDAR survey measures by several meters, and this offset is a property of the source data, not an error in your survey. Use this layer for context — never as a boundary survey.

Coverage ​

Availability depends on your country and region: parcels are fetched automatically where a free, openly licensed cadastre service exists for your project area. If your area is not covered, processing completes normally and the layer is simply delivered empty.

The option is ticked in the default Topographic survey preset and in Site & infrastructure; otherwise you opt in with a single checkbox. Lidarvisor determines the correct data source from your project's location automatically.

In the Viewer ​

Parcels render as thin brown outlines with no fill, so they read as context and never obscure your surveyed features. This layer cannot be edited — it is a third-party record.

Common Uses ​

  • Reading survey results against property boundaries
  • Site plans and permitting documents
  • Checking which parcels a project, corridor, or finding touches

Building Footprints ​

What They Are ​

Building footprints are polygons (outlines) of detected buildings as seen from above. Each polygon represents the boundary of one building's roof.

How They Are Created ​

  1. The AI identifies which points are classified as Building.
  2. Points are grouped into clusters — each cluster is one building.
  3. The outline of each cluster is extracted and simplified into a clean polygon.

Simplification Modes ​

You choose a simplification mode during processing:

  • Rural — Produces simple, clean outlines with straight edges and right angles. Ideal for isolated houses, barns, and rural structures where buildings have simple shapes.
  • Urban — Produces more detailed outlines that follow L-shaped, T-shaped, and other complex building footprints. Ideal for city centers with attached buildings and complex roof shapes.
  • Natural — Follows the detected shape closely with minimal geometric correction. The outlines may look more organic and less "square."

What Each Building Polygon Contains ​

Each building footprint comes with attributes:

  • Height — the estimated height of the building above the ground
  • Area — the footprint area in square meters
  • Elevation — the ground elevation at the building location
  • Roof heights — ground_z (the ground around the building), eave_z (the low edge of the roof) and ridge_z (its highest point, a church spire for example) as elevations, h_eave and h_ridge as heights above that ground, and pitch_deg, the roof pitch in degrees. Eave and ridge are robust statistics of the roof (its 5th and 99th percentiles), so a stray point does not move them.

Common Uses ​

  • Cadastral mapping and property boundaries
  • Urban planning and zoning
  • 3D city models (using height to extrude footprints)
  • Insurance and risk assessment

Bridges ​

What They Are ​

Bridge vectors are polygons outlining the deck of each detected bridge — the road- or rail-carrying surface — drawn at the deck's elevation so they sit at the correct height in the 3D viewer.

How They Are Created ​

  1. The AI identifies points classified as Bridge Deck and groups them into one cluster per bridge.
  2. The bridge's parapet walls are located and measured to find the bridge's precise axis and width — the polygon stops at the inner face of the parapets, so it represents the usable deck.
  3. The deck length is extended over sections the classification missed (bridges are recognized in part by the void beneath them), producing a clean, oriented rectangle per bridge.

What Each Bridge Polygon Contains ​

  • Length — the deck length along the bridge axis
  • Width — the deck width between the parapets
  • Deck elevation — the elevation of the deck surface

Classification Cleanup ​

When bridges are extracted, the result is also written back into the classified point cloud: points on the deck are relabeled as Bridge Deck, and parapet points as Fence / Wall — even where the AI originally missed them. See Understanding Your Results for how vector extraction refines the classification.

In the Viewer ​

Bridges render as light-brown filled polygons, visually distinct from buildings (red) and roads. Extraction is enabled by default.

Common Uses ​

  • Infrastructure inventory and asset management
  • Verifying that all expected bridges were surveyed
  • Importing bridge footprints into GIS alongside roads and buildings

Roads ​

What They Are ​

Road vectors are lines that follow the edges of detected road surfaces.

How They Are Created ​

Lidarvisor uses an AI-powered image recognition approach to detect roads. It analyzes an overhead image of your project — the orthophoto you uploaded, or one generated automatically from the point cloud — identifies the road surfaces, and traces their edges as vector lines.

For best results, upload a high-resolution orthophoto (5 cm to 20 cm per pixel) with your project.

Modes ​

  • Rural: Optimized for paved country roads and simpler layouts. Dirt tracks and field paths are not roads: see Tracks.
  • Urban — Optimized for paved streets, intersections, and complex road networks.

Note: Road extraction is currently a beta feature. Results may vary depending on road visibility in the data (roads under heavy tree canopy may not be fully detected).

Classification Cleanup ​

Ground points inside the detected road surfaces are relabeled as Road Surface in the classified point cloud, so the point cloud you download agrees with the road vectors.

Common Uses ​

  • Road inventory and mapping
  • Transportation planning
  • Access route planning for forestry and utility maintenance

Road Markings ​

What They Are ​

Road marking vectors are outlines of every painted marking on the paved ground (lines, dashes, crossings, hatching, arrows, symbols and text, parking lines), all in one layer. Each outline is draped on the terrain model.

How They Are Created ​

The markings are detected on an overhead image of the site, and only paint lying on paved ground is kept. The image is your uploaded orthophoto or, when you have none, an orthophoto generated from your point cloud's own colours. If your cloud's colours were added from 30 cm satellite imagery, they are not sharp enough and the layer explains why it is empty. With an image coarser than 10 cm per pixel, small markings may be missed, and the layer says so.

Note: Road marking extraction is a beta feature, off by default.

What Each Marking Contains ​

  • Type (type): line, dash, transverse, crossing, hatching, arrow, symbol, parking, or other (paint the typing could not place, and every outline drawn by hand), with its confidence (type_conf)
  • Colour (colour): white, yellow, or other
  • Size: area (area_m2), length (length_m), width (width_m), and for dashed lines the dash and gap lengths (dash_m, gap_m)
  • Identifiers: mark_id, and group_id, shared by the shapes that form one set (the dashes of one line, the bars of one crossing, the lines of a row of parking spaces)
  • Quality: detection confidence (conf) and the resolution of the image it was read on (ortho_cm)

On projects in feet, the GeoJSON fields carry feet (area_ft2, length_ft, ...). In the DXF, markings are on the PAVEMENT_MARKINGS layer.

In the Viewer ​

Each outline is filled by its type; the info icon on the layer row shows the legend.

Common Uses ​

  • Road marking inventory and renewal plans
  • Base plans for traffic and parking studies
  • Checking markings against design drawings

Rails ​

What They Are ​

Rail vectors are 3D lines that follow each individual rail of a railway track — the left and right rail of every track, traced as parallel lines at the standard track gauge.

How They Are Created ​

Lidarvisor locates railway lines using openly available railway map data (OpenStreetMap), then places each rail using both the overhead image of your project and the rail heads found in the point cloud. Each line's elevation is the top of the rail, measured in the point cloud.

A rail is only drawn where the survey shows it:

  • A line stops where the cloud has no points for more than 10 m.
  • Overgrown or removed track, where vegetation or objects fill the space between the rails, is not drawn. A short occupied stretch (30 m or less) between clear track, such as a parked train, is kept.
  • Duplicate lines and short leftover pieces are removed.

The extraction needs an orthophoto: your uploaded one, or the one generated with the roads option (on by default), the road markings option or Generate Orthophoto. Uploading a high-resolution orthophoto (5 cm to 20 cm per pixel) is strongly recommended.

Note: Rail extraction is currently a beta feature, designed to accelerate linework productivity rather than replace a survey.

What Each Rail Line Contains ​

  • Side (kind): whether the line is the left or right rail of its track
  • Track, segment and pair identifiers (track_id, segment_id, pair_id): so the two rails of one track can be paired
  • OpenStreetMap way (osm_way_id): the railway line it was found on
  • Length (length_m): the rail segment length
  • Gauge (gauge_m): the rail spacing used
  • Evidence (mean_evid): how strongly the rail was seen along the line

Classification Cleanup ​

The track corridor along the rails that were drawn is relabeled as Rail in the classified point cloud, so a stretch of track that was not drawn is not given the rail class either. Where a railway crosses a road or a bridge, the rail classification wins on the track bed itself, while vegetation and wires above the track keep their own classes.

Common Uses ​

  • Railway corridor inventory
  • Track alignment linework for CAD
  • Vegetation management along rail corridors

Tracks ​

What They Are ​

Track vectors are centre lines of unpaved tracks and paths (farm and forest tracks, field paths, bridleways), draped on the terrain. They have no width and no edges, and they stop where an extracted road begins.

Where They Come From ​

Tracks are taken from map data over your survey area, clipped to the area your point cloud covers, with their heights read from your terrain model. A track that is not in the map data is not drawn, even when you can see it in your point cloud or orthophoto.

When the Layer Is Empty ​

The project tree says why, under the Tracks layer, and the processing report repeats it as a note on the Tracks row:

  • "No track is mapped in this survey area": the map data holds no track inside your survey. Nothing failed.
  • "The map data could not be read for this survey": the map data was not available during the run, so no track was drawn.

Drawing Every Visible Track ​

On paid plans, Precision mode draws the tracks visible on a drone orthophoto of 5 cm or finer, whether or not they are in the map data. Add the orthophoto to your project (uploaded, or computed from your drone photos), tick Extract Tracks, then switch on Precision mode below it. It adds a price per hectare, shown before you confirm.

Common Uses ​

  • Access routes for forestry and utility maintenance
  • Planimetry of a topographic survey, over the terrain model

Ditches, Walls and Fences, Vertical Structures, Manholes (Beta) ​

Four survey layers complete the topographic plan. Each is an option of its own in the processing panel, marked Beta:

LayerWhat you getNeeds
DitchesDitches and small watercourses as lines: the axis along the bottom, with its depth and width, and the two edges.Read from the terrain model; a ditch shallower than the tooltip's figure is not found.
Walls and FencesWalls, retaining walls and fences as lines, each with its type and height. Where the cloud is too sparse to tell a wall from a fence, the line is marked "wall or fence".The point cloud.
Vertical StructuresStreet lights and poles that carry no wire, as points, each with its type and height. Power-line poles stay in the Towers layer.The point cloud; no orthophoto needed.
ManholesManhole covers as outlines (circle, square or rectangle) at their ground height.A drone orthophoto of 5 cm or finer, uploaded or computed from your drone photos.

They download in the same formats as the other vectors (GeoJSON, Shapefile, DXF).


Precision Mode ​

On paid plans, some layers offer a Precision mode switch under their option. It draws the layer with our most accurate method, for survey-grade linework. It needs a drone orthophoto of 5 cm or finer, uploaded or computed from your drone photos: without one, the switch says so and cannot be turned on.

LayerWhat Precision mode does
RoadsRoad edges drawn exactly on the asphalt edge.
BreaklinesSlope breaks drawn where the terrain really breaks, even under trees.
Walls and FencesWalls and fences the standard misses.
TracksTracks drawn, including those the standard misses.
DitchesDitches traced along their whole length.

It is computing-intensive: it adds processing time and a price per hectare, shown next to the switch ("+4 credits/ha · +N credits for this survey") and included in the total you confirm before processing. If Precision mode cannot be completed for a layer on a run, the standard layer is delivered and the credits for it are not charged; the project tree says so. On the Free plan, the switch opens the upgrade dialog.


Water Bodies and Shorelines ​

Lidarvisor offers two independent water layers, selectable separately.

Water Body ​

Filled polygons of enclosed water surfaces — lakes, ponds, and reservoirs that lie entirely inside your surveyed area.

Shoreline ​

Open 3D lines along the land/water edge — river banks, canal edges, and coastline. Shorelines are deliberately left open where the water leaves the surveyed area: a river crossing your project has real banks but no closed outline, so forcing a polygon would draw a false bank across the survey edge. This is why a river produces shorelines rather than a water body polygon.

Every water vertex is placed at the detected water surface elevation, so the lines and polygons sit on the water in the 3D viewer.

How They Are Created ​

Water is detected on the overhead image of your project and then confirmed and grown against evidence in the point cloud itself. If your project has no orthophoto, you can allow Lidarvisor to use open-source satellite imagery of your area to seed the detection — uploading your own orthophoto gives the best results.

Note: Water extraction is currently a beta feature. Both layers are off by default.

Classification Cleanup ​

When water extraction runs, the classified point cloud is updated to match: points on the detected water surface are relabeled as Water, and stray "water" labels elsewhere in the project (the AI sometimes mistakes wet roads or dark roofs for water) are cleaned up. See Understanding Your Results for details.

Common Uses ​

  • Flood mapping and hydraulic studies
  • Hydrography layers for topographic plans
  • Shoreline and bank monitoring
  • Separating water returns from ground when deriving terrain

Hydrology: Drainage Axes, Depressions and Sub-Basins ​

Three vector layers describe how water runs off your site. Each is ticked on its own, under Hydrography Vectors, and is built from the ground points (the DTM option is not needed). The raster companion, Flow accumulation, is described in Terrain Models. None of them is ticked by default.

There is no threshold to type in: every threshold is derived from your data and stated in the project report. The one setting is Network density (Finer, Balanced, or Coarser), shown when Drainage axes is ticked; it also sets how finely the sub-basins are cut.

Drainage Axes ​

3D lines along which runoff concentrates: thalwegs, ditches and stream paths, traced on the conditioned terrain and draped on it. In the viewer, larger axes are drawn thicker. Each line carries:

  • Order (order): 1 for a fingertip rill fed by no other line, 2 where two rills have met, and so on up to the main axes of the site
  • Drained area (upstr_ha): the area draining into the line, in hectares
  • Length (length_m) and mean slope (slope_pct)

Depressions ​

Closed hollows where water ponds before it overflows: wet spots, retention storage, blocked drainage. Each polygon is drawn at its spill level, the rim height at which it starts to overflow, and carries its maximum and mean depth (max_dep_m, mean_dep_m), area (area_m2), storage volume (volume_m3) and spill level (spill_z). Hollows shallower than the measured ground noise are left out.

The treatment field tells the two kinds apart, and so do the colours in the viewer: breached (blue), where an outlet path was found nearby and the hollow most likely drains in reality (a culvert, a gap in a bank), and filled (ochre), where no outlet is within reach and water stays until it soaks in or evaporates.

Sub-Basins ​

The catchment feeding each drainage reach: every drop falling inside one polygon flows to that basin's outlet. Each polygon carries its area (area_ha) and the position and order of its outlet (out_x, out_y, out_order). In the viewer, colours only tell neighbouring basins apart.

At the Edge of the Survey ​

Water flowing in from outside the survey is not seen. Features that touch the survey boundary are marked with the edge field, and their figures are minimums.

On projects in feet, the GeoJSON fields carry feet and acres (upstr_ac, area_ac, max_dep_ft, ...). In the DXF, the layers are DRAINAGE_AXES, DEPRESSIONS and SUB_BASINS, and all three are drawn on the topographic map when it is generated. A site too flat to derive any drainage gives empty layers with the reason.

Common Uses ​

  • Drainage design: where to place or check culverts, ditches and outlets
  • Sizing what each outlet must carry, from its sub-basin
  • Ponding and retention studies
  • Erosion and runoff assessment

Tree Tops ​

What They Are ​

Tree top points represent the location and height of individual trees. Each detected tree is marked with a single point at its highest position.

What Each Point Contains ​

  • Tree ID — a unique number identifying the tree
  • Height — the tree's height above the ground in meters
  • Position — X, Y coordinates (geographic position) and Z (elevation)
  • Vegetation area ID — the identifier of the vegetation area the tree stands in (see Vegetation Areas), or 0 if it stands alone

How Trees Are Detected ​

Lidarvisor's algorithm analyzes the Canopy Height Model (CHM) and uses a watershed-based method to identify individual trees. It finds the peak (highest point) of each tree and records its position and height.

You can set the minimum tree height (default 4 m, adjustable from 2 to 10 m): anything shorter is not reported as an individual tree. Lower it for young plantations and orchards; raise it to count only mature stems.

Common Uses ​

  • Counting trees across a large area
  • Measuring tree heights for timber inventory
  • Identifying the tallest trees (for clearance or risk assessment)
  • Plantation row analysis
  • Urban tree inventory

Tree Crowns ​

What They Are ​

Tree crown polygons represent the canopy boundary of individual trees — the outline of each tree as seen from above. Each polygon encircles one tree's leaf canopy.

What Each Polygon Contains ​

  • Tree ID — a unique number matching the corresponding tree top
  • Height — the tree's height above the ground
  • Crown area — the area of the canopy in square meters
  • Crown radius (crown_r_m) — the radius of the circle with the same area as the crown; also a column of the forest inventory CSV
  • Position — centroid coordinates
  • Vegetation area ID — the identifier of the vegetation area the tree stands in, or 0 if it stands alone

Crown Geometry Setting ​

You choose 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 deliverables.
  • Polygon — the true canopy outline traced from the point cloud.

The choice does not change any measured value (area, crown radius, carbon). Detection sensitivity itself is automatic: Lidarvisor adapts it to the local canopy structure, so there is no sensitivity setting to tune.

In the Viewer ​

Tree crowns appear as colored polygons overlaid on the point cloud. Combined with tree tops, you can see both the location and the extent of each tree.

Common Uses ​

  • Forest inventory — measuring canopy cover and density
  • Individual tree analysis — crown competition, growth space
  • Urban tree management — identifying trees that need pruning or removal
  • Carbon estimation input (crown area correlates with biomass)
  • Habitat assessment — canopy structure determines habitat suitability

Vegetation Areas ​

What They Are ​

Vegetation areas are generalized outlines of wooded areas — one polygon per wood or copse, traced at the outer crown edge, with large clearings kept as holes inside the polygon. This is how vegetation is drawn on a topographic plan: as a mass, not as thousands of individual circles. On a densely wooded site, this layer is what makes the plan readable.

Vegetation areas are independent of the per-tree layers: you can request them with or without Tree Tops and Tree Crowns. An isolated tree is not an area — it is delivered as a point in Tree Tops.

How They Are Created ​

The outlines are derived directly from the Canopy Height Model rather than from individual tree detection, which makes them robust: a missed tree top cannot punch a hole in the wooded outline. The layer uses the same minimum tree height as tree detection, so one definition of "vegetation" applies across your whole project.

What Each Area Contains ​

  • Nature — closed_wood, open_wood, or copse: areas of 5,000 m² or more are woods (closed if canopy cover is at least 40%, open otherwise); smaller areas are copses
  • Area, perimeter, width, length — the polygon's dimensions
  • Canopy cover — the percentage of the area actually covered by canopy
  • Height statistics — mean, maximum, and 95th-percentile canopy height, plus the height floor used
  • Tree count and density — the number of detected tree tops inside the area and stems per hectare (when tree detection also ran)

In the Viewer ​

Vegetation areas render as a light, translucent green, deliberately lighter than the tree-crown green, so the mass reads as background and the crowns as detail when both are displayed together. The option is ticked in the default Topographic survey preset.

Common Uses ​

  • Topographic plans with standard vegetation symbology
  • Delineating woods, copses, and stands for forestry
  • Lightweight CAD deliverables for wooded sites
  • Stand-level statistics (cover, height, density)

Power Lines ​

What They Are ​

Power line vectors are 3D lines that follow the cables of overhead power lines, including the natural curve (catenary sag) of each cable. There is one line per conductor per span: a span is the stretch of line between two supports.

What Each Line Contains ​

Every conductor says which span it belongs to and what was measured on it, as surveyed on the day of the flight (not at maximum operating temperature):

  • Span (span_id) and the two supports it hangs between (twr_a, twr_b, the tower_id of each support in the Towers layer)
  • Span length (span_len): the horizontal distance between the two support bases
  • Sag (sag_m): this conductor's largest drop below the straight line between its ends, and the worst sag of the span (sag_max)
  • Lowest point (low_z): the lowest elevation of the conductor
  • Ground clearance (clr_gnd): the smallest vertical distance to the ground under the span, with the share of the span that had ground under it (clr_cov). It is left empty when less than half of the span had ground under it, and it can be negative where the ground rises above the conductor
  • Vegetation clearance (clr_veg) and the number of clearance zone findings on the span (veg_n), when the vegetation analysis ran
  • Span quality (sp_q): ok; partial, where a conductor is broken inside the span; or open, where one end has no tower (for example at the edge of the survey)
  • Kind (kind): line for a conductor of the line, drop for a service drop from a pole to a building. Drops carry no span figures

A value that was not measured is left empty, never written as 0. In the DXF, conductors are on the POWER_WIRES layer and service drops on POWER_DROPS.

The Towers panel lists every span with these figures, and can colour the lines by ground or vegetation clearance.

What You Also Get ​

When you enable power line extraction, you can also enable several analysis layers:

Buffer Zones (up to 3) ​

A buffer zone is a band of a specific width centered on the power lines. Any vegetation found within this band is flagged. You can define up to three zones with different widths to represent different risk levels:

  • Zone 1 (e.g., 5 m) — immediate proximity, highest risk
  • Zone 2 (e.g., 10 m) — moderate proximity, medium risk
  • Zone 3 (e.g., 20 m) — broader monitoring zone

Clearance Zone ​

The clearance zone identifies vegetation that is too close to the power lines. You define a minimum safe distance, and any tree or vegetation closer than that distance is flagged. This is essential for regulatory compliance.

Right-of-Way Zone (ROW) ​

The right-of-way zone flags vegetation inside a flat horizontal corridor of a chosen half-width on each side of the line axis, regardless of height. This answers a different question from the buffer and clearance zones: those measure electrical proximity to the conductor in 3D, while the ROW measures presence inside the legal corridor a utility is obliged to keep clear (the right-of-way in North America, franja de seguridad in Chile).

A low bush 4 m off-axis under a 20 m-high line is far from the conductor in 3D — the buffer and clearance modes correctly ignore it — but it is inside the corridor, so the ROW mode flags it. The default half-width is 15 m (adjustable from 1 to 50 m); the tooltip in the app lists reference values per voltage class.

Tree Fall Risk ​

The tree fall risk layer identifies trees that are tall enough to hit a power line if they were to fall over. Lidarvisor checks: "Is this tree taller than its distance to the nearest wire?" If yes, it is flagged as a fall risk.

Findings in the Viewer and in Your Downloads ​

Each analysis you enable produces its own vector layer, grouped under Encroachment Findings in the project tree: Buffer Zone 1, Buffer Zone 2, Buffer Zone 3, Clearance Zone, Right-of-Way Zone, and Fallen Tree Risk. Every flagged vegetation cluster is drawn as a polygon draped on the terrain, color-coded by severity:

LayerColor
Buffer Zone 1Red (closest tier — immediate hazard)
Buffer Zone 2Orange
Buffer Zone 3Yellow
Clearance ZoneMagenta
Right-of-Way ZoneCyan (broadest area, lowest opacity)
Fallen Tree RiskDark red

Click any finding in the viewer to see its details: cluster ID, number of points, area, volume, distance to the wire, the wire ID, and for buffer, clearance and right-of-way findings, the span and the nearest tower. Clicking either of those opens the Towers panel on that row.

Each findings layer is downloadable in the standard three formats (GeoJSON, Shapefile, DXF). The finding attributes also include the closest conductor position (X, Y, Z), the 3D distance to the conductor, the wire ID (which matches the wire ID in the power line export, so the two files can be joined), and the detection type, so you can import findings straight into your own GIS or asset-management system without recomputing anything. Buffer, clearance and right-of-way findings also carry their span (span_id), the support nearest to the conductor point (twr_near) and the distance to it (twr_dist); fall-risk findings do not. The same information appears in the spreadsheet (CSV) files delivered with the vegetation encroachment report (Span_id, Nearest_tower_id, Distance_to_tower_m), where a missing value is a blank cell.

Every finding also carries the height of the vegetation above the ground (veg_h_m) and the innermost zone that holds it (zone). Fall-risk trees carry the canopy-to-conductor 3D distance (canopy_m), the crown diameter (crown_d_m), their span, their nearest tower and their zone. These values are in the downloads (GeoJSON, Shapefile, DXF and the CSV files) and on the cards of the viewer.

The zone distances can be changed after the run, without processing again: see Changing the Vegetation Zone Distances After the Run.

Common Uses ​

  • Power line corridor inspection
  • Vegetation management planning
  • Regulatory compliance (NERC FAC-003 and similar standards)
  • Legal right-of-way clearing programs
  • Post-storm damage assessment priorities
  • Utility asset inventory

Towers ​

What They Are ​

The Towers layer holds every support of the corridor: lattice towers, poles and double poles. Each support is a point at its base, carrying what was measured on it. The viewer draws each one in 3D as its family (lattice towers as their members, poles as cylinders at their measured radius, double poles as two uprights), and a separate 3D structure export delivers that geometry.

Supports come from three sources, recorded in the src field:

  • Detected (auto): found in the classified point cloud
  • Inferred (inferred): a pole the point cloud barely shows, placed from the shape of the conductors it carries, or (bridge) the pole placed at a bridge apex
  • Added by hand (manual): placed in the viewer, see Tower and Span Inventory

What Each Tower Contains ​

  • Identifiers: tower_id, the number shown as T-014 in the viewer and used by the spans, and tower_uid, a permanent identifier that survives your edits
  • Type (struct): lattice, pole, dbl_pole or unknown
  • Height (height) and where it came from (ht_src), plus where its base (base_src: measured ground, the terrain model dtm, the lowest return, or assumed) and its top (top_src) came from. A support with no ground returns beneath it takes its base from the terrain model, so its height is the structure's, not just the part the scanner saw
  • Lean: the angle from vertical (lean_deg), the direction the top leans towards (lean_az, degrees clockwise from grid north), the components along and across the line (lean_inl, lean_trv), the horizontal offset of the top (lean_top), and a quality flag (lean_q: ok, low, or none) with the reason (lean_why) when the lean could not be measured
  • Spans: the number of conductors at the support (n_wires), its spans (span_ids), and the number of clearance zone findings nearest to it (veg_n)
  • Shape: orientation and measured dimensions (orient, body_w, body_l, radius, and for lattice towers their taper, panels and arms), with geom_src saying whether the shape was measured or is a default
  • Edited (edited): true when the support was placed or corrected by hand

A support that could not be measured is left empty with the reason, never given a default passed off as a measurement. In the DXF, poles are on the POWER_POLES layer and the other supports on POWER_TOWERS.

3D Tower Structures ​

The Towers download dialog has a second section, 3D tower structures (generated), with three formats: 3D structures DXF, 3D structures Shapefile (PolylineZ) (a ZIP) and 3D structures GeoJSON. Each support is rebuilt as real 3D line geometry from its measured parameters: lattice towers as their individual members, poles as cylinders, double poles as two uprights and a head. A support without a measured size is exported as a simple box on a separate layer (TOWER_STRUCTURES_DEFAULT, the measured ones being on TOWER_STRUCTURES), so measured and default geometry are never mixed silently. The export is generated at download time from the current Towers layer, so your edits are always included.

The Inventory ​

With power lines and towers extracted, the Towers panel in the viewer lists every support and every span, lets you set the lean bands that colour the towers, and lets you add, move or retype a support by hand. See Tower and Span Inventory.

Common Uses ​

  • Utility infrastructure inventory
  • Asset management databases
  • Lean monitoring and tower inspection planning
  • Telecom site analysis

Viewing Vectors in the 3D Viewer ​

All vector layers appear in the project tree in the left panel after processing. To view them:

  1. Check the checkbox next to the layer name to make it visible.
  2. The vectors will appear overlaid on the point cloud in the 3D viewer.
  3. You can show multiple vector layers at the same time.

A layer that ran but legitimately found nothing (for example, water extraction on a dry site, or cadastral parcels outside coverage) appears in the tree marked as empty — this is normal, not an error.

Combining Layers ​

Some powerful combinations:

CombinationWhy It Is Useful
Contour lines + DTM hillshadeClassic topographic map visualization
Contour lines + breaklinesComplete terrain linework for a survey plan
Building footprints + classified point cloudVerify building detection accuracy
Cadastral parcels + building footprintsSee structures relative to property boundaries
Tree crowns + tree topsSee both tree locations and canopy boundaries
Vegetation areas + tree crownsSchematic vegetation mass with per-tree detail on top
Power lines + encroachment findingsFull utility vegetation management view, severity color-coded
Water body + shoreline + DTM hillshadeHydrography overview of the site
Contour lines + buildings + roadsComprehensive site overview
Bridges + roads + railsComplete transportation infrastructure view

Downloading Vectors ​

All vector layers can be downloaded individually from the project tree. Click the download button next to any vector layer, then choose your format:

  • GeoJSON — in WGS84 coordinates (latitude/longitude), compatible with web maps and most GIS tools
  • DXF — in the original projected coordinate system, compatible with CAD software
  • Shapefile — in the original projected coordinate system, compatible with GIS tools

See Downloading and Exporting for more details.

Next Step ​

Let's look at the report outputs. Head to Reports.

Lidarvisor — Process LiDAR in Minutes, Not Hours