Point Cloud Task Command Line Tool
About the Point Cloud Task Command Line Tool
The LPRunPCT.exe application contains a number of command line options and associated parameters for running point cloud tasks via the Windows Command Line Interface (CLI). This tool is very useful in certain scenarios where routine tasks are performed, such as when classifying ground, vegetation, or buildings over large areas.
Before being able to run any point cloud task, you will need to create a point cloud task, set its parameters, and then save that task as an .xml file. It will also be necessary to own the proper license level (Basic, Standard, and Advanced) for that task. If you already have LP360 for ArcGIS® or LP360 for Windows® active, this will cause the operation to fail in the node locked license case. If using a floating license, another license is checked out if available. If not available, the operation will fail.
How to Use the Point Cloud Task Command Line Tool
In order to run a point cloud task through the command prompt, you need to create and set the settings for a point cloud task and then save it as an .xml file. This can be done by running the “Export Selected Task” command either in LP360 for ArcGIS or LP360 for Windows. You can select this command by opening the Point Cloud Tasks tab on the Table of Contents window and then clicking on the down-arrow next to the “Point Cloud Tasks” button and selecting “Export Selected Task” from the drop-down menu. In the dialog box that appears you can set the directory and name your .xml file.
The command line options to execute point cloud tasks are as follows:
LPRunPCT{-h}{-q}{-v}{-t<task xml file path>}{-d<input files folder path>}{-i}{p<LP360_PROJECT_PATH>}{-f<input LAS file path>} {-g<input geometry shape file path>} |
Below is the list of operations you can use
| -h or -? -help | Displays usage information |
| -t | Point Cloud Task options xml file path (mandatory) |
| -d | Input files folder path. If this option is supplied, -f is ignored |
| -i | Process files individually from input files folder path, otherwise process as a group. The option is valid only with the -d option |
| -r | Process file recursively from input files folder path, otherwise process files from the input folder. This option is valid only with the -d option |
| -f | Input a file path for processing single LAS files |
| -g | Input a shape file path for area of interest (AOI) geometries. This is optional. If this option is not provided then the point cloud task will be executed on the entire project. |
| -p | LP360-PROJECT_PATH. If this indirection is used in the Input/Output definitions for the point cloud task (strongly recommended), then this path is set by this variable |
| -v | Verbose. All progress messages that you usually get while running the task either in the status bar or in the progress bar are displayed in the command line; Maximum informational output to STDOUT. |
| -q | Quiet. No output to STDOUT. |
Limitations:
You cannot specify a Shape Layer as input geometry. You can only specify either 'Tool_Geometry' or 'File'. If you specify input geometry as 'Tool_Geometry', then you can optionally provide an Area of Interest (AOI) using a shape file. If you have not specified an AOI using a shape file, then the task will be run on the whole project.
You cannot specify 'LAS Layer' as the input layer (except in the case of the Volumetric task).
Breakline enforcement settings do not work in the command line. Layer names are used in breakline enforcement and the command line does not recognize layers
If you set the 'Selected Feature only' option for a point cloud task, it ignores this option and then proceeds to work on all features.
The setting to add outputs to the map is ignored.
The tasks that require you to interact with the map (ex. The Ground Cleaner) cannot be run using the command line tool.
Error Codes returned by LP360:
0 Success
-1 General fatal error
-2 Incorrect parameter
-3 Incorrect license level for the commanded task
Comments
0 comments
Please sign in to leave a comment.