THE FILE FIELD GUIDE
.laz

LAZ Compressed Point Cloud

Maps & GPS

LAZ losslessly compresses LAS point data and needs point-cloud decoding support rather than ordinary document extraction. Lossless compression does not prove that earlier filtering or attribute removal never occurred.

Main use
Store LAS point clouds with lossless compression
Data type
Binary data
All sections, questions and sources

Content reviewed: · Editor:Kai

Opening steps

Choose your environment or purpose to see its steps.

LASzip / PDAL / LAZ-compatible software

Preserve the original and inspect a working copy in a compatible application.

  1. Open a copy directly in LAZ-capable point-cloud software.
  2. If needed, decode to a separate LAS with LASzip or equivalent.
  3. Inspect point count, coordinate bounds and attributes.
Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

  1. Check underlying LAS/point format and LAZ support.
  2. Estimate decompressed size and workspace.
  3. Ask about subsampling/classification changes before delivery.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Ordinary extractor fails: use an LAZ point-cloud decoder.
  • Legacy software rejects it: check point-format/compression support.
  • Fewer points: investigate subsampling rather than assuming compression loss.
  • LAS too large: consider direct LAZ reading or spatial subsets.

LAZ → LAS / selected region

  1. Decode to LAS or export the required region through supported software.
  2. Verify CRS, point count, classifications/attributes and required spatial extent.

Decompression cannot add missing points/attributes; separately inspect output scale/offset and field selection.

Lossless compression versus processing history

LAZ losslessness concerns compression. Prior classification, thinning or reprojection are separate processes requiring provenance and accuracy checks.

Source for these steps:LASzip project · LASzip: lossless LiDAR compression / PDAL project · readers.las / PDAL project · writers.las

Worked example: checks before handoff

Example: compare decoded point counts/attributes for an unmodified compression; for processed data, inspect processing conditions rather than expecting the original count.

Source for these steps:LASzip project · LASzip: lossless LiDAR compression / PDAL project · readers.las / PDAL project · writers.las

Related-format differences

Related-format differences
Format / methodPurpose and preserved information
.lazStore LAS point clouds with lossless compression
LAS / ZIPLAS is uncompressed point data; ZIP is a generic archive without point semantics.
LAZ → LAS / selected regionDecompression cannot add missing points/attributes; separately inspect output scale/offset and field selection.

Handling and security

Review licensing and sharing scope for detailed building/terrain locations.

Questions and answers

Can it be renamed ZIP?

No; use a matching point-cloud decoder.

Does small LAZ mean lower accuracy?

Size alone does not establish accuracy; inspect coordinate encoding and processing history.

Does decompression add points?

It restores stored data, not points removed before compression.

Format facts: name, steward and MIME type
Formal name
LAZ Compressed Point Cloud
Steward / specification
LASzip project
MIME type
Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources

  • Project documentationLASzip: lossless LiDAR compression

    Lossless LAS compression and compatible implementations.

    LASzip project · Link checked:
  • Software documentationreaders.las

    Reading LAS/LAZ, point attributes and record formats.

    PDAL project · Link checked:
  • Software documentationwriters.las

    Coordinate scale/offset, versions and output attributes.

    PDAL project · Link checked: