[liblas] 20/23: Add manpage for txt2las.

Bas Couwenberg sebastic at xs4all.nl
Sat Feb 8 01:30:45 UTC 2014


This is an automated email from the git hooks/post-receive script.

sebastic-guest pushed a commit to branch master
in repository liblas.

commit 878dfd88e65e418f6eb84a8f0f698ace213f0d2c
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date:   Sat Feb 8 00:03:06 2014 +0100

    Add manpage for txt2las.
---
 debian/liblas-bin.manpages |   1 +
 debian/man/txt2las.1.xml   | 211 +++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 212 insertions(+)

diff --git a/debian/liblas-bin.manpages b/debian/liblas-bin.manpages
index 273e1ef..d7969d7 100644
--- a/debian/liblas-bin.manpages
+++ b/debian/liblas-bin.manpages
@@ -3,3 +3,4 @@ debian/man/las2ogr.1
 debian/man/las2txt.1
 debian/man/lasinfo.1
 debian/man/lasmerge.1
+debian/man/txt2las.1
diff --git a/debian/man/txt2las.1.xml b/debian/man/txt2las.1.xml
new file mode 100644
index 0000000..ecc959f
--- /dev/null
+++ b/debian/man/txt2las.1.xml
@@ -0,0 +1,211 @@
+<?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='txt2las'>
+
+  <refmeta>
+    <refentrytitle>txt2las</refentrytitle>
+    <manvolnum>1</manvolnum>
+  </refmeta>
+
+  <refnamediv>
+    <refname>txt2las</refname>
+    <refpurpose>converts LIDAR data from ASCII format into LAS representation</refpurpose>
+  </refnamediv>
+
+  <refsynopsisdiv id='synopsis'>
+    <cmdsynopsis>
+      <command>txt2las</command>
+      <group>
+        <arg choice='plain'><option>-h</option></arg>
+        <arg choice='plain'><option>-parse</option> <literal>tsxyz</literal>
+          <replaceable>lidar.txt</replaceable>
+        </arg>
+        <arg choice='plain'><option>-parse</option> <literal>txyzar</literal>
+          <replaceable>lidar.txt.gz lidar.laz</replaceable>
+        </arg>
+        <arg choice='plain'><option>-parse</option> <literal>xyz</literal>
+          <arg choice='opt'><option>-scale</option>
+            <replaceable>0.02</replaceable>
+          </arg>
+          <option>-i</option> <replaceable>lidar.txt</replaceable>
+          <option>-o</option> <replaceable>lidar.laz</replaceable>
+        </arg>
+        <arg choice='plain'><option>-parse</option> <literal>xyzsst</literal>
+          <arg choice='opt'><option>-verbose</option></arg>
+          <arg choice='opt'><option>-scale</option> <replaceable>0.05</replaceable></arg>
+          <replaceable>lidar.txt</replaceable>
+        </arg>
+        <arg choice='plain'><option>-parse</option> <literal>xsysz</literal>
+          <arg choice='opt'><option>-xyz_scale</option> <replaceable>0.02 0.02 0.01</replaceable></arg>
+          <replaceable>lidar.txt</replaceable>
+        </arg>
+      </group>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsect1 id='description'>
+    <title>DESCRIPTION</title>
+    <para>
+      <command>txt2las</command> converts LIDAR data from a standard
+      ASCII format into the more efficient binary LAS representation.
+    </para>
+  </refsect1>
+
+  <refsect1 id='options'>
+    <title>OPTIONS</title>
+
+    <variablelist>
+
+      <varlistentry>
+        <term><option>-h</option></term>
+        <listitem>
+          <para>
+            produce help message
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-parse</option> <replaceable>arg</replaceable></term>
+        <listitem>
+          <para>Parsing Flags</para>
+          <para>
+            The '<option>-parse tsxyz</option>' flag specifies how to interpret
+            each line of the ASCII file.
+          </para>
+          <para>
+            For example, '<literal>tsxyzssa</literal>' means that the first
+            number is the gpstime, the next number should be skipped,
+            the next three numbers are the x, y, and z coordinate,
+            the next two should be skipped,
+            and the next number is the scan angle.
+          </para>
+          <para>
+            The other supported entries are:
+            <itemizedlist>
+              <listitem>
+                <para>i - intensity</para>
+              </listitem>
+              <listitem>
+                <para>n - number of returns of given pulse</para>
+              </listitem>
+              <listitem>
+                <para>r - number of return</para>
+              </listitem>
+              <listitem>
+                <para>c - classification</para>
+              </listitem>
+              <listitem>
+                <para>u - user data</para>
+              </listitem>
+              <listitem>
+                <para>p - point source ID</para>
+              </listitem>
+              <listitem>
+                <para>e - edge of flight line flag</para>
+              </listitem>
+              <listitem>
+                <para>d - direction of scan flag.</para>
+              </listitem>
+            </itemizedlist>
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-scale</option> <replaceable>arg</replaceable></term>
+        <listitem>
+          <para>Scale</para>
+          <para>
+            The '<option>-scale 0.02</option>' flag specifies the quantization.
+          <para>
+          </para>
+            The default value of 0.01 means that the smallest increment two
+            between coordinates is 0.01.
+          <para>
+          </para>
+            If measurements are in meters this corresponds to centimeter
+            accuracy, which is commonly considered sufficient for LIDAR data.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-i</option> <replaceable>arg</replaceable></term>
+        <listitem>
+          <para>
+            input LAS file.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-o</option> <replaceable>arg</replaceable></term>
+        <listitem>
+          <para>
+            output text file.
+          </para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-xyz_offset</option> <replaceable>500000 2000000 0</replaceable></term>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-xyz_scale</option> <replaceable>0.02 0.02 0.01</replaceable></term>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-file_creation</option> <replaceable>67 2003</replaceable></term>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-system_identifier</option> <replaceable>"Airborne One Leica 50,000 Hz"</replaceable></term>
+      </varlistentry>
+
+      <varlistentry>
+        <term><option>-generating_software</option> <replaceable>"TerraScan"</replaceable></term>
+      </varlistentry>
+
+    </variablelist>
+
+  </refsect1>
+
+  <refsect1 id='example'>
+    <title>EXAMPLE</title>
+
+    <example>
+      <title>Simple conversion to text file</title>
+
+      <screen>
+$ txt2las -i lidar.las -o lidar.txt -parse xyz
+      </screen>
+
+      converts LAS file to ASCII and places the x, y, and z coordinate
+      of each point at the 1st, 2nd, and 3rd entry of each line.
+      The entries are separated by a space.
+    </example>
+
+    <example>
+      <screen>
+$ txt2las -i lidar.taxyz -o lidar.las -parse ssxyz
+      </screen>
+
+      converts ASCII file and uses the 3rd, 4th, and 5th entry of each
+      line as the x, y, and z coordinate of each point.
+    </example>
+
+    <example>
+      <screen>
+$ txt2las -i lidar.txt.gz -o lidar.las -parse txyzsa
+      </screen>
+
+      converts a gzipped ASCII file and uses the 1st entry of each line
+      as the gps time, the 3rd, 4th, and 5th entry as the x, y, and z
+      coordinate of each point, and the 6th entry as the scan angle
+    </example>
+
+  </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