Back to Top

Create Point Cloud Scene Layer Content (Data Management)

In this topic

  1. Summary
  2. Usage
  3. Parameters
  4. Environments
  5. Licensing information

Summary

Creates a point cloud scene layer package (.slpk) or scene layer content (.i3sREST) in the cloud from LAS, zLAS, LAZ, or LAS dataset input.

Usage

  • The output coordinate system should match the coordinate system of the web scene in which it will be displayed. If the intended display environment will be a global web scene view, the output coordinate system must use GCS WGS 84 or China Geodetic Coordinate System 2000. A vertical coordinate system for a global scene must be ellipsoidal, EGM2008 Geoid, or EGM96 Geoid.

  • All .las, .zlas, or .laz files being processed must have the same spatial reference. If multiple spatial references are used by the input collection of .las or .zlas files, consider using the Extract LAS tool to reproject the data to a common spatial reference. Datasets with an unknown coordinate system will be blocked as input to the tool.

  • A .las, .zlas, or .laz file can have its spatial reference defined in its header or by a .prj file with the same base name that is placed in the same location. The .prj file will override the information in the header and can be used to correct missing or invalid spatial reference information. If all of the .las, .zlas, or .laz files being processed have unknown coordinates but use the same spatial reference, only one file will need a .prj file defined for the tool to process the collection. You can generate a .prj file using the Create LAS Dataset tool.

  • .laz files with missing coordinate system information can be defined through the Input Coordinate System parameter.

  • Use the Target Cloud Connection parameter to output scene layer content to an object store located in the cloud such as Amazon S3, Azure Blob storage, Alibaba OSS, or Google Cloud. This content can be published as a scene service and the location you choose must be registered as a user-managed data store in ArcGIS Enterprise.

  • You can build a connection file (.acs) using the Create Cloud Storage Connection File tool.

Parameters

DialogPython

LabelExplanationData Type
Input Dataset

The lidar data (LAS, zLAS, LAZ, or LAS dataset) that will be used to create a scene layer package. The lidar data can also be specified by selecting the parent folder that contains the files.

Layer File; LAS Dataset Layer; Folder; File
Output Scene Layer Package
(Optional)

The output scene layer package (.slpk).

File
Output Coordinate System
(Optional)

The coordinate system of the output scene layer package. It can be any projected or custom coordinate system. Supported geographic coordinate systems include WGS84 and China Geodetic Coordinate System 2000. WGS84 and EGM96 Geoid are the default horizontal and vertical coordinate systems, respectively. The coordinate system can be specified in any of the following ways:

  • Specify the path to a .prj file.
  • Reference a dataset with the correct coordinate system.
  • Use an arcpy.SpatialReference object.

Spatial Reference
Geographic Transformation
(Optional)

The datum transformation method that will be used when the input layer's coordinate system uses a datum that differs from the output coordinate system. All transformations are bidirectional, regardless of the direction implied by their names. For example, NAD_1927_to_WGS_1984_3 will work correctly even if the datum conversion is from WGS 1984 to NAD 1927.

Note:

ArcGIS coordinate system data is required for vertical datum transformations between ellipsoidal and gravity-related and two gravity-related datums.

String
Attributes to cache
(Optional)

Specifies the source data attributes that will be included in the scene layer package. These values will be accessible when the content is consumed in other viewers. Select attributes that are required for the desired rendering and filtering options (for example, intensity, returns, class codes, RGB). To reduce storage, exclude unneeded attributes.

  • Intensity— The return strength of the laser pulse for each lidar point will be included.
  • RGB—RGB imagery information collected for each lidar point will be included.
  • LAS flags—Classification and scan direction flags will be included.
  • Classification code—Classification code values will be included.
  • Return value—Discrete return numbers from the lidar pulse will be included
  • User data—A customizable attribute that can be any number in the range of 0 through 255 will be included.
  • Point source ID—For aerial lidar, this value typically identifies the flight path that collected a given lidar point, which will be included.
  • GPS time— The GPS time stamp at which the laser point was emitted from the aircraft will be included. The time is in GPS seconds of the week in which the time stamp is between 0 and 604800 and resets at midnight on a Sunday.
  • Scan angle—The angular direction of the laser scanner for a given lidar point will be included. The value range is from -90 through 90.
  • Near infrared—Near infrared records collected for each lidar point will be included.
String
Point Size (m)
(Optional)

The point size of the lidar data. For airborne lidar data, the default of 0 or a value close to the average point spacing is usually best. For terrestrial lidar data, the point size should match the desired point spacing for the areas of interest. Values are expressed in meters. The default of 0 will automatically determine the best value for the input dataset.

Double
XY Max Error (m)
(Optional)

The maximum x,y error tolerated. A higher tolerance will result in better data compression and more efficient data transfer. Values are expressed in meters. The default is 0.001.

Double
Z Max Error (m)
(Optional)

The maximum z-error tolerated. A higher tolerance will result in better data compression and more efficient data transfer. Values are expressed in meters. The default is 0.001.

Double
Input Coordinate System
(Optional)

The coordinate system of the input .laz files. This parameter is only used for .laz files that do not contain spatial reference information in their header or have a .prj file in the same location.

Coordinate System
Scene Layer Version
(Optional)

The Indexed 3D Scene Layer (I3S) version of the resulting point cloud scene layer package. Specifying a version supports backward compatibility and allows scene layer packages to be shared with earlier versions of ArcGIS.

  • 1.x—The point cloud scene layer package will be supported in all ArcGIS clients.
  • 2.x—The point cloud scene layer package will be supported in AllSource 2.1.2 or later and can be published to ArcGIS Online and ArcGIS 10.6.1 or later. This is the default.
String
Target Cloud Connection
(Optional)

The target cloud connection file (.acs) where the scene layer content (.i3sREST) will be output.

Folder
Output Name
(Optional)

The output name of the scene layer content when output to a cloud store. This parameter is only available when a Target Cloud Connection parameter value is specified.

String

arcpy.management.CreatePointCloudSceneLayerPackage(in_dataset, {out_slpk}, {out_coor_system}, {transform_method}, {attributes}, {point_size_m}, {xy_max_error_m}, {z_max_error_m}, {in_coor_system}, {scene_layer_version}, {target_cloud_connection}, {out_name})
NameExplanationData Type
in_dataset

The lidar data (LAS, zLAS, LAZ, or LAS dataset) that will be used to create a scene layer package. The lidar data can also be specified by selecting the parent folder that contains the files.

Layer File; LAS Dataset Layer; Folder; File
out_slpk
(Optional)

The output scene layer package (.slpk).

File
out_coor_system
(Optional)

The coordinate system of the output scene layer package. It can be any projected or custom coordinate system. Supported geographic coordinate systems include WGS84 and China Geodetic Coordinate System 2000. WGS84 and EGM96 Geoid are the default horizontal and vertical coordinate systems, respectively. The coordinate system can be specified in any of the following ways:

  • Specify the path to a .prj file.
  • Reference a dataset with the correct coordinate system.
  • Use an arcpy.SpatialReference object.

Spatial Reference
transform_method
[transform_method,...]
(Optional)

The datum transformation method that will be used when the input layer's coordinate system uses a datum that differs from the output coordinate system. All transformations are bidirectional, regardless of the direction implied by their names. For example, NAD_1927_to_WGS_1984_3 will work correctly even if the datum conversion is from WGS 1984 to NAD 1927.

Note:

ArcGIS coordinate system data is required for vertical datum transformations between ellipsoidal and gravity-related and two gravity-related datums.

String
attributes
[attributes,...]
(Optional)

Specifies the source data attributes that will be included in the scene layer package. These values will be accessible when the content is consumed in other viewers. Select attributes that are required for the desired rendering and filtering options (for example, intensity, returns, class codes, RGB). To reduce storage, exclude unneeded attributes.

  • INTENSITY— The return strength of the laser pulse for each lidar point will be included.
  • RGB—RGB imagery information collected for each lidar point will be included.
  • FLAGS—Classification and scan direction flags will be included.
  • CLASS_CODE—Classification code values will be included.
  • RETURNS—Discrete return numbers from the lidar pulse will be included
  • USER_DATA—A customizable attribute that can be any number in the range of 0 through 255 will be included.
  • POINT_SRC_ID—For aerial lidar, this value typically identifies the flight path that collected a given lidar point, which will be included.
  • GPS_TIME— The GPS time stamp at which the laser point was emitted from the aircraft will be included. The time is in GPS seconds of the week in which the time stamp is between 0 and 604800 and resets at midnight on a Sunday.
  • SCAN_ANGLE—The angular direction of the laser scanner for a given lidar point will be included. The value range is from -90 through 90.
  • NEAR_INFRARED—Near infrared records collected for each lidar point will be included.
String
point_size_m
(Optional)

The point size of the lidar data. For airborne lidar data, the default of 0 or a value close to the average point spacing is usually best. For terrestrial lidar data, the point size should match the desired point spacing for the areas of interest. Values are expressed in meters. The default of 0 will automatically determine the best value for the input dataset.

Double
xy_max_error_m
(Optional)

The maximum x,y error tolerated. A higher tolerance will result in better data compression and more efficient data transfer. Values are expressed in meters. The default is 0.001.

Double
z_max_error_m
(Optional)

The maximum z-error tolerated. A higher tolerance will result in better data compression and more efficient data transfer. Values are expressed in meters. The default is 0.001.

Double
in_coor_system
(Optional)

The coordinate system of the input .laz files. This parameter is only used for .laz files that do not contain spatial reference information in their header or have a .prj file in the same location.

Coordinate System
scene_layer_version
(Optional)

The Indexed 3D Scene Layer (I3S) version of the resulting point cloud scene layer package. Specifying a version supports backward compatibility and allows scene layer packages to be shared with earlier versions of ArcGIS.

  • 1.X—The point cloud scene layer package will be supported in all ArcGIS clients.
  • 2.X—The point cloud scene layer package will be supported in AllSource 2.1.2 or later and can be published to ArcGIS Online and ArcGIS 10.6.1 or later. This is the default.
String
target_cloud_connection
(Optional)

The target cloud connection file (.acs) where the scene layer content (.i3sREST) will be output.

Folder
out_name
(Optional)

The output name of the scene layer content when output to a cloud store. This parameter is only available when a target_cloud_connection parameter value is specified.

String

Code sample

CreatePointCloudSceneLayerPackage example (Python window)

The following Python script demonstrates how to use the CreatePointCloudSceneLayerPackage function from the Python window.

import arcpy
arcpy.env.workspace = "c:/gis_data"
arcpy.management.CreateSceneLayerPackage(
    "Milan.lyrx", "Milan.slpk", arcpy.SpatialReference(4326), 
    ["ITRF_2000_To_WGS_1984 + WGS_1984_To_WGS_1984_EGM2008_2.5x2.5_Height"],
    ["INTENSITY", "RGB", "CLASS_CODE", "FLAGS", "RETURNS"], 0, 0.1, 0.1, None, 
    "1.X")

Environments

This tool does not use any geoprocessing environments.

Feedback on this topic?

In this topic
  1. Summary
  2. Usage
  3. Parameters
  4. Environments
  5. Licensing information