writers.sqlite¶

Example¶

<?xml version="1.0" encoding="utf-8"?>
<Pipeline version="1.0">
    <Writer type="writers.sqlite">
        <Option name="connection">
            output.sqlite
        </Option>
        <Option name="cloud_table_name">
            SIMPLE_CLOUD
        </Option>
        <Option name="pre_sql"/>
        <Option name="post_sql"/>
        <Option name="block_table_name">
            SIMPLE_BLOCKS
        </Option>
        <Option name="cloud_column_name">
            CLOUD
        </Option>

        <Filter type="filters.chipper">
            <Option name="capacity">
                50
            </Option>
            <Reader type="readers.las">
                <Option name="filename">
                    latlon.las
                </Option>
                <Option name="spatialreference">
                    EPSG:4326
                </Option>
            </Reader>
        </Filter>
    </Writer>
</Pipeline>

Options¶

connection

SQLite filename [Required]

cloud_table_name

Name of table to store cloud (file) information [Required]

block_table_name

Name of table to store patch information [Required]

cloud_column_name

Name of column to store primary cloud_id key [Default: cloud]

compression

Use https://github.com/verma/laz-perf compression technique to store patches

overwrite

To drop the table before writing set to ‘true’. To append to the table set to ‘false’. [Default: true]

pre_sql

Optional SQL to execute before running the translation. If the value references a file, the file is read and any SQL inside is executed. Otherwise the value is executed as SQL itself.

post_sql

Optional SQL to execute after running the translation. If the value references a file, the file is read and any SQL inside is executed. Otherwise the value is executed as SQL itself.

scale_x, scale_y, scale_z / offset_x, offset_y, offset_z

If ANY of these options are specified the X, Y and Z dimensions are adjusted by subtracting the offset and then dividing the values by the specified scaling factor before being written as 32-bit integers (as opposed to double precision values). If any of these options is specified, unspecified scale_<x,y,x> options are given the value of 1.0 and unspecified offset_<x,y,z> are given the value of 0.0.

output_dims

If specified, limits the dimensions written for each point. Dimensions are listed by name and separated by commas.