Key takeaways
- Imagery and LiDAR answer different questions. Imagery shows where vegetation is and how dense it is. LiDAR measures how tall it is and how far it sits from the conductor or the pipe.
- A clearance number is a distance between two things, so both have to be measured. The vegetation surface and the conductor or ground surface are separate datasets, and the clearance is the gap between them.
- Conductor position moves with load and temperature. A clearance measured on a cool low-load day is not the clearance at peak, which is why the standard your own engineering group applies matters more than the raw measured distance.
- Leaf-off capture measures structure. Leaf-on capture measures encroachment as the line sees it in summer, so the window you fly is a decision about which question you are answering.
- Two captures give a growth rate, which is what actually drives a cutting schedule. One capture tells you where you are standing today.
- The output has to be a work list, not a map. A span, a location, a measured clearance and a priority is what a crew can act on.
- Vegetation under a dense canopy and anything below grade are invisible to both sensors, so the deliverable should flag where occlusion limited the measurement rather than imply uniform coverage.
- The clearance standard is yours. We measure and report what is there against the threshold you supply; the compliance reading stays with your engineering group.
Vegetation management on a right-of-way is a budgeting problem disguised as a field problem. The money is finite, the corridor is long, and the decision every year is which spans get cut now and which can wait. Walking the line to find out is slow, and driving it only shows you what is visible from the access trail.
Aerial capture changes that, but only if the output is a work list. A beautiful point cloud that nobody can turn into a cutting plan is a cost rather than a tool.
Imagery and LiDAR are answering different questions
These get bundled together in conversation and they do genuinely different jobs.
Imagery gives you extent and density. Where the vegetation is, how continuous it is along the corridor, where the edge has crept in from the treeline, which spans are clear and which are closing in. In colour it also gives you some species and health signal, which matters if the concern is danger trees outside the corridor rather than growth inside it. What imagery does not give you directly is height. Photogrammetry can produce a surface, and over vegetation that surface is the top of the canopy, which is useful, but it is weak where the canopy is broken or the texture is poor.
LiDAR gives you height and structure. Because the pulse penetrates gaps in the canopy, a LiDAR capture returns both the top of the vegetation and, in many places, the ground beneath it. That is what makes a vegetation height measurement meaningful rather than inferred. It also returns the conductor itself on a powerline, which is the other half of the clearance calculation.
In practice a serious encroachment program uses both. The LiDAR carries the measurement and the imagery carries the interpretation, because a clearance exceedance on a screen is much easier to act on when the crew can see what species and what access they are walking into.
Clearance is a two-surface problem
This is the part that gets lost. A clearance is not a property of the vegetation. It is a distance between the vegetation and something else, and that something else has to be measured too.
On a transmission or distribution line, the other surface is the conductor. A LiDAR capture that resolves the conductor lets the clearance be computed directly as the distance from each vegetation return to the nearest point on the wire. On a pipeline right-of-way, the concern is usually different: root intrusion risk, access for patrol and emergency response, and the ability to see the surface at all during an aerial or ground patrol. There the relevant measurement is vegetation height above ground within the corridor boundary, which needs the bare-earth surface rather than a conductor.
Either way, two datasets, one subtraction. And the quality of the answer is limited by the weaker of the two.
The conductor does not sit still
A measured clearance is a clearance on the day, at the load and temperature on the day. Conductors sag more when they are hot and heavily loaded, and they move laterally in wind. A capture flown on a cool morning at low load will show more clearance than the same span has on a hot afternoon at peak.
We are not the right party to decide what to do about that. What we can do is record the conditions at capture and deliver the measured geometry, so that your engineering group can apply whatever sag model and clearance standard they work to. Any vendor who hands you a clearance number without stating the capture conditions is handing you a number that cannot be audited.
The same logic applies to the threshold itself. The clearance criterion is set by your own standard or by the authority you answer to, and it is not ours to assert. The deliverable reports measured distances against the threshold you supply, and flags what falls short of it.
Leaf-off or leaf-on
In Alberta this is a real fork rather than a technicality, because the two windows answer different questions.
Leaf-off, in late fall after drop or in early spring before flush, gives the cleanest structural measurement. LiDAR penetrates better, the ground surface underneath is far better defined, and stem and branch geometry is visible. If you want to know the physical structure of what is in the corridor and get a reliable bare-earth surface, this is the window.
Leaf-on, through the summer, measures the canopy at its largest. That is the encroachment the line actually experiences during the season when load is highest. It is the better window if the question is operational risk right now rather than structure.
Programs that run for several years tend to settle on one window and hold it, because comparability between captures is worth more than optimising any single one. Mixing the two across years produces an apparent growth figure that is partly a seasonal artefact.
Cadence is what produces a growth rate
A single capture tells you the current state of the corridor. Useful, and not the thing that changes how you budget.
Two captures a known interval apart give you growth per year by span. That is the number that lets you schedule rather than react: a span with fast growth and marginal clearance is a different priority from a span with the same clearance and slow growth, and without a rate you cannot tell them apart.
The interval has to be long enough that real growth exceeds the measurement uncertainty, and that depends on species, site productivity and how good the captures are. An annual cycle is the common starting point because it is operationally simple and lines up with budget cycles. Whether that is right for a given corridor is a question for the people who know what grows there. What matters technically is that the interval is known and the method is held constant, so the difference is growth rather than noise.
Turning the capture into a cutting plan
The deliverable that gets used looks like a schedule, not a dataset. For each span or segment:
- A location identifier that matches how your crews already refer to the corridor.
- The measured minimum clearance, with the capture date and conditions attached.
- Whether it is inside or outside the threshold you supplied.
- Growth rate where a prior capture exists.
- An estimate of the work, usually area or stem count, so it can be priced.
- Access notes that are visible from the air, such as whether the span is reachable from an existing trail, water crossings, and terrain.
Sorted by priority, that is a cutting plan. Supplied alongside the imagery and the point cloud, it is also auditable, because anyone can go back to the source data for a span they disagree with.
The access notes are the part clients tend not to ask for and then use the most. A corridor segment that needs clearing and has no vehicle access is a materially more expensive job than one beside a road, and knowing that before the tender rather than after is worth real money.
What the capture will not tell you
Neither sensor sees through a dense canopy to the small vegetation underneath, so understory in heavily treed segments is poorly measured and the deliverable should say where. Nothing below grade is visible, so root systems and buried infrastructure are out of scope. Species identification from the air is a reasonable signal rather than a determination, and where species drives the treatment decision it needs ground confirmation. Internal decay, structural defects in a danger tree and anything requiring an arborist's judgement are not aerial findings.
And the capture does not determine compliance. It measures geometry against a standard you provide. The reading of that against your obligations stays with your own engineering and vegetation staff.
How to scope the first one
Four questions. What is the corridor boundary, as a file rather than a description. What clearance threshold are we reporting against, and who owns it. Is the concern inside the corridor, danger trees outside it, or both, because the second one widens the capture extent. And is this a one-off assessment or the first capture in a program, because a program means fixing the window, the boundary and the coordinate system now rather than at capture three.