Troubleshooting: “invalid bounding box: at least one axis has a size of zero”

📌 Problem

“invalid bounding box: at least one axis has a size of zero”

🔍 Root Cause

The error means that one or more LAS files in your dataset have invalid spatial extents. In simple terms, LP360 is trying to build a map boundary around a tile, but the tile is so small or improperly formed that the boundary collapses to zero width or height.

This is almost always caused by a problem LAS tile, not by LP360 itself.

Customers typically run into this error for one of the following reasons:

1. A LAS tile contains extremely few points

Some tiles may contain only one or very few points, which prevents LP360 from creating a valid bounding box.

2. A LAS file is unusually small or corrupted

If a file is only a few kilobytes in size, or was generated incorrectly, LP360 cannot process it.

3. Issues during tiling or flight planning

Incorrect flight coverage or tiling settings may produce malformed tiles that trigger this error.

✅ Probable Resolutions

You can resolve this quickly by following these steps:

1. Check your LAS tiles

Open the dataset in LAS File Analyst and look for:

• Very small files (a few kilobytes)
• Tiles with unusually low point counts
• Tiles that visually appear empty or incorrect

2. Remove or replace the problematic tile(s)

Once you identify the tile causing the issue:

• Remove it from the dataset and re-run geocoding/pyramiding, or
• Regenerate it by re-exporting or reprocessing the affected portion of the project.

This step resolves the problem in nearly all customer cases.

3. Validate flight planning

4. If the problem persists, reprocess your data

Try:

• Re-running the AI Ground or classification step
• Reimporting the cycle
• Checking your flight plan for data gaps

📬 Need Help?

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