Case study · Geomatics & linear engineering

Corridor LiDAR processing pipeline

We built an end-to-end corridor LiDAR processing pipeline that turns raw mobile-mapping scans into engineering-ready DTM deliveries, holding positional drift under 3 cm on bridge decks and shipping about 200 km of corridor per week with a single operator.

Start a similar project →All case studies
Context

The situation.

State road authority, 4,100 km of sealed corridors resurveyed on a rolling two-year cycle.

Scope

End-to-end pipeline for linear-corridor mobile-mapping scans: RAW trajectory smoothing against a CORS network, scan-to-trajectory registration, ground/non-ground classification, breakline-enforced DTM generation, and delivery packages conforming to the authority GIS schema. Acceptance criteria were positional accuracy per 100 m segment, not per dataset.

Outcome

Target throughput of ~200 km of corridor scans per week with a single operator, accuracy certificate issued per delivery batch.

Delivery

Delivered by Epcotec Pty Ltd, Canberra · Client location: Hume Highway corridor, NSW–ACT–VIC

Stack
PythonC++PDALPostGISS3
Challenges

What made it hard.

Registration drift of 6-11 cm appeared on bridge decks where GNSS multipath peaked: we introduced control-point constraints extracted from the previous epoch and constrained-spline trajectory blending, holding drift under 3 cm.

Classification confused sparse understorey with low vegetation in riparian segments: we added a local height variance feature and a width-of-return classifier pass, cutting manual correction area by 71%.

FAQ

Common questions.

What was the scope?

End-to-end pipeline for linear-corridor mobile-mapping scans: RAW trajectory smoothing against a CORS network, scan-to-trajectory registration, ground/non-ground classification, breakline-enforced DTM generation, and delivery packages conforming to the authority GIS schema. Acceptance criteria were positional accuracy per 100 m segment, not per dataset.

Who was the client?

Client names are withheld under confidentiality agreements. References are available on request.

What was the outcome?

Target throughput of ~200 km of corridor scans per week with a single operator, accuracy certificate issued per delivery batch.

Related capability

Data & MLOps

Ingestion, warehousing, pipelines, model serving, drift monitoring.

Explore this capability →
Trust

This is one of roughly fifty engagements we ship per year. The full record, 2011 to today, lives on the delivery history page.

Have a similar problem?

Fixed scope, senior engineers, staging from week one.

Start a project →