Data types supported by a LAS dataset

The main data sources for LAS datasets are lidar data stored in LAS format files (*.las, *.zlas, and *.laz), and surface constraints stored in feature classes. zLAS and LAZ files are compressed versions of LAS files.

Lidar and point cloud data

General characteristics of point clouds include the following:

  • Lidar (light detection and ranging) point clouds stored in .las file format
  • Not surface specific
  • Sampled to required nominal point spacing, varying from 1 to 15 feet (approximately 0.3 to 5 meters) depending on application
  • Every point contains attributes that are stored with the x,y,z data
  • Large quantities of point data
  • Photogrammetric point cloud data stored in .las files

Compressed lidar formats

Two compressed lidar formats are supported in ArcGIS Pro: *.zlas and *.laz files. They are both losslessly compressed version of a LAS file. Compressed lidar formats are optimized versions of LAS files, which is useful for archiving, sharing, and direct use in ArcGIS Pro. Compressed lidar formats files are much smaller and more efficient to use, especially on the cloud and over networks, than regular LAS.

General characteristics for ZLAS format include the following:

  • You can add *.zlas files to a LAS dataset using the LAS dataset properties dialog and LAS dataset creation tools.
  • You can see individual *.zlas files in the Catalog pane, and drag and drop them into a map or scene in ArcGIS Pro.
  • You can calculate statistics for a LAS dataset referencing *.zlas files to understand what class codes and other attributes that are available in the *.zlas files.
  • A spatial index is made for a LAS dataset referencing *.zlas files when statistics are calculated. A LAS auxiliary file *.lasx is created along side the *.zlas files to improve overall performance.
  • A pyramid can be built for a LAS dataset referencing *.zlas files.
  • You can run geoprocessing tools to create derivative products from a LAS dataset referencing a *.zlas files or on individual *.zlas files.
  • You can edit class codes and class flags from a LAS dataset referencing *.zlas files or on individual *.zlas files.

General characteristics for LAZ format include the following:

  • You can add *.laz files to a LAS dataset using the LAS dataset properties dialog box and LAS dataset creation tools.
  • You cannot see individual *.laz files in the Catalog pane, nor can you drag them to a map or scene in ArcGIS Pro. They must added to a LAS dataset to be used in ArcGIS Pro.
  • You can calculate statistics for a LAS dataset referencing *.laz files to understand what class codes and other attributes that are available in the *.laz files.
  • A spatial index is not supported for *.laz files.
  • A pyramid can be built for a LAS dataset referencing *.laz files. Building a pyramid is important since there is no spatial index support for *.laz.
  • You can run geoprocessing tools to create derivative products from a LAS dataset referencing a *.laz file. Overall performance might not be as good as *.zlas or *.las files. It is recommended to keep *.laz tiles small to improve performance.
  • You can not edit class codes and class flags from a LAS dataset referencing *.laz files.

Surface constraints

Surface constraints are surface features stored in geodatabase feature classes, which are usually derived from a remote sensing technique such as photogrammetry.

Characteristics of photogrammetrically derived breaklines include the following:

  • Surface-specific breaks in slope along linear features
  • Natural landforms (for example, ridges and valleys)
  • Terrain features resulting from earthworks (for example, bulldozed)
  • Lake shorelines, creeks, or river shorelines
  • Edge of road pavement
  • Delineation of void areas (typically obscured by vegetation)
  • Minimal attribution
  • Typically moderate quantities

Characteristics of GPS points include the following:

  • Irregularly spaced
  • May or may not represent surface-specific peaks and pits
  • Used for control, QA, and benchmarking other data
  • Property boundary control points
  • Potentially significant attribution per point
  • Typically small quantities

The following table describes the types of surface constraints that can be used.

Surface constraint typeFeature class Z-value source in the feature class Example data

Points (x,y,z locations)

Point feature class

Can be either of the following:

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value per shape
  • Spot heights
  • Survey points
  • GPS points

Polygon feature class

  • Shape geometry; x,y,z per vertex

or

  • Attribute column containing one z-value per shape

Shoreline delineation

Breaklines (hard or soft)

Line feature class

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value per shape
  • No height source; z-values interpolated for each feature from the surface before being added
  • Contours
  • Edge of pavement
  • Water lines (streams, rivers, canals, and shorelines)

Polygon feature class

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value per shape (such as a shoreline)
  • No height source; z-values interpolated for each feature from the surface before being added

Lake shoreline

Clipping polygons (hard or soft)

Polygon feature class

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value per shape (such as a shoreline)
  • No height source; z-values interpolated for each feature from the surface before being added

Study area boundary

Erase polygons (hard or soft)

Polygon feature class

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value per shape
  • No height source; z-values interpolated for each feature from the surface before being added
  • Lake shoreline
  • Obscured areas (dense forest canopy)

Replace polygons (hard or soft)

Polygon feature class

  • Shape geometry; x,y,z per vertex
  • Attribute column containing one z-value for all vertices in each shape

Water bodies