Add Files To LAS Dataset (Data Management Tools)

Summary

Adds one or more LAS format files and surface constraint features to an existing LAS dataset.

Usage

The LAS dataset provides a way to visualize, manage, and analyze collections of point cloud data stored in uncompressed LAS files (*.las) and compressed variants (*.zlas and *.laz). The LAS dataset references the input files where they reside and supports working with a large collection of separate files through a single access point that can optimize the rendering experience. Compressed files typically use approximately 30 percent of the storage size of uncompressed files, making them a suitable alternative for managing large collections of data and archival storage. You can edit the class codes of uncompressed .las files and .zlas files. When considering which file format to use, evaluate the formats by the applications in which they will be used.

Learn more about the data types supported by the LAS dataset

ZLAS files can be created with any tool that creates .las files, including: Convert LAS, Extract LAS, Thin LAS, Tile LAS, and Project LAS. LAZ files can be created with the Convert LAS tool.
Surface constraint features can be used to enforce feature-derived elevation values that represent surface characteristics in the LAS dataset.
The class code labels provided in the LAS dataset's layer and catalog properties reflect the class designations outlined in the ASPRS LAS 1.4 specifications. This classification scheme is oriented for aerial lidar surveys and is comprised of the following:
- Classes associated with predefined objects, for example, 2 represents ground
- Classes whose values are not defined but reserved for later use by the ASPRS
- Classes that can be allocated to any other object
The LAS dataset layer's point filters, interactive editing options, and default symbology labels reflect the LAS format specification's class code labels.

Learn more about lidar point classification.
Each LAS file (*.las, *.zlas, or .laz) that will be added to the LAS dataset is examined to determine if its file structure meets the ASPRS LAS format specifications. Files that are improperly created or corrupted will fail to load. If this occurs, use the Esri CheckLAS application to evaluate the file.
The ASPRS specifications for a .las file require the file to have spatial reference information. If this information is missing or improperly defined, the file will have an unknown spatial reference, which will cause it to render in the coordinate system of the map. If the correct spatial reference is known, use the Define Projection tool or the Create LAS Dataset tool with the Create PRJ For LAS Files set to All LAS File or Files with Missing Spatial References.

Learn more about how LAS coordinate system information is stored and modified
The class code labels provided in the LAS dataset's layer and catalog properties reflect the class designations outlined in the ASPRS LAS 1.4 specifications. This classification scheme is oriented for aerial lidar surveys and is comprised of the following:
- Classes associated with predefined objects, for example, 2 represents ground
- Classes whose values are not defined but reserved for later use by the ASPRS
- Classes that can be allocated to any other object
The LAS dataset layer's point filters, interactive editing options, and default symbology labels reflect the LAS format specification's class code labels.

Learn more about lidar point classification.
If the LAS standard is applicable for the data but the class codes do not conform, consider modifying the class designations to match the ASPRS LAS 1.4 standards to ensure that the data will be interpreted in a consistent manner. Since LAS format 1.0 files did not require any classification standard, data vendors may have applied classification codes to objects that did not match the standard that was introduced in the more recent LAS formats. If the class code values in the data are not consistent with the LAS standard, use the Change LAS Class Codes tool to align the value with the latest ASPRS classification scheme.

Label	Explanation	Data type
Input LAS Dataset	The LAS dataset that will be processed.	LAS Dataset Layer
LAS Files or Folders (Optional)	The LAS format files (`.las`, `.zlas`, and `.laz`) that will be added to the input LAS dataset. A folder can be specified to add all supported files in the directory. Likewise, another LAS dataset can be provided to add all of its files with valid paths. In the Geoprocessing pane, a folder can also be specified as an input by selecting the folder in File Explorer and dragging it onto the parameter's input box.	LAS Dataset Layer; Folder; File
Include subfolders (Optional)	Specifies whether LAS format files (`.las`, `.zlas`, and `.laz`) residing in the subdirectories of an input folder will be added to the LAS dataset. Checked—All LAS format files residing in the subdirectories of an input folder will be added to the LAS dataset. Unchecked—Only LAS format files residing in an input folder will be added to the LAS dataset. This is the default.	Boolean
Surface Constraints (Optional)	The features that will contribute to the definition of the triangulated surface generated from the LAS dataset. Input Features—The features with geometry that will be incorporated into the LAS dataset's triangulated surface. Height Field—The feature's elevation source can be derived from any numeric field in the feature's attribute table or the geometry by selecting `Shape.Z`. If no height is necessary, specify the keyword `<None>` to create z-less features with elevation that will be interpolated from the surface. Type—Defines the feature's role in the triangulated surface generated from the LAS dataset. Options with hard or soft designation refer to whether the feature edges represent distinct breaks in slope or a gradual change. Surface Feature Type—The surface feature type that defines how the feature geometry will be incorporated into the triangulation for the surface. Options with hard or soft designation refer to whether the feature edges represent distinct breaks in slope or a gradual change. anchorpoints—Elevation points that will not be thinned away. This option is only available for single-point feature geometry. hardline or softline—Breaklines that enforce a height value. hardclip or softclip—Polygon dataset that defines the boundary of the LAS dataset. harderase or softerase—Polygon dataset that defines holes in the LAS dataset. hardreplace or softreplace—Polygon dataset that defines areas of constant height. Value table columns: Input Features—The feature to be referenced by the LAS dataset. Height Field—The feature's elevation source can be derived from any numeric field in the feature's attribute table or the geometry by selecting Shape.Z. Type—Defines the feature's role in the triangulated surface generated from the LAS dataset.	Value Table

Derived output

Label	Explanation	Data type
Updated Input LAS Dataset	The updated LAS dataset.	LAS Dataset Layer

arcpy.management.AddFilesToLasDataset(in_las_dataset, {in_files}, {folder_recursion}, {in_surface_constraints})

Name	Explanation	Data type
in_las_dataset	The LAS dataset that will be processed.	LAS Dataset Layer
in_files [in_files,...] (Optional)	The LAS format files (`.las`, `.zlas`, and `.laz`) that will be added to the input LAS dataset. A folder can be specified to add all supported files in the directory. Likewise, another LAS dataset can be provided to add all of its files with valid paths. In the Geoprocessing pane, a folder can also be specified as an input by selecting the folder in File Explorer and dragging it onto the parameter's input box.	LAS Dataset Layer; Folder; File
folder_recursion (Optional)	Specifies whether LAS format files (`.las`, `.zlas`, and `.laz`) residing in the subdirectories of an input folder will be added to the LAS dataset. `RECURSION`—All LAS format files residing in the subdirectories of an input folder will be added to the LAS dataset. `NO_RECURSION`—Only LAS format files residing in an input folder will be added to the LAS dataset. This is the default.	Boolean
in_surface_constraints [[in_feature_class, height_field, SF_type],...] (Optional)	The features that will be referenced by the LAS dataset when generating a triangulated surface. Each feature must have the following properties defined: `in_feature_class`—The feature to be referenced by the LAS dataset. `height_field`—Any numeric field in the feature's attribute table can be used to define the height source. If the feature's geometry contains z-values, it can be selected by specifying `Shape.Z`. If no height is necessary, specify the keyword `<None>` to create z-less features with elevation that will be interpolated from the surface. `SF_type`—The surface feature type that defines how the feature geometry will be incorporated into the triangulation for the surface. Options with hard or soft designation refer to whether the feature edges represent distinct breaks in slope or a gradual change. `anchorpoints`—Elevation points that will not be thinned away. This option is only available for single-point feature geometry. `hardline` or `softline`—Breaklines that enforce a height value. `hardclip` or `softclip`—Polygon dataset that defines the boundary of the LAS dataset. `harderase` or `softerase`—Polygon dataset that defines holes in the LAS dataset. `hardreplace` or `softreplace`—Polygon dataset that defines areas of constant height. Value table columns: `Input Features`—The feature to be referenced by the LAS dataset. `Height Field`—The feature's elevation source can be derived from any numeric field in the feature's attribute table or the geometry by selecting Shape.Z. `Type`—Defines the feature's role in the triangulated surface generated from the LAS dataset.	Value Table

Derived output

Name	Explanation	Data type
derived_las_dataset	The updated LAS dataset.	LAS Dataset Layer

Code sample

AddFilesToLasDataset example 1 (Python window)

The following sample demonstrates the use of this tool in the Python window:

import arcpy
from arcpy import env

env.workspace = "C:/data"
arcpy.management.AddFilesToLasDataset("test.lasd",
                                      ["LA_N", "LA_S/LA_5S4E.las"],
                                      "RECURSION",
                                      ["boundary.shp <None> Soft_Clip",
                                       "breakline.shp Shape.Z Hard_Line"])

AddFilesToLasDataset example 2 (stand-alone script)

The following sample demonstrates the use of this tool in a stand-alone Python script:

'''*********************************************************************
Name: Modify Files in LAS Dataset& Calculate Stats for LASD
Description: Adds files & surface constraints to a LAS dataset, then
             calculates statistics and generates report.
*********************************************************************'''
# Import system modules
import arcpy

try:
    # Script variables
    arcpy.env.workspace = 'C:/data'
    lasd = 'sample.lasd'
    oldLas = ['2006', '2007/file2.las']
    newLas = ['2007_updates_1', '2007_updates_2']
    oldSurfaceConstraints = ['boundary.shp', 'streams.shp']
    newSurfaceConstraints = [['sample.gdb/boundary', '<None>',
                              'Soft_Clip']
                             ['sample.gdb/streams', 'Shape.Z',
                              'Hard_Line']]
    arcpy.management.RemoveFilesFromLasDataset(lasd, oldLas,
                                               oldSurfaceConstraints)
    arcpy.management.AddFilesToLasDataset(lasd, newLas, 'RECURSION',
                                          newSurfaceConstraints)
    arcpy.management.LasDatasetStatistics(lasd, "UPDATED_FILES",
                                          "lasd_stats.txt",
                                          "LAS_FILE", "DECIMAL_POINT",
                                          "SPACE", "LAS_summary.txt")
except arcpy.ExecuteError:
    print(arcpy.GetMessages())
except Exception as err:
    print(err.args[0])

Environments

Current Workspace, Scratch Workspace

Licensing information

Basic: Requires 3D Analyst or Spatial Analyst
Standard: Yes
Advanced: Yes

Add Files To LAS Dataset (Data Management Tools)

Summary

Usage

Parameters

Derived output

Environments

Licensing information

Related topics