Compare
E57 vs LAS
E57 exchanges scan points, images and acquisition information. LAS standardizes LiDAR and other point records and attributes; overlapping uses do not mean identical structures.
Which format should you choose?
Consider E57 for images and scan-level context, LAS for GIS or point-cloud workflows that consume LAS attributes.
Good fit for E57
Exchange 3D scanner point clouds and measurement data · Hand off scan points with related photographs
- Data exchange between 3D imaging workflows
- Keeping points and related images together
Good fit for LAS
Exchange classified and attributed 3D point clouds from LiDAR and other surveys · Inspect and process uncompressed point data in a widely used format
- Representing coordinates, intensity, returns, classification, time, color, and extra attributes
- Identifying the LAS version and point data record format when handing data off
Basic information
| Field | E57 | LAS |
|---|---|---|
| Extension | .e57 | .las |
| MIME type | ||
| Common uses | Exchange 3D scanner point clouds and measurement data · Hand off scan points with related photographs | Exchange classified and attributed 3D point clouds from LiDAR and other surveys · Inspect and process uncompressed point data in a widely used format |
| How to open | Open with E57-capable point-cloud or GIS software. Check point count, coordinate system, units, color/intensity, scanner position, and imported images; record what the export cannot retain. | Use point-cloud or GIS software supporting the file's LAS version and point record format. Check version, point count, bounds, scale and offset, CRS/WKT, VLRs/EVLRs, classifications, and returns. LAS 1.5 changed CRS requirements, so verify reader support. |
| Export or convert | Before converting to LAS/LAZ, identify required attributes, CRS, units, scan pose, and photos. Compare counts, bounds, representative attributes, and images after export; retain the source E57 for information the target cannot represent. | Converting LAS to LAZ usually compresses point data losslessly, but compare metadata and any companion files too. When changing LAS versions, validate point record formats, CRS representation, waveform data, and extra bytes; do not just rename the extension. |
Choose by use case
Data exchange between 3D imaging workflows
Exchange 3D scanner point clouds and measurement data · Hand off scan points with related photographs
E57Keeping points and related images together
Exchange 3D scanner point clouds and measurement data · Hand off scan points with related photographs
E57Representing coordinates, intensity, returns, classification, time, color, and extra attributes
Exchange classified and attributed 3D point clouds from LiDAR and other surveys · Inspect and process uncompressed point data in a widely used format
LASIdentifying the LAS version and point data record format when handing data off
Exchange classified and attributed 3D point clouds from LiDAR and other surveys · Inspect and process uncompressed point data in a widely used format
LASKey point 1
E57 can carry 3D points and related 2D images.
More on the differencesKey point 2
LAS attributes depend on version and point-record format.
More on the differencesMore on the differences
Agree on required images, coordinates and attributes before conversion, retain originals, and check the receiving software's implementation.
- E57 can contain multiple scans and poses. When merging into LAS, verify coordinate transformations and how scan identity is retained.
- LAS classifications and returns may not map identically to E57. In reverse conversion, verify images, acquisition information and additional attributes individually.
Frequently asked questions
Does a matching point count prove successful conversion?
No. Check positions, units, CRS, color, intensity, classification and required images, and document losses.