[liblas] 10/15: Install las2col & las2pg in liblas-bin.
Bas Couwenberg
sebastic at debian.org
Mon Aug 22 20:44:34 UTC 2016
This is an automated email from the git hooks/post-receive script.
sebastic pushed a commit to branch master
in repository liblas.
commit 9ab9d3faa31c2bc9e51aadb3dcc4fe2a8d508a4a
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date: Mon Aug 22 20:11:59 2016 +0200
Install las2col & las2pg in liblas-bin.
---
debian/changelog | 1 +
debian/liblas-bin.install | 2 +
debian/liblas-bin.manpages | 2 +
debian/man/las2col.1.xml | 238 +++++++++++++++++++++++++++++++++++++++++++++
debian/man/las2pg.1.xml | 202 ++++++++++++++++++++++++++++++++++++++
5 files changed, 445 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index 33cf45f..9a2873b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,7 @@ liblas (1.8.1~rc1-1) UNRELEASED; urgency=medium
- Rename MIT license shortname to Expat
* Add patch to fix 'offset' typo.
* Update symbols for amd64.
+ * Install las2col & las2pg in liblas-bin.
-- Bas Couwenberg <sebastic at debian.org> Mon, 22 Aug 2016 15:42:02 +0200
diff --git a/debian/liblas-bin.install b/debian/liblas-bin.install
index 4ba9111..bf02db6 100644
--- a/debian/liblas-bin.install
+++ b/debian/liblas-bin.install
@@ -1,5 +1,7 @@
+/usr/bin/las2col
/usr/bin/las2las
/usr/bin/las2ogr
+/usr/bin/las2pg
/usr/bin/las2txt
/usr/bin/lasblock
/usr/bin/lasinfo
diff --git a/debian/liblas-bin.manpages b/debian/liblas-bin.manpages
index 1b3c1fe..c06426e 100644
--- a/debian/liblas-bin.manpages
+++ b/debian/liblas-bin.manpages
@@ -1,5 +1,7 @@
+debian/man/las2col.1
debian/man/las2las.1
debian/man/las2ogr.1
+debian/man/las2pg.1
debian/man/las2txt.1
debian/man/lasblock.1
debian/man/lasinfo.1
diff --git a/debian/man/las2col.1.xml b/debian/man/las2col.1.xml
new file mode 100644
index 0000000..5ebec4f
--- /dev/null
+++ b/debian/man/las2col.1.xml
@@ -0,0 +1,238 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<refentry id='las2col'>
+
+ <refmeta>
+ <refentrytitle>las2col</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </refmeta>
+
+ <refnamediv>
+ <refname>las2col</refname>
+ <refpurpose>LAS translation to MonetDB binary format</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv id='synopsis'>
+ <cmdsynopsis>
+ <command>las2col</command>
+ <arg choice='opt'><option><replaceable>OPTIONS</replaceable></option></arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsect1 id='description'>
+ <title>DESCRIPTION</title>
+ <para>
+ <command>las2col</command> performs LAS translation to MonetDB binary
+ format with optional configuration.
+ </para>
+ </refsect1>
+
+ <refsect1 id='options'>
+ <title>OPTIONS</title>
+
+ <variablelist>
+
+ <varlistentry>
+ <term><option>-h</option></term>
+ <term><option>-help</option></term>
+ <term><option>--help</option></term>
+ <listitem>
+ <para>
+ produce help message
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-v</option></term>
+ <term><option>--verbose</option></term>
+ <listitem>
+ <para>
+ Verbose message output
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--num_read_threads</option> <replaceable>number</replaceable></term>
+ <listitem>
+ <para>
+ Set number of threads
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-s</option></term>
+ <term><option>--skip_invalid</option></term>
+ <listitem>
+ <para>
+ Skip writing invalid point(s)
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-parse</option> <replaceable>string</replaceable></term>
+ <term><option>--parse</option> <replaceable>string</replaceable></term>
+ <listitem>
+ <para>
+ Specify which entries of the LAS/LAZ will be extracted
+ (default is xyz).
+ For example, 'txyzia' means that six columnar (binary) MonetDB
+ files will be generated, the first one containing all gpstime
+ values, the next three containing values for x, y, and z
+ coordinates, the next one with intensity values and the last one
+ with scan angle values.
+ The supported entries are:
+ <simplelist type='vert' columns='1'>
+ <member>t - gpstime as double</member>
+ <member>x - x coordinate as double</member>
+ <member>y - y coordinate as double</member>
+ <member>z - z coordinate as double</member>
+ <member>X - x coordinate as decimal(<replaceable>num_digits_unscaled_max_x</replaceable>,<replaceable>num_digits_scale_x</replaceable>)</member>
+ <member>Y - y coordinate as decimal(<replaceable>num_digits_unscaled_max_y</replaceable>,<replaceable>num_digits_scale_y</replaceable>)</member>
+ <member>Z - z coordinate as decimal(<replaceable>num_digits_unscaled_max_z</replaceable>,<replaceable>num_digits_scale_z</replaceable>)</member>
+ <member>a - scan angle as tinyint</member>
+ <member>i - intensity as smallint</member>
+ <member>n - number of returns for given pulse as smallint</member>
+ <member>r - number of this return as smallint</member>
+ <member>c - classification number as tinyint</member>
+ <member>u - user data as tinyint</member>
+ <member>p - point source ID as smallint</member>
+ <member>e - edge of flight line as smallint</member>
+ <member>d - direction of scan flag as smallint</member>
+ <member>R - red channel of RGB color as smallint</member>
+ <member>G - green channel of RGB color as smallint</member>
+ <member>B - blue channel of RGB color as smallint</member>
+ <member>M - vertex index number as integer</member>
+ <member>k - Morton 2D code using X and Y (unscaled and no offset) as bigint</member>
+ </simplelist>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-moffset</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <term><option>--moffset</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <listitem>
+ <para>
+ Specify a global offset in X and Y to be used when computing the
+ Morton 2D code. Values must be unscaled
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-check</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <term><option>--check</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <listitem>
+ <para>
+ Check suitability to compute Morton 2D codes.
+ It checks specified scale matches the one in input file.
+ If <option>--moffset</option> is provided it also checks that
+ obtained Morton 2D codes will be consistent, i.e. global X,Y within [0,2^31]
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-i</option> <replaceable>arg</replaceable></term>
+ <term><option>-in</option> <replaceable>arg</replaceable></term>
+ <term><option>-input</option> <replaceable>arg</replaceable></term>
+ <term><option>--input</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ file with the list las/laz files
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-f</option> <replaceable>arg</replaceable></term>
+ <term><option>-file</option> <replaceable>arg</replaceable></term>
+ <term><option>--file</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ input LAS file
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-o</option> <replaceable>arg</replaceable></term>
+ <term><option>-out</option> <replaceable>arg</replaceable></term>
+ <term><option>--out</option> <replaceable>arg</replaceable></term>
+ <term><option>--output</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ output prefix
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ </refsect1>
+
+ <refsect1 id='example'>
+ <title>EXAMPLE</title>
+
+ <para>
+ Convert a las/laz file into columnar format (binary) of MonetDB,
+ outputs for each entry a file
+ <replaceable>output_prefix</replaceable>_col_<replaceable>entry_name</replaceable>.dat:
+ <screen>
+las2col -i <replaceable>input_file</replaceable> -o <replaceable>output_prefix</replaceable>
+ </screen>
+ </para>
+
+ <para>
+ Convert a list of las/laz files (still outputs for each entry a file
+ <replaceable>output_prefix</replaceable>_col_<replaceable>entry_name</replaceable>.dat):
+ <screen>
+las2col -i <replaceable>las_file_1</replaceable> -i <replaceable>las_file_2</replaceable> -o <replaceable>output_prefix</replaceable>
+ </screen>
+ Alternatively:
+ <screen>
+las2col -f <replaceable>file_with_the_list_las/laz_files</replaceable> -o <replaceable>output_prefix</replaceable>
+ </screen>
+ </para>
+
+ <para>
+ Convert a list of las/laz files using
+ <replaceable>num_read_threads</replaceable> threads (default is 1):
+ <screen>
+las2col -f <replaceable>file_with_the_list_las/laz_files</replaceable> -o <replaceable>output_prefix</replaceable> --num_read_threads <replaceable>number_of_threads</replaceable>
+ </screen>
+ </para>
+
+ <para>
+ After generating the columnar files, import them in MonetDB.
+ Example:
+ <screen>
+mclient <replaceable>db_name</replaceable> -s "COPY BINARY INTO flat FROM ('<replaceable>full_parent_path</replaceable>/out_col_x.dat','<replaceable>full_parent_path</replaceable>/out_col_y.dat','<replaceable>full_parent_path</replaceable>/out_col_z.dat')"
+ </screen>
+ Note that full paths of the columnar files MUST be used.
+ Also note that a table called flat has to be created in a MonetDB DB
+ beforehand.
+ The table must have the columns in the same order as specified by the
+ <option>--parse</option> option, and the column types must be the ones
+ specified above.
+ Example:
+ <screen>
+mclient <replaceable>db_name</replaceable> -s "create table flat (x double, y double, z double)"
+ </screen>
+ Note that for decimal entries (XYZ) the column definition at
+ table-creation time must be
+ decimal(<replaceable>num_digits_unscaled_max</replaceable>,<replaceable>num_digits_scale</replaceable>)
+ For example, if the maximum X value of a file (or a list of files) is
+ 638982.55, then the X definition when creating the table is decimal(8,2).
+ Example:
+ <screen>
+mclient <replaceable>db_name</replaceable> -s "create table flat (x decimal(8,2), y decimal(8,2), z decimal(8,2))"
+ </screen>
+ </para>
+
+ </refsect1>
+</refentry>
diff --git a/debian/man/las2pg.1.xml b/debian/man/las2pg.1.xml
new file mode 100644
index 0000000..404c894
--- /dev/null
+++ b/debian/man/las2pg.1.xml
@@ -0,0 +1,202 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<refentry id='las2pg'>
+
+ <refmeta>
+ <refentrytitle>las2pg</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </refmeta>
+
+ <refnamediv>
+ <refname>las2pg</refname>
+ <refpurpose>LAS translation to PostgreSQL binary format</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv id='synopsis'>
+ <cmdsynopsis>
+ <command>las2pg</command>
+ <arg choice='opt'><option><replaceable>OPTIONS</replaceable></option></arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsect1 id='description'>
+ <title>DESCRIPTION</title>
+ <para>
+ <command>las2pg</command> performs LAS translation to PostgreSQL binary
+ format with optional configuration.
+ </para>
+ </refsect1>
+
+ <refsect1 id='options'>
+ <title>OPTIONS</title>
+
+ <variablelist>
+
+ <varlistentry>
+ <term><option>-h</option></term>
+ <term><option>-help</option></term>
+ <term><option>--help</option></term>
+ <listitem>
+ <para>
+ produce help message
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-v</option></term>
+ <term><option>--verbose</option></term>
+ <listitem>
+ <para>
+ Verbose message output
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--num_read_threads</option> <replaceable>number</replaceable></term>
+ <listitem>
+ <para>
+ Set number of threads
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-s</option></term>
+ <term><option>--skip_invalid</option></term>
+ <listitem>
+ <para>
+ Skip writing invalid point(s)
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-parse</option> <replaceable>string</replaceable></term>
+ <term><option>--parse</option> <replaceable>string</replaceable></term>
+ <listitem>
+ <para>
+ Specify what exactly to write for each row (default is xyz).
+ For example, 'txyzia' means that the first field of each row will
+ be the gpstime, the next three fields will be the x, y, and z
+ coordinates, the next field will be the intensity and the next
+ field will be the scan angle.
+ The supported entries are:
+ <simplelist type='vert' columns='1'>
+ <member>t - gpstime as double</member>
+ <member>x - x coordinate as double</member>
+ <member>y - y coordinate as double</member>
+ <member>z - z coordinate as double</member>
+ <member>a - scan angle as integer</member>
+ <member>i - intensity as integer</member>
+ <member>n - number of returns for given pulse as integer</member>
+ <member>r - number of this return as integer</member>
+ <member>c - classification number as integer</member>
+ <member>u - user data as integer</member>
+ <member>p - point source ID as integer</member>
+ <member>e - edge of flight line as integer</member>
+ <member>d - direction of scan flag as integer</member>
+ <member>R - red channel of RGB color as integer</member>
+ <member>G - green channel of RGB color as integer</member>
+ <member>B - blue channel of RGB color as integer</member>
+ <member>M - vertex index number as integer</member>
+ <member>k - Morton 2D code using X and Y (unscaled and no offset) as bigint</member>
+ </simplelist>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-moffset</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <term><option>--moffset</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <listitem>
+ <para>
+ Specify a global offset in X and Y to be used when computing the
+ Morton 2D code. Values must be unscaled
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-check</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <term><option>--check</option> <replaceable>x</replaceable>,<replaceable>y</replaceable></term>
+ <listitem>
+ <para>
+ Check suitability to compute Morton 2D codes.
+ It checks specified scale matches the one in input file.
+ If <option>--moffset</option> is provided it also checks that
+ obtained Morton 2D codes will be consistent, i.e. global X,Y within [0,2^31]
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--stdout</option></term>
+ <listitem>
+ <para>
+ Use STDOUT
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-i</option> <replaceable>arg</replaceable></term>
+ <term><option>-in</option> <replaceable>arg</replaceable></term>
+ <term><option>-input</option> <replaceable>arg</replaceable></term>
+ <term><option>--input</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ file with the list las/laz files
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-o</option> <replaceable>arg</replaceable></term>
+ <term><option>-out</option> <replaceable>arg</replaceable></term>
+ <term><option>--out</option> <replaceable>arg</replaceable></term>
+ <term><option>--output</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ output prefix
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ </refsect1>
+
+ <refsect1 id='example'>
+ <title>EXAMPLE</title>
+
+ <para>
+ Convert a las/laz file into PostgreSQL binary dump format,
+ outputs <replaceable>output_name</replaceable>:
+ <screen>
+las2pg -i <replaceable>input_file</replaceable>.las -o <replaceable>output_name</replaceable>
+ </screen>
+ Use flag <option>--stdout</option> to write to standard output
+ (recommended use together with a pipe, see below).
+ </para>
+ <para>
+ The intended use of this tool is by using the <option>--stdout</option>
+ flag and a pipe to avoid storing intermediate files.
+ Example:
+ <screen>
+las2pg 1.2-with-color.laz --parse xyzRGBi --stdout | psql -c "copy flat from stdin with binary"
+ </screen>
+ This obviously require a table called flat to be created in a PostgreSQL
+ DB beforehand.
+ The table must have the columns in the same order as specified by the
+ <option>--parse</option> option, and the column types must be the ones
+ specified above.
+ Example:
+ <screen>
+psql -c "create table flat (x double precision, y double precision, z double precision, r integer, g integer, b integer, i integer)"
+ </screen>
+ </para>
+
+ </refsect1>
+</refentry>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/liblas.git
More information about the Pkg-grass-devel
mailing list