Corridors are long, thin, and chainage-driven. The capture geometry is different, the deliverables are different, the coordination overhead is different, and the gotchas are different. This is the engineering version of what makes corridor work its own discipline.
If you've scoped both area and corridor LiDAR work, you know the quotes look superficially similar — hectares captured, deliverables produced, point density per square metre — and they're entirely different jobs underneath. Corridor work threads everything through a chainage system that area mapping never has to deal with, and the coordination overhead is significant enough to dominate the schedule in ways area work doesn't.
This article is what corridor work actually involves, from the linear capture geometry through to the chainage-driven deliverables your design or maintenance team will read.
An area capture is essentially a rectangle. Plan a boustrophedon flight pattern across the rectangle at adequate point density, overlap the strips appropriately, fly the plan, process the cloud, generate the deliverables. Geometry is straightforward.
A corridor capture is a long, narrow ribbon of capture — typically 100–300 m wide and anywhere from 1 km to 100 km long. The ribbon follows a centreline that may be curved, kinked at intersections, crossing structures, undulating in plan and section. The capture plan, the deliverables, and the QA all reference position along that centreline rather than position in a 2D coordinate system.
That single difference cascades through everything else.
A corridor has a chainage — a one-dimensional measure of distance along the centreline from a defined origin. The Australian convention is to express chainage in metres, often grouped into kilometre + metres notation: chainage 1247.500 is written as CH 1+247.500, the convention dating back to imperial chains but the metric values absolutely modern.
Every deliverable from the capture is keyed against chainage:
Get the chainage origin right and everything threads through consistently. Get it wrong — origin in the wrong place, direction reversed, or chainage redefined mid-project — and every reference that touches the capture has to be re-keyed manually.
The first 30 seconds of any corridor scoping call: where's the origin, which way does chainage increase, and what's the project's existing chainage definition if one exists?
A corridor capture is typically flown as multiple parallel flight strips along the corridor:
For a typical road corridor with 200 m strip width and 30% lateral overlap, two flight strips cover 280 m of capture envelope (strip 1 covering centreline ±100 m, strip 2 offset to cover the remaining 180 m on the appropriate side). Wider corridors or denser point density requirements add more strips.
The trade-off worth understanding: corridors that need both engineering-grade DTM (high point density) AND wide capture envelope (verge and adjacent land) cost more in airtime than either requirement on its own. Specifying both at scoping prevents the surprise on the quote.
For corridor LiDAR, the per-deliverable target densities are:
If the deliverable mix needs all of these (typical for road work), the capture flies to the tightest requirement — typically the pavement spec at 100–200 pt/m². Density that's necessary for the pavement is abundant for the verge and canopy, so all deliverables benefit.
Cross-sections are the engineering currency of corridor design. The interval at which they're generated drives both the deliverable usefulness and the deliverable size:
| Interval | Sections per km | Typical use | File size impact | | -------- | --------------- | ---------------------- | ---------------- | | 5 m | 200 | Design set-out | Very large | | 10 m | 100 | Civil design | Large | | 25 m | 40 | Concept design | Medium | | 50 m | 20 | Initial feasibility | Small |
The good news: cross-sections are derived, not captured. A captured DTM supports any cross-section interval you nominate post-fact. We typically deliver an initial set at 10 m or 25 m and stand ready to generate tighter intervals on demand against the same cloud.
The right interval depends on what's downstream. For a finished road design, 5 m sections at structures and chainages of interest plus 10 m sections everywhere else is standard. For early concept work, 25 m is plenty. For pure context, 50 m suffices.
The expensive mistake is to specify 5 m sections everywhere across a 30 km corridor when concept design only needs 25 m. The cloud supports both intervals; the deliverable size doesn't have to.
Where cross-sections capture the corridor across its width, the long-section captures it along the centreline:
A long-section is typically delivered as a DWG drawing with the profile, grade annotations, structure markers, vertical curve overlays and chainage labels. It's the document a designer references constantly during the design phase.
A corridor capture isn't just terrain — it's an asset-dense environment. Standard extracted assets for a road corridor:
For rail corridors:
For powerlines:
Each asset class adds extraction effort in processing and shifts the deliverable budget. Specifying the asset extraction scope at quote time keeps the pricing comparable across providers.
Linear infrastructure corridors run through vegetation, and the vegetation either is or isn't a problem:
LiDAR captures all of this as part of the standard corridor flight — no separate capture required. The deliverable is typically a span-by-span register of breaches with location, severity and recommended work zone.
Once a corridor has been baseline-captured, subsequent captures reuse the same flight plan, control and processing pipeline. Period-on-period change detection becomes a deliverable:
For asset-owning authorities (state road authorities, network operators, rail operators), this turns the corridor from a sampled-once dataset into a measurable longitudinal record. The maintenance program shifts from complaint-driven to data-driven.
Corridor work has coordination overhead that area work doesn't. Worth flagging at scoping:
A capture booked for next week is typically two weeks behind on coordination. Realistic lead time for a corridor capture from scoping to flight is 2–4 weeks, with most of that being coordination rather than airtime.
Six things to nail down at scoping to avoid re-work:
That sentence list eliminates most of the post-quote ambiguity that costs corridor projects time and money.
Corridor mapping with LiDAR is its own discipline — linear capture geometry, chainage-driven deliverables, dense asset extraction, significant coordination overhead. Cross-section interval is the deliverable lever worth understanding (derived not captured; post-fact tightening always possible). Strip width and point density set the airtime budget. Coordination usually dominates the schedule.
If you're scoping a corridor project, the article above is the checklist worth running through before requesting quotes. The road corridors vertical and rail corridors vertical walk through specific deliverables in more detail.
Tell us the alignment, chainage convention, deliverable mix and coordination context. We'll scope the capture and coordination together — corridor work is usually 50/50 capture and admin.
Interactive plan + cross-section explorer with five station types (cut, fill, bridge, culvert, at-grade). The applied version of this article.
Kinematic gauging cross-section with three structure types (at-grade, overbridge, tunnel). Rail-specific corridor work.