A Special Note About LAS Files and Coordinate Systems

Referenced From

4. Non-Standard Coordinate Systems — Client-requested coordinate systems that modify an official EPSG definition are considered non-standard coordinate systems. While some client software platforms may support such configurations, the Company may not be able to generate such coordinate systems, cannot guarantee positional accuracy when data is transformed into non-standard systems, and does not certify data accuracy for coordinate systems lacking an official EPSG code. View in Deliverable Formats Addendum

Why the LAS Header Matters

LAS files are not just point data — they also contain a header that describes how the data should be interpreted.

Every LAS file includes a standardized header that stores critical information such as:

  • Coordinate reference system details.
  • Units and scaling factors.
  • Offsets and bounding information.

When LAS files are imported into software, the very first thing the software reads is the header — not the point data itself.

If the header information does not accurately describe the data inside the file, software may:

  • Fail to import the file
  • Apply incorrect scaling
  • Shift or distort the data
  • In worst cases, apply seemingly random scaling that causes the data to misalign entirely with other datasets.

1. Why Non-Standard Coordinate Systems Are Especially Risky for LAS

Non-standard or custom coordinate systems (for example, modifying a meter-based EPSG system into U.S. Survey Feet without a corresponding EPSG code) present a unique challenge for LAS files.

This is because:

  • LAS headers rely on standardized formatting.
  • There is no universally accepted way to represent custom CRS definitions in LAS headers.
  • Different software platforms interpret LAS headers slightly differently.

While LAS standards exist, they are loosely enforced, and real-world implementations vary across GIS, CAD, survey, and point cloud software.

There is no single header configuration that is guaranteed to work correctly in every software environment.

2. Custom LAS Header Work (When Requested)

In limited cases, we have developed custom LAS headers tailored to specific client software environments.

Important considerations:

  • This process is time-intensive, often requiring:
    • Iterative testing
    • Multiple software imports
    • Manual header inspection and adjustment
  • Additional processing time may range from 8 to 15 hours or more.
  • This work is billed at custom data processing rates.

3. No Guarantee and Speculative Nature of Custom LAS Header Work

Because of the variability across software platforms:

  • Custom LAS header work is performed on a best-effort basis.
  • No guarantee can be made that a custom header will work in all client software.
  • Even with extensive effort, results may vary depending on the client's tools and configurations.

If custom LAS header work is requested:

  • It must be explicitly agreed to in writing.
  • It is considered speculative work.
  • Payment is required regardless of outcome, provided the agreed work was performed.

4. Best Practice Recommendation for LAS Deliverables

To minimize risk:

  • Use official EPSG-recognized coordinate systems whenever possible.
  • Avoid custom unit conversions or modified CRS definitions.
  • Confirm CRS requirements with your surveyor, engineer, or GIS lead before work begins.

Following these practices significantly improves interoperability and reduces the risk of import, scaling, or alignment issues.

Plain-English Bottom Line

LAS files are powerful — but they are also sensitive to how their headers are structured.

Custom or non-standard coordinate systems dramatically increase complexity and risk. While we will always try to help, accuracy certification and guaranteed compatibility are only possible when industry standards are followed.