Exporting LAS files failed: Unexpected error in LASExporter::ExportTINRaster()

📌 Problem

When attempting to build or update a TIN (Triangulated Irregular Network), the operation produces unexpected results or fails. For example, an error encountered while exporting digital elevation models using the LP360 Export Wizard:

[Window Title]

LP360 Error

[Main Instruction]

Exporting LAS files failed. (17340)

[Expanded Information]

Exception Information:

HRESULT: 0x8000ffff

Description:

Unexpected error in LASExporter::ExportTINRaster()

[^] Collapse this [ ] Do not show exceptions again. [OK]

[Footer]

Press 'Ctrl+C' to copy message to clipboard.

🔍 Root Cause

✅ Probable Resolutions

Before rebuilding your TIN, confirm:

• No duplicate XY points exist
• Points are not all in a straight line
• Breaklines do not overlap or self‑intersect
• Long breaklines are properly densified
• Coordinate system and units are correct
• Required point classes exist across the area

1. Duplicate or Conflicting Points

Two or more points exist at the same XY location. This commonly occurs when data from multiple sources is merged or when points overlap exactly but have different elevations.

Resolution:

• Check for duplicate XY coordinates
• Remove or merge overlapping points
• Rebuild the TIN after cleaning the data

Learn how to use the Duplicate Points Classifier PCT

2. Points Aligned in a Straight Line

If nearby points fall along a straight line with little spatial variation, valid triangles cannot be formed.

Resolution:

• Ensure points have sufficient spatial distribution
• Add supporting points where needed
• Avoid using only linear features to create a surface

3. Invalid or Overlapping Breaklines

Breaklines that have topological issues, such as they cross themselves, overlap, or intersect without proper nodes can prevent the TIN from enforcing them correctly. Use Feature Analyst to review the breaklines for any issues. If using more than one feature file, turn on on-the-fly topological corrections in the breakline enforcement settings.

Resolution:

• Inspect breaklines for self‑intersections or overlaps
• Split breaklines at intersections
• Remove duplicate or overlapping line segments

4. Breaklines Too Close to Existing Points or Edges

Breakline vertices that lie exactly on, or extremely close to, existing TIN points or edges can create ambiguous geometry.

Resolution:

• Snap breaklines cleanly to existing vertices
• Slightly offset breaklines if necessary
• Simplify or densify breaklines to improve clarity

5. Coordinate System or Precision Issues

Datasets with very large coordinate values combined with very small point spacing or elevation differences can exceed numeric precision limits.

Resolution:

• Verify the correct coordinate system is assigned
• Ensure units are consistent and appropriate
• Avoid unnecessary scaling or unit conversions

6. Long Line Segments Without Enough Vertices

Breaklines that span long distances without intermediate vertices may not enforce correctly on the surface.

Resolution:

• Densify long breaklines
• Add vertices where elevation changes occur
• Rebuild the TIN after editing

7. Mixing 2D and 3D Data

Using a combination of 3D points and 2D features requires draping 2D features onto an existing surface. If the base surface is incomplete, this can fail.

Resolution:

• Confirm a valid base surface exists before enforcing breaklines
• Ensure 2D features are appropriate for draping
• Rebuild the TIN before adding constraints

Learn more about Conflation

8. Missing Data Due to Filters

If the TIN is built using a filtered subset of points (for example, ground only), areas without points in that filter cannot be triangulated.

Resolution:

• Verify points exist across the entire area of interest
• Adjust display or processing filters if necessary
• Check for gaps before building the TIN

📚 Additional Notes

Cleaning and validating point and breakline geometry before building a TIN will resolve the majority of issues. If problems persist after reviewing the items above, contact LP360 Support and include:

• A description of the workflow being used
• Any error messages shown
• A small sample of the data, if possible

📬 Need Help?

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