Script Tool API Reference

This appendix documents 127 public gvscript tools in 19 modules for the LiDAR360MLS Script Editor. Availability depends on the LiDAR360MLS 10.0 installation, plug-ins, licensing, and current project state.

Back to Script Development

Calling conventions

• Run scripts inside LiDAR360MLS and normally import APIs with from gvscript import mls.
• Prefer mls..(...) wrappers. Exact tool IDs support advanced gvscript.run_tool() calls.
• input_paths is always a list. Replace D:/data/... paths with real paths.
• Pass top-level parameters directly and create nested Parameters with *_parameters(). Use attribute assignment for valid Python identifiers, item assignment for other field names, and dictionaries for dynamic construction.
• Calls return ToolResult. Inspect result.ok, result.message, and result.error_code, then read result.output, result.outputs, or result.result. Failures raise by default; pass raise_on_error=False to handle them.
• Defaults come from LiDAR360MLS 10.0 configuration. Follow each entry's enum, conditional, and file-format requirements.

Parameters object example

from gvscript import mls

params = mls.point_cloud.pointcloud_extract_by_elevation_parameters()
params.minElevation = 10
params.maxElevation = 80

result = mls.point_cloud.pointcloud_extract_by_elevation(
    input_paths=["D:/data/a.LiData", "D:/data/b.LiData"],
    output_path="D:/data/extracted",
    Parameters=params,
)

for path in result.outputs:
    print(path)

Module index