> For the complete documentation index, see [llms.txt](https://docs.terraref.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terraref.org/beta/user-manual/data-products/point-cloud-data.md).

# Point Cloud Data

## Summary

3D point cloud data is collected using the Fraunhofer 3D laser scanner. Custom software installed at Maricopa converts .png output to the .ply point clouds. The .ply point clouds are converted to georeferenced .las files using the 3D point cloud extractor

Level 1 data products are provided in both .las and .ply formats.

For each scan, there are two .ply files representing two lasers, one on the left and the other on the right. These are combined in the .las files.

## Sensor information

* [Fraunhofer 3D scanner collection](https://terraref.ncsa.illinois.edu/clowder/files/581793394f0ce77b66562ff9?dataset=581789af4f0ce77b6655d094\&space=)

For details about using this data via Clowder or Globus, please see [Data Access](/beta/user-manual/how-to-access-data.md) section.

## Data access

Data is available via Clowder, Globus, and Workbench.

* **Clowder**: [Laser Scanner 3D LAS](https://terraref.ncsa.illinois.edu/clowder/collection/5a0ca1ad4f0ca87e15b485e8)
* **Globus or Workbench File System**:
  * LAS `/sites/ua_mac/raw_data/laser3D_las`
  * PLY `/sites/ua_mac/raw_data/laser3D`

## Computational pipeline

Raw sensor output (PLY) is converted to LAS format using the `ply2las` extractor

[**ply2las**](https://github.com/terraref/extractors-3dscanner)[ **extractor**](https://github.com/terraref/extractors-3dscanner)

## See also

* [Geospatial information](https://github.com/terraref/documentation/tree/a6e3a2c5990b2e866d233fbb0f61a4dd6acc1b9e/user/geospatial-information.md)

## Known issues

* The position of the lasers is affected by temperature. We plan to add a correction for temperature that will adjust for this effect. See [terraref/reference-data#161](https://github.com/terraref/reference-data/issues/161)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.terraref.org/beta/user-manual/data-products/point-cloud-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.