Error 92: File to Pyramid is Too Small Based on Header (810) – LP360

📌 Problem

Adding a LAS file to LP360 and attempting to generate pyramids results in the error,

"The following files had errors while pyramiding:

Failed to create LPLAS for file

'file.las'

Detail:

92: File to pyramid is too small based on header (header size plus points times pnt_size). (810)"

🔍 What the Error Means

The error indicates a mismatch between the LAS file's header information and the actual data content. Specifically, the error occurs in LP360 when the LAS file’s actual size is smaller than expected based on its header metadata. The system calculates expected size using:

header size + (number of points × point size)

If the file is smaller than this calculation, LP360 throws error 92.

🧠 Common Causes

Corrupted or truncated LAS file
Third-party edits without updating the pyramid (.qvr) structure
File processed on a network drive (access/locking issues)
File exceeds 4GB and triggers bugs in older LP360 versions

✅ Probable Resolutions

1. Recopy Corrupt Files

If the LAS file was obtained from a third party:

Check the file size versus the original file.
Use a robust copy tool such as TeraCopy or Robocopy to recopy the file.

2. Delete and Rebuild Pyramids

If the LAS file was modified externally:

Go to the LAS Files tab next to the TOC.
Right-click the LAS layer.
Select Rebuild Pyramids.

3. Check Disk Space

Ensure sufficient space is available on:

The drive containing the LAS file.
The drive hosting the Windows temp folder.

4. Use Local Storage

Move LAS files to a local drive before importing into LP360. Avoid using network drives.

5. Update LP360

If using an older version, upgrade to the release (e.g., v2023.2.18.0 or higher) to resolve known bugs with large LAS files.

6. Convert to LPLAS Format

For better performance and stability, use the LPLAS format instead of the older QVR pyramids:

Right-click the LAS layer
Select Generate LPLAS
Use the LPLAS layer for classification and editing

Tip: If you frequently encounter this error, consider automating pyramid rebuilds or using LPLAS as your default format.

7. Attempt to Load Corrupted Files

LP360 includes a recovery feature that allows you to try loading LAS files that are:

Partially corrupted
Missing header information
Improperly formatted
Structurally inconsistent

This is done by enabling the “Attempt to Load Corrupt Files” checkbox in the Add Files dialog. When selected, LP360 will try to recover and load as much usable data as possible from the file.

🧪 Recommended Workflow

Enable Recovery Mode
- In the Add Files dialog, check “Attempt to Load Corrupt Files”.
- Choose Read-Write access if you plan to repair the file.
Use LAS File Analyst (LFA)
- After importing, run the LAS File Analyst tool.
- Scan the file to identify issues like:
  - Missing headers
  - Invalid point data
  - Incorrect formatting
- Enable repairs for detected issues.
- Optionally add WKT if projection info is missing.
Verify Integrity
- After repair, reload the file and confirm that point cloud data is visible.
- If only footprints load, the file may be too damaged for full recovery.

⚠️ Limitations and Cautions

Severely damaged files may only load footprints, not full point cloud data.
LP360 may crash if the file contains corrupted EVLRs (Extended Variable Length Records). In some cases, LP360 will ignore EVLRs to prevent crashes.
Files with stray points or mismatched EPSG codes may require manual reprocessing or header repair using LFA tools.

📚 Helpful Resources

📬 Need Help?

If you're still stuck, please Contact Support for assistance.

Related to