filters.splitter

The Splitter Filter breaks a point cloud into square tiles of a specified size. The origin of the tiles is chosen arbitrarily unless specified with the origin_x and origin_y option.

The splitter takes a single PointView as its input and creates a PointView for each tile as its output.

Splitting is usually applied to data read from files (which produce one large stream of points) before the points are written to a database (which prefer data segmented into smaller blocks).

Default Embedded Stage

This stage is enabled by default

Example

[
    "input.las",
    {
        "type":"filters.splitter",
        "length":"100",
        "origin_x":"638900.0",
        "origin_y":"835500.0"
    },
    {
        "type":"writers.pgpointcloud",
        "connection":"dbname='lidar' user='user'"
    }
]

Options

length: Length of the sides of the tiles that are created to hold points. [Default: 1000]
origin_x: X Origin of the tiles. [Default: none (chosen arbitrarily)]
origin_y: Y Origin of the tiles. [Default: none (chosen arbitrarily)]
buffer: Amount of overlap to include in each tile. This buffer is added onto length in both the x and the y direction. [Default: 0]

where: An expression that limits points passed to a filter. Points that don’t pass the expression skip the stage but are available to subsequent stages in a pipeline. [Default: no filtering]
where_merge: A strategy for merging points skipped by a ‘where’ option when running in standard mode. If true, the skipped points are added to the first point view returned by the skipped filter. If false, skipped points are placed in their own point view. If auto, skipped points are merged into the returned point view provided that only one point view is returned and it has the same point count as it did when the filter was run. [Default: auto]