Classifying utility corridors in LiDAR: conductors, poles, and towers

A transmission corridor is one of the hardest scenes a LiDAR classification team meets. The features that matter most — the conductors strung between structures — are thin, sparse, and suspended in mid-air, and the value of the whole survey often turns on getting them exactly right. This guide is for utility and transmission survey teams and the mapping contractors who classify their data: what a corridor scan is flown for, which classes carry the work, why wires are genuinely difficult, and what a reviewer checks before a block is delivered.

The vocabulary is the same ASPRS LAS classification set used everywhere else in LiDAR work, but a corridor leans on a small group of codes that most other jobs barely touch. Getting those codes right — and keeping them consistent span after span — is what separates a corridor deliverable that supports clearance analysis from one that only looks correct from a distance.

Why utility corridors get flown

Utility corridors are surveyed for a handful of overlapping reasons, and the reason drives everything from the sensor to the point density to the classes that carry the deliverable. Vegetation management along the right-of-way is one of the most common: crews need to know where trees and brush are growing into the space around the line so cutting can be planned before a branch becomes a fault. Clearance assessment measures the distance between the conductors and everything beneath and beside them — ground, vegetation, buildings, road and rail crossings — under the conditions captured at flight time. Asset inventory records where the structures stand and what sits at each one. And engineering re-modeling rebuilds the geometry of the line itself, so the conductors and structures can be carried into modeling tools that study sag, tension, and loading.

How the corridor is flown follows from span length and the level of detail required. Long transmission lines crossing open country are often flown by helicopter, which can hold a slow, low, steady pass directly over the right-of-way. Fixed-wing aircraft cover wide networks and longer routes efficiently where the line runs for hundreds of kilometres. UAVs are increasingly used for shorter runs, substation approaches, and detailed re-flights where a dense cloud over a few spans is worth more than broad coverage. Whatever the platform, the classification problem that lands on the mapping team is the same: separate the wires and structures from the ground and vegetation, cleanly, span after span.

The classes that carry a corridor scene

A corridor block uses the same ASPRS LAS classification codes as any other job, but the weight sits on a small group of them. Three codes describe the aerial part of the scene, and a handful more describe the ground it hangs over.

Two points are worth making about how these codes are used in practice. The shield wire in code 13 sits above the phase conductors and is there to intercept lightning; keeping it separate from the phases in code 14 matters because the two are measured against different things. And distribution poles do not have a dedicated ASPRS code of their own — in practice they are usually carried in the transmission tower or structure class, or in a project-specific code agreed with the client. What matters is that the convention is written down and held the same way across the whole job.

Why wires are genuinely hard to classify

Conductors are the reason corridor classification is a specialty rather than a variation on ground work, and the difficulty comes from the nature of the target itself. A conductor is a thin linear feature suspended in open air — a few centimetres across, with nothing behind it to reflect off. A pulse only returns from a wire when it strikes it more or less dead on, so any single span carries sparse, scattered returns rather than the dense surface a rooftop or a field gives back. The classifier has to connect a broken string of points into a continuous line and decide it is one conductor and not noise.

The geometry does not sit still either. A conductor sags in a catenary curve between its supports, and the depth of that sag changes with temperature and electrical load at the moment of acquisition — the same span flown on a hot afternoon hangs lower than on a cold morning. That is exactly why the flight conditions matter for clearance work: the cloud captures the line as it hung that day, not at some nominal design state. At each structure the wires converge and cross, so the clean separation between phases breaks down right where the conductors meet the tower. And where the right-of-way has not been cleared recently, vegetation grows up into and beside the span, putting tree returns at nearly the same height as the wire — the single most common source of confusion in a corridor block.

What good corridor classification enables

When the conductors, shield wires, and structures are cleanly separated from the ground and vegetation, the deliverable stops being a point cloud and becomes an input to the work the corridor was flown for.

The most direct product is span-by-span clearance review: with conductors on their own layer and ground and vegetation on theirs, the distance between the line and everything under and beside it can be measured span by span, and the places where a tree or the terrain crowds the wire can be flagged. The classified conductors and structures also feed engineering modeling tools that reconstruct the line's geometry — carrying the catenary of each span and the position of each structure into software that studies sag and loading. And because the vegetation is classified alongside the wires, the same block prioritizes vegetation work: crews can be sent first to the spans where growth is closest to the conductors rather than walking the whole line blind.

Review before delivery

A corridor block is rarely accepted on the first pass, and the review checks are specific to the features that make the scene hard. Before a block ships, a reviewer works through the corridor class by class:

• Conductor continuity: each conductor runs unbroken span to span, without a phase dropping out mid-span or a gap where sparse returns were left unclassified.
• Tower and structure completeness: every structure is present and fully captured, and nothing is missing between two spans that clearly connect.
• Shield versus phase: the overhead shield wire is held apart from the phase conductors rather than merged into a single layer.
• Vegetation touching wires: tree returns growing into the span are classified as vegetation, not swept into the conductor class where they would corrupt clearance measurements.
• Structure junctions: the point where wires converge at a tower is separated cleanly, since this is where phases most often merge.
• Ground under the span: the terrain the clearance is measured to is clean, with no wire or vegetation returns left in the surface.

Corridor classification in Vecten Desktop

Corridor work lines up with how classification tools are organized in practice. In Vecten Desktop it is handled by VUtilities, the module for corridor assets — wire conductors, poles, and transmission towers — separating them from the ground and vegetation beneath and producing reviewable outputs a mapping team can check span by span before delivery. Because the conductors, structures, and vegetation come out as distinct layers, the same block that classifies the corridor is also the one a reviewer walks to confirm continuity and clearance.

However the corridor is flown and whatever tool classifies it, the classes are the shared language of the deliverable. Knowing why code 14 is hard to hold, why the shield wire in code 13 is kept apart from the phases, and what a reviewer checks span after span is what lets a corridor block move from a scattered set of returns to a product a clearance or engineering team can build on.