Format Atlas

Guides

Handing Off Point Clouds with LAS, LAZ and E57

Point-cloud handoffs need coordinates, attributes, scan context and reader support, not just an extension. This is distinct from mesh or 3D-print workflows.

Which format should you choose?

Choose by the role each file plays in your workflow.

  • Agree on required information and versions
  • Record conversion and coordinate operations separately
  • Validate in the receiving environment

Agree on required information and versions

Check recipient software, LAS version and point-record format, LAZ support, and E57 image/pose support. List CRS, axis order, units, vertical datum and required color, intensity or classification. Do not equate LAS 1.5 and LAZ 1.4 support.

Record conversion and coordinate operations separately

When combining local coordinates or scan poses, document applied transforms. Check LAS scale/offset and extra attributes, E57 images and scan identity; supply separate documentation for information that cannot survive. Distinguish compression from thinning, filtering and coordinate transformation.

Validate in the receiving environment

Compare counts, bounds, representative positions, attributes, images and CRS before and after conversion. Bundle required files and documentation with checksums, settings and software versions. Test real loading; size reduction alone is not success.

Formats to consider

LAS

Good for: Exchange LAS attributes with supported tools

Less suitable for: Preserve a complete scan-image and acquisition package

LAZ

Good for: Losslessly compress storage and transfer in compatible workflows

Less suitable for: Deliver to recipients without confirmed LAZ support

E57

Good for: Deliver images and scan-level context to supported tools

Less suitable for: Deliver unchanged to tools that accept only LAS

Before you export

  • Clouds may reveal sensitive locations, facilities or acquisition conditions. Check sharing scope and use restrictions.
  • Keep originals and document losses and transforms. Equal counts do not prove correct positions or attributes.

Related comparisons

LAS vs LAZLAS stores point records without compression; LAZ losslessly compresses supported LAS data. Reader compatibility matters as well as size.E57 vs LASE57 exchanges scan points, images and acquisition information. LAS standardizes LiDAR and other point records and attributes; overlapping uses do not mean identical structures.PLY vs PCDPLY handles vertices and faces; PCD handles point fields and organization for PCL. Both can store points, but their structures differ.

Guides

Checks before handing off GIS dataAgree on layers, coordinate reference systems, attributes and recipient software. Beyond choosing a format, verify positions and retained information after conversion.

References and specifications