# Export Cloud to LAS The “Export to LAS” option allows you to configure the various parameters associated with exporting the data in your Project into common mapping formats such as LAS or LAZ. {% hint style="success" %} You must first create a .cloud file in SpatialExplorer 5.0.X before exporting to LAS {% endhint %} {% tabs %} {% tab title="SpatialExplorer v5.0.X" %} ![Export Cloud to LAS button in SpatialExplorer v5.0.X](/files/-M78juQAJ2rC9dPMNVjE) {% endtab %} {% tab title="SpatialExplorer v4.0.X" %} ![Export Project to LAS option in SpatialExplorer 4.0.X](/files/-M78jqoEb1z9x-UrTRbG) {% endtab %} {% endtabs %} After adding and inspecting the loaded data, SpatialExplorer is ready to fuse the data into a common mapping format file with the selected options. This can be initiated anytime by clicking on the OK radio button. ![](/files/-M78kTJmbb02W-Pnt6mQ) ## Data to Export (Interval to Fuse) This option determines which portions of the loaded trajectory will be exported to a LAS/LAZ file. The default option for this parameter is “All Data.” This will fuse the entire trajectory to the LAS/LAZ file and it will be the only option if you have chosen NOT to autosplit the trajectory. Otherwise, if you have autosplit the trajectory you will be able to choose between fusing everything or just the portions of the trajectory that were autosplit. Refer to [Autosplit Trajectory](/spatialexplorer/work-offline/workflow/navigation/autosplit-trajectory.md) for more information. {% tabs %} {% tab title="SpatialExplorer v5.0.X" %} ![Choose data to export based on intervals](/files/-M78kvzgZRKABZMDAnwW) {% endtab %} {% tab title="SpatialExplorer v4.0.X" %} ![Choose data to export based on intervals](/files/-M78lPid2iTRjUNZN0Cc) {% endtab %} {% endtabs %} ## Output Coordinate System When you add a trajectory file to SpatialExplorer, it will automatically determine the correct coordinate system as defined by the loaded trajectory. ![SpatialExplorer Autodetected Output Coordinate System indicator](/files/-LTP1l_dMfbopU-ZPj3W) However, if you want to change the output coordinate system you can do so from within SpatialExplorer by selecting the “Custom:” radio button and clicking the “...” radio button located to the right of the Custom Output Coordinate System indicator. ![SpatialExplorer Custom Output Coordinate System indicator](/files/-LTP1tKUUcxVPkQU7vje) From the Select Coordinate Reference System window, you can search for a Coordinate System or you can select a Coordinate System from the available list. ![SpatialExplorer Select Custom Coordinate Reference System options](/files/-LTP1z_-ddPiOVhYkTEx) ### Utilizing Geoid Models in SpatialExplorer {% embed url="" %} ## File Version & File Type SpatialExplorer will fuse and export to a LAS or a LAZ file. A LAS file is an industry-standard binary format for storing lidar data. An LAZ file is simply a compressed version of a LAS file. As of this writing, LAS 1.2 (PointType 0, 1, 2, 3) and LAS 1.4 (PointType 6, 7, 8) are supported in SpatialExplorer 3.5 and above. However, LAZ is not compatible with LAS 1.4. ![SpatialExplorer File Version and File Type options](/files/-LTP6PaboYbD1GCgBvp3) ## Options These are additional options that apply to the LAS/LAZ file created during the fusing process. ![](/files/-M78mRFgJcA9KMbwhc6D) | | | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Only write colorized points | This option will create a LAS/LAZ file consisting only of RGB colorized points. | | Only write single-return points | This option will create a LAS/LAZ file consisting only of points with single returns. | | Create one file per processing interval | This option will create individual LAS/LAZ files per processing interval. Requires selecting two or more separate processing intervals. | | Fill UserData with Laser ID | This option will store the Laser ID of each point in the User Data field of the Point Data Record portion of the LAS/LAZ file | | Store each point’s range using scaling factor | This option will store the range of each point in the User Data field of the Point Data Record portion of the LAS/LAZ file. It is used to scale the corresponding X, Y, and Z long values within the point record. | ## Time Format When you create a LAS/LAZ file, you must specify the GPS time storage format for the data you wish to fuse in SpatialExplorer. The selected time format is used for all entities and layers within the exported LAS/LAZ file. ![SpatialExplorer Export to LAS Time Format options](/files/-LTPB3FARsbiaBaXYnbV) | | | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | No Time | This option will apply no time value to the exported LAS/LAZ file. | | GPS Standard Time | GPS standard time + 1,000,000,000, is the unadjusted GPS standard time (continuously counting from Jan 6, 1980.) | | GPS Standard Time (Adjusted) | Defined by the LAS standard as the Adjusted Standard Time, (satellite GPS Time minus 1 x 10^9), smaller than one 1,000,000,000. | | Time of Week (seconds) | Time stamps are between 0 and 604800, where the clock resets at midnight Saturday night to Sunday morning. | {% hint style="info" %} If you are going to be post-processing the LAS/LAZ file in TerraSolid, you must ensure the Time Format selected is Time of Week (seconds). Seconds of the week allows easily matching the point cloud records with the time in the SBET when calibrating in TerraSolid. This allows connecting the point cloud with the trajectory based on time. {% endhint %} ## Point Source ID The Point Source ID option allows you to associate each point in a cloud with its corresponding laser of origin. Much like each the X, Y, and Z coordinate values or the R/G/B values, the Point Source ID is a property of every point in a LAS/LAZ file. When you create a LAS/LAZ file from a multi-laser LiDAR sensor (e.g. Velodyne VLP-16, Velodyne HDL-32E) and you inspect a single point, you will not be able to identify which specific laser created that specific point. However, if you associate the ID number of each laser (e.g. 0-15 for the Velodyne VLP-16 or 0-31 for the Velodyne HDL-32E) into the Point Source ID of each point, then you will be able to identify which specific laser created each point. This option is useful during post-processing after exporting to LAS/LAZ with SpatialExplorer; it allows the calibration of every laser in a multi-laser LiDAR sensor. ![SpatialExplorer Point Source ID options](/files/-LTPCxQOHPs-vRQJmfLs) When setting the Point Source ID, there are several options to choose from. The following table describes the available Point Source ID options. | | | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Zero | Sets the Point Source ID value of all points to 0. A Point Source ID of zero implies the points originated in this file at some time during processing. | | Index of Laser Head (Multilaser) | Sets the Point Source ID to match the index as indicated by the layout of the lasers in the LiDAR sensor. | | Index of Laser Log | Associates the Point Source ID values based on individual LiDAR log files. The Point Source ID value will begin with index 0 with every new LIDAR file generated. | | Index of Interval starting at 0 | Sets the Point Source ID value to match the index as indicated by the corresponding flight intervals (e.g. 0, 1, 2, 3, etc.) | | Index of Interval starting at 1, with all curves set to 0 | Sets the Point Source ID value to match the index to 1 as indicated by the corresponding flight intervals, while setting the index of all points acquired in curves to 0 (e.g. 1, 0, 2, 0, 3, 0, etc.) | | Deviation (Riegl) | Sets the Point Source ID to use the pulse shape of the echo signal which is compared to the pulse shape representing the system response.The pulse shape deviation can be interpreted as the comparison of the area below the shape curve. | | Amplitude (Riegl) | Sets the Point Source ID to use the amplitude of the echo signal reaching the laser scanner. The value of the amplitude reading is a ratio, given in the units of decibel (dB). | ## Classes to Export If you've classified your point cloud, you can choose to export only certain defined classes. Refer to [Classification](/spatialexplorer/work-offline/workflow/create-a-cloud/filtering.md) for more information. ![SpatialExplorer Classes to Export option](/files/-M78nL_SJkDMm2eAQWhj) ## Manual Point Offset The three fields for the Manual Point Offset option in SpatialExplorer are ordered as X, Y, and Z. This option will allow you to offset your point cloud based on your GNSS reference station new surveyed coordinates. You must calculate the difference in distance and enter it as meters or whichever units your Output Coordinate System uses. ![SpatialExplorer Manual Point Offset option](/files/-LTPDtGZQNHIChss3-8r) --- # Agent Instructions: 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: ``` GET https://docs-6.phoenixlidar.com/spatialexplorer/work-offline/workflow/export-project-to-las.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.