> For the complete documentation index, see [llms.txt](https://docs-7.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-7.phoenixlidar.com/lidarmill-desktop/workflow-kk/export-cloud/las-laz-pointcloud.md).

# LAS/LAZ Pointcloud

Export to LAS or LAZ using the Export icon:

{% hint style="success" %}
You must first [create a .cloud file](https://docs.phoenixlidar.com/lidarmill-desktop/post-processing/workflow-kk/create-a-cloud/create-cloud) in SpatialExplorer 6.0.X before exporting to LAS
{% endhint %}

![Export Cloud to LAS button in SpatialExplorer v6.0.X](/files/-M_gDB-1foCqPEkulkpi)

The Export Cloud to LAS window allows you to configure the various parameters associated with exporting the data:

![](/files/IOc9KikaNeM6rs6EyC0I)

### Data to Export (Intervals to Fuse)

This option determines which portions of the loaded trajectory will be exported to a LAS/LAZ file. You can either fuse all data or fuse only data from specified intervals. 

### Output Coordinate System

By default, SpatialExplorer will output the LAS/LAZ file in the project CRS. You can output the LAS/LAZ in a different CRS using the [CRS menu](/lidarmill-desktop/workflow-kk/project-setup.md).

* **File Version** 
  * Select output file version 1.2 or 1.4
* **File Type**
  * Select output file as an uncompressed LAS or compressed LAZ
* Options (Optional)
  * Only write Colorized points
  * Only write single-return points
  * Create one file per processing interval 
* Use grid for tiling (Optional)
  * Select [grid](https://docs.phoenixlidar.com/lidarmill-desktop/user-interface/windows/project-management-window/grid#creating-a-grid-for-tiled-pointcloud-export) to be used for tiled pointcloud output
* **User Data**
  * Deviation - Riegl scanners only
  * Index of Interval starting at 0
  * Index of Interval starting at 1, with all curves set to 0
  * Index of LaserHead - Multilaser Scanners only
  * Range (using scalefactor) - Requires user specified scale factor
  * Zero
* **Time Format**
  * GPS Microseconds
  * GPS Standard Time
  * GPS Standard Time (Adjusted)
  * No Time / Zero
  * Seconds in UTC day
  * Time of Week (seconds)
* **Point Source ID**
  * Amplitude - Riegl scanners only
  * Deviation - Riegl scanners only
  * Index of Interval starting at 0
  * Index of Interval starting at 1, with all curves set to 0
    * Recommend to be used with Phoenix LiDAR Terrasolid workflow
  * Index of LaserHead - Multilaser Scanners only
  * Range in centimeters
  * Zero 
* **Classes to Export**
* Extra Bytes (Optional) - only compatible with version 1.4 output
  * store distance, amplitude, deviation, normalized height, sensor id, and laser id information
* Manual Point Offset (Optional)
  * Specify an additional manual offset to be applied to the selected transformation
  * Input Boxes for X, Y, Z
* Trajectories (Optional)
  * Write Trajectories as LAS files
  * PointSource-ID
* [Report](https://docs.phoenixlidar.com/lidarmill-desktop/post-processing/workflow-kk/export-cloud/reports#create-reports) (Optional)
  * [Write Project Report](https://docs.phoenixlidar.com/lidarmill-desktop/user-interface/toolbars/trajectory-cloud-reporting#save-report-tool)

Once all parameters are configured click **OK** and SpatialExplorer will begin exporting the CLOUD file to LAS/LAZ.