Skip to main content

Tile LAS (3D Analyst Tools)

Summary

Creates a set of nonoverlapping LAS files whose horizontal extents are divided by a regular grid.

Usage

  • The tiling operation will retain all points that are within the processing extent of the LAS dataset being tiled regardless of any layer filter settings that may be applied. If filtering is needed, consider using the Extract LAS tool either before or after tiling the LAS dataset.

  • Subdividing large LAS files that exceed 500 MB in size will improve the performance of any operation that relies on reading the data in spatial clusters, such as analysis operations that require the creation of a surface, or data visualization operations. The default tiling scheme produces square tiles whose width and height is defined by a target size limit of 250 MB. Points from multiple LAS files that fall within the area of one tile will be merged into the output tile.

  • A LAS dataset composed of LAS files with overlapping extents may yield inaccurate results in operations that rely on a file-by-file analysis. For example, the point spacing estimate is derived by an analysis of the points at each file over the area of coverage within that file and, consequently, has no mechanism for adjusting to the impact of points in the overlapping regions. Likewise, the Thin LAS tool also relies on file-by-file processing, and the result will not conform to the expected output in the regions where file overlaps exist.

  • Rearranging the LAS points will spatially cluster the lidar data and improve its performance when visualizing or performing analysis operations. This process will require the creation of a temporary file. Consider specifying a folder on a solid-state drive as the Scratch Workspace value in the environment settings to improve the speed of this operation.

  • You can write the output files with the zLAS compression to reduce storage size. The zLAS compression typically reduces file size to one-third of the uncompressed LAS file, and zLAS files support edits to the point classification codes and flags.

  • You can define LAS tiles by doing one of the following:

    • Specify the width and height of each tile.

    • Specify a target file size for each output LAS file. This file size is used to estimate the tile width and height based on the average point spacing and the amount of bytes required to store each point with its associated attributes. The derived width and height is based on the assumption that the LAS points are regularly distributed across the entire data extent. When the output is a zLAS file, this file size will be its uncompressed size.

    • Specify polygon features that define the tiling schema. Each polygon should be rectangular and have a uniform width and height. If the polygon is not rectangular, its minimum bounding envelope will be used to establish the tiling schema. The Create Fishnet or Generate Tessellation tool can be used to create tiled polygons which match the extent of the LAS data. Custom LAS tile base names can be assigned using a text field in the polygon's attribute table.

  • The output LAS tiles can be reprojected by either specifying an Output Coordinate System value in the environment settings or using input features with a different spatial reference than the original LAS files. A z-datum transformation can be accomplished by specifying the required transformation through the Transformation window. Z-datum transformations require the installation of vertical datum transformation grids.

  • This tool can be used to merge LAS points distributed across many files into one file by specifying a tile size that is larger than the extent of the input files.

Parameters

Label Explanation Data type

Input LAS Dataset

The LAS dataset that will be processed.

LAS Dataset Layer

Target Folder

The folder where the tiled LAS files will be written.

Folder

Output Base Name

(Optional)

The name that each output file will begin with.

String

Output LAS Dataset

(Optional)

The new LAS dataset that references the tiled LAS files created by this tool. This parameter is optional.

LAS Dataset

Compute statistics

(Optional)

Specifies whether statistics will be computed for the .las files referenced by the LAS dataset. Computing statistics provides a spatial index for each .las file, which improves analysis and display performance. Statistics also enhance the filtering and symbology experience by limiting the display of LAS attributes, such as classification codes and return information, to values that are present in the .las file.

  • Checked—Statistics will be computed. This is the default.

  • Unchecked—Statistics will not be computed.

Boolean

Output Version

(Optional)

Specifies the LAS file version of each output file.

  • 1.0—The LAS file version will be 1.0. This version supported 256 unique class codes but did not have a predefined classification schema.

  • 1.1—The LAS file version will be 1.1. This version introduced a predefined classification scheme, and point record formats 0 and 1, and the synthetic classification flag for points that were derived from a source other than a lidar sensor.

  • 1.2—The LAS file version will be 1.2. This version featured support for GPS time and RGB records in point records 2 and 3.

  • 1.3—The LAS file version will be 1.3. This version added support for point records 4 and 5 for waveform data. However, waveform information is not read in ArcGIS. This is the default.

  • 1.4—The LAS file version will be 1.4. This version introduced point record formats 6 through 10, along with new class definitions, 256 unique class codes, and the overlap classification flag.

String

Point Format

(Optional)

The point record format of the output LAS files. The available options will vary based on the LAS file version specified in the Output Version parameter.

Long

Compression

(Optional)

Specifies whether the output LAS file will be in a compressed format or the standard LAS format.

  • No Compression—The output will be in the standard LAS format (*.las file). This is the default.

  • zLAS Compression—Output LAS files will be compressed in the zLAS format.

String

LAS Options

(Optional)

Specifies modifications that will be made to the output LAS files.

  • Rearrange Points—LAS points will be arranged according to their spatial clustering.

  • Remove Variable Length Records—Variable-length records that are added after the header and the point records of each file will be removed.

  • Remove Extra Bytes—Extra bytes that are present with each point record in the input LAS file will be removed.

String

Import from Feature Class

(Optional)

The polygon features that define the tile width and height to be used when tiling the lidar data. The polygons are presumed to be rectangular, and the first feature's extent is used to define the tile width and height.

Feature Layer

Naming Method

(Optional)

Specifies the naming convention that will be used to provide a unique name for the output files. This name will be appended to the text specified in the Output Base Name parameter. When input features are used to define the tiling scheme, its text fields can also be used to provide a unique name for the output files.

  • XY Coordinates—Each tile name will be appended with the x- and y-coordinates of its lower left corner in the format "<base name><x-coordinate><y-coordinate>". This is the default.

  • Rows and Columns—The tile name will be assigned based on the row and column it belongs to in the overall tiling scheme. The rows increment from the bottom up, while the columns increment from left to right. The name will be in the format "<base name><row number><column number>".

  • Ordinal Designation—The tile name will be assigned based on its order of creation starting from the bottom left and incrementing to the top right. The name will be in the format "<base name>_<order number>". The number of leading zeros in the order number will be based on the maximum number of files that is created.

String

Target File Size (MB)

(Optional)

A value, which is expressed in megabytes, that represents the upper limit of the uncompressed file size of an output LAS tile with uniform point distribution across its entire extent. The default is 250, and the value is used to estimate the tile width and height.

The value of this parameter will change when the Tile Width and Tile Height parameters are modified. When the Import from Feature Class parameter is specified, this parameter will be disabled.

Double

Tile Width

(Optional)

The width of each tile. This parameter is disabled when the Import from Feature Class parameter is specified. If the tile width and height are both provided, the Target File Size (MB) parameter will be updated to reflect the size of the output that would be generated with these dimensions. Similarly, if the Target File Size (MB) parameter is modified, the tile width and height get updated to reflect this change.

Linear Unit

Tile Height

(Optional)

The height of each tile. This parameter is disabled when the Import from Feature Class parameter is specified. If the tile width and height are both provided, the Target File Size (MB) parameter will be updated to reflect the size of the output that would be generated with these dimensions. Similarly, if the Target File Size (MB) parameter is modified, the tile width and height get updated to reflect this change.

Linear Unit

Tile Origin

(Optional)

The coordinates of the origin of the tiling grid. The default values are obtained from the lower left corner of the input LAS dataset. This parameter is disabled when input features are specified for the Import from Feature Class parameter.

Point

Derived output

Label Explanation Data type

Output Folder

The folder that the output LAS files will be written to.

Folder

Environments

Current Workspace, Scratch Workspace, Extent, Output Coordinate System, Geographic Transformations

Licensing information

  • Basic: Requires 3D Analyst
  • Standard: Requires 3D Analyst
  • Advanced: Requires 3D Analyst