LiDAR point-cloud recovery

A damaged LAS or LAZ file may retain point records even when its header, offsets, bounds, or compressed chunks fail.

LAS stores a public header, variable-length records, point records, and optional extended records. LAZ adds compression. Truncation or incorrect offsets can prevent a reader from locating valid point data.

Understand the symptom

Point interpretation depends on the header, record format, scale, offset, and coordinate metadata.

WHY

What is happening

The LAS specification defines the LASF signature, header size, point-data offset, record format and length, point counts, scale factors, offsets, and coordinate bounds. Incorrect values can make intact records appear absent or geographically wrong.

What you may see

Symptoms that change the recovery path.

01

Invalid LAS signature or header

The header may be overwritten or the file mislabeled.

02

Zero points or wrong count

Count fields or point-data offsets may not match payload length.

03

Coordinates are far away

Scale, offset, CRS, or byte interpretation may be wrong.

04

LAZ decompression stops

A compressed chunk or end of file may be damaged.

Protect the source

Actions that can make the situation worse.

01

Header repair can hide provenance

Retain the untouched source and every changed copy.

02

Wrong point format misaligns records

One bad record length corrupts interpretation of following points.

03

Tile merging can duplicate or omit data

Validate bounds and identities before combining outputs.

Do this now

Safe steps before evaluation.

01

Copy all tiles and indexes

Keep original names, sizes, checksums, hierarchy, and neighboring tiles.

02

Collect survey metadata

Preserve CRS, trajectory, calibration, flight lines, acquisition dates, and processing logs.

03

Record expected point properties

Note point format, count, returns, scale, offset, bounds, and extra dimensions.

04

Protect the source device

Image storage that reports CRC errors, disconnects, or short reads.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Header and payload mapping

NEPFOSYS compares declared offsets and formats with available bytes.

02

Copy-based point extraction

Readable records or compressed chunks are exported to new files.

03

Geospatial validation

Counts, bounds, scales, CRS, returns, classifications, and sample coordinates are checked.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can a LAS file have points with a broken header?

Yes. Point records may remain, but their format, location, scale, and CRS must be reconstructed accurately.

Is LAZ recovery the same as LAS?

No. LAZ adds chunked compression, so compressed-stream damage may limit which point ranges can be decoded.

Should I run a header repair tool first?

Only on a duplicate after recording the original structure and expected survey metadata.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case