Blog

Path profile vs. Fresnel clearance report: what each document shows

A telecommunications tower with antennas on a forested hilltop under a clear blue sky.

If you've pulled a path profile for a new hop and then had someone ask for "the Fresnel clearance report" like it's the same document, you're not alone. They're related, but they answer different questions, and conflating them is how trim budgets get spent on the wrong hops.

What a path profile contains

A path profile is the baseline elevation plot between your two antenna sites. Pull it from a tool like Pathloss or a carrier's internal RF planning suite and you get a line-of-sight elevation profile: ground height at every point along the great-circle path, your two tower or mast heights, earth curvature correction at whatever k-factor you're designing to (0.667 standard, maybe worse for a coastal or ducting-prone route), and the straight ray trace between the antennas.

This is the document you build the link on. It's what tells you whether the hop clears a ridgeline, whether you need a taller tower at one end, and what your first-order Fresnel radius looks like at the worst pinch point. A path profile survey, done properly, uses surveyed terrain data or LiDAR, not just a 90 m SRTM tile, because a 15 m error in ground elevation at the right spot can eat your whole margin.

But a path profile is a design-time document. It's drawn once, when the link is engineered, maybe revisited if you change antenna heights or re-route. It does not get updated every growing season.

Where Fresnel clearance comes in, and where it stops

Fresnel clearance is a calculation that rides on top of the path profile, not a separate survey. It defines the ellipse around that direct ray, typically the zone you want 60 to 100 percent clear of obstructions at your design k-factor, and it's where vegetation height matters most. The path profile tells you where the ridge is. The Fresnel clearance report tells you how much air you have above that ridge, and above whatever is growing on it, before the signal starts picking up diffraction loss or scintillation.

Here's the part that trips people up: the original path profile usually assumes a terrain surface, bare ground, maybe with a clutter allowance baked in at design time. It does not know that the eucalyptus stand at the 4 km mark has put on six meters since the link went live. That's a separate, ongoing problem, and it's not something a path profile revision catches unless someone goes back out and re-surveys clutter height along the whole route, which nobody budgets for every year.

Why you need both, on different schedules

Think of it as one document at commissioning and one check on a recurring cadence. The path profile is your as-built reference: terrain, tower heights, the theoretical clearance envelope. The vegetation side is the part that moves. A tree doesn't care what your k-factor assumption was in 2019.

So when a planner asks "do we have a current Fresnel clearance picture," what they need isn't a redrawn path profile. They need to know current canopy height against the clearance envelope that profile already defined. That's a narrower, cheaper question, and it's the one that actually predicts whether a hop is going to start throwing fade margin alarms next monsoon season versus one that's fine for another three years.

Teams that treat these as the same ask end up either re-surveying the whole path profile unnecessarily (expensive, and terrain doesn't change) or skipping vegetation checks entirely because "we already have a path profile" (cheap now, expensive when the fault ticket comes in). Neither is the right call. Link Vegetation Monitor is built around the second, narrower question specifically: canopy height against your existing Fresnel envelope, checked once a year, so you know which hops need a trim crew before the signal tells you.

If your path profiles are solid but nobody's checked what's grown into the clearance envelope since commissioning, that's the gap worth closing first.

← Back to the blog