[liblas] 15/23: Add manpage for las2las.
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 de5144847b3e7b765131952a2cddff8cde030da6
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date: Fri Feb 7 04:15:56 2014 +0100
Add manpage for las2las.
---
debian/liblas-bin.manpages | 1 +
debian/man/las2las.1.xml | 999 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 1000 insertions(+)
diff --git a/debian/liblas-bin.manpages b/debian/liblas-bin.manpages
new file mode 100644
index 0000000..1f6f19f
--- /dev/null
+++ b/debian/liblas-bin.manpages
@@ -0,0 +1 @@
+debian/man/las2las.1
diff --git a/debian/man/las2las.1.xml b/debian/man/las2las.1.xml
new file mode 100644
index 0000000..fe7980f
--- /dev/null
+++ b/debian/man/las2las.1.xml
@@ -0,0 +1,999 @@
+<?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='las2las'>
+
+ <refmeta>
+ <refentrytitle>las2las</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </refmeta>
+
+ <refnamediv>
+ <refname>las2las</refname>
+ <refpurpose>Advanced LAS filtering and manipulation</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv id='synopsis'>
+ <cmdsynopsis>
+ <command>las2las</command>
+ <arg choice='opt'><option><replaceable>OPTIONS</replaceable></option></arg>
+ </cmdsynopsis>
+ </refsynopsisdiv>
+
+ <refsect1 id='description'>
+ <title>DESCRIPTION</title>
+ <para>
+ <command>las2las</command> reads and writes LiDAR data in the ASPRS LAS
+ 1.0, 1.1, and 1.2 formats while modifying its contents.
+ <command>las2las</command> is designed for filtering and transformation
+ operations of LAS files.
+ </para>
+ <para>
+ While
+ <citerefentry>
+ <refentrytitle>lasinfo</refentrytitle>
+ <manvolnum>1</manvolnum>
+ </citerefentry>,
+ can do a few simple operations like updating header information,
+ more drastic changes, like removing points or altering values,
+ will require <command>las2las</command>.
+ <command>las2las</command> is expected to be used for modifying
+ single files at a time, and some <command>las2las</command> operations
+ require multiple read passes through the points.
+ Some examples of operations <command>las2las</command> can be used for
+ include:
+ <itemizedlist>
+ <listitem>
+ <para>
+ clipping of points to those that lie within a certain region
+ specified by a bounding box (<option>--extent</option>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ eliminating points that are the second return
+ (<option>--drop-return 2</option>),
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ eliminating points that have a scan angle
+ above some threshold (<option>--drop-scan-angle "<5"</option>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ eliminating points that have an intensity below some
+ threshold (<option>--drop-intensity "<15"</option>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ extracting only first (<option>--first-only</option>)
+ or last (<option>--last-only</option>) returns
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ changing the format from LAS 1.0 to 1.1 or vice versa
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ eliminating points of a given classification
+ (<option>--eliminate class 2</option>)
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ <command>las2las</command> started a port of Martin Isenburg's
+ <command>las2las</command> utility from
+ <ulink url="http://www.cs.unc.edu/~isenburg/lastools/">LASTools</ulink>
+ to the libLAS library.
+ It is much-improved from his version, however,
+ and provides a number of additional capabilities.
+ </para>
+ <formalpara>
+ <title>See also</title>
+ <para>
+ <ulink url="http://www.liblas.org/lastools.html#lastools-liblas">libLAS’ Relationship to LAStools</ulink>
+ contains background information on the port of Isenburg
+ and Shewchuck's utilities to the libLAS library.
+ </para>
+ </formalpara>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Text output describing the operation(s) is only provided when the
+ <option>--verbose</option> (<option>-v</option>)
+ switch is provided.
+ Errors are reported to stderr.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Coordinate reprojection, including vertical datum transformation
+ when compiled with the latest
+ <ulink url="http://www.gdal.org">GDAL</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Coordinate system description and alteration.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Variable Length Records (VLRs) are carried forward by default.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ VLR alteration, including adding your own VLRs with files and
+ removal of VLRs
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ File splitting based on a specified file size
+ (<option>--split-mb</option>) or points
+ (<option>--split-pts</option>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Ability to set coordinate offsets to minimum
+ values of the existing coordinate space.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Color filtering
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </refsect1>
+
+ <refsect1 id='options'>
+ <title>OPTIONS</title>
+
+ las2las2 options:
+ <variablelist>
+
+ <varlistentry>
+ <term><option>-h</option></term>
+ <term><option>--help</option></term>
+ <listitem>
+ <para>
+ produce help message
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--split-mb</option> <replaceable>arg</replaceable> (=0)</term>
+ <listitem>
+ <para>
+ Split file into multiple files with each being this size in MB
+ or less.
+ If this value is 0, no splitting is done
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--split-pts</option> <replaceable>arg</replaceable> (=0)</term>
+ <listitem>
+ <para>
+ Split file into multiple files with each being this many points
+ or less.
+ If this value is 0, no splitting is done
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-i</option> <replaceable>arg</replaceable></term>
+ <term><option>--input</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ input LAS file
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-o</option> <replaceable>arg</replaceable></term>
+ <term><option>--output</option> <replaceable>arg</replaceable> (=output.las)</term>
+ <listitem>
+ <para>
+ output LAS file
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-v</option></term>
+ <term><option>--verbose</option></term>
+ <listitem>
+ <para>
+ Verbose message output
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ Header modification options:
+ <variablelist>
+
+ <varlistentry>
+ <term><option>--a_srs</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Coordinate system to assign to input LAS file
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--a_vertcs</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Override vertical coordinate system information.
+ Use
+ <option>--a_vertcs "verticalCSType [citation [verticalDatum [verticalUnits]]]"</option>
+ For example:
+ <option>--a_vertcs 5703 "North American Vertical Datum of 1988 (NAVD88)" 5103 9001</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--offset</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A comma-separated or quoted, space-separated list
+ of offsets to set on the output file:
+ <option>--offset 0,0,0</option>
+ <option>--offset "1234 5678 91011"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--scale</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A list of scales to set on the output file.
+ Scales <emphasis>cannot</emphasis> be negative,
+ and should always be a negative power of 10:
+ <option>--scale 0.1 0.1 0.00001</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-f</option> <replaceable>arg</replaceable></term>
+ <term><option>--file-format</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Set the LAS format of the new file (only 1.0-1.2
+ supported at this time):
+ <option>--file-format 1.2</option>
+ <option>-f 1.1</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--point-format</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Set the LAS point format of the new file (0, 1, 2, 3):
+ <option>--point-format 3</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--pad-header</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Add extra bytes to the existing header
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--min-offset</option></term>
+ <listitem>
+ <para>
+ Set the offset of the header to the minimums of all
+ values in the file.
+ Note that this requires multiple read passes through
+ the file to achieve.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--file-creation</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Set the header's day/year.
+ Specify either as "1 2010" for the first day of 2010,
+ or as "now" to specify the current day/year
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--add-schema</option></term>
+ <listitem>
+ <para>
+ Add the liblas.org schema VLR record to the file.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--delete-vlr</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Removes VLRs with the given name and id combination.
+ <option>--delete-vlr LASF_Projection 34737</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--add-vlr</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Add VLRs with the given name and id combination.
+ <option>--add-vlr hobu 1234 "Description of the VLR" "filename.ext"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--system-identifier</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Set the SystemID for the file.
+ <option>--system-identifier "MODIFICATION"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--generating-software</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Set the SoftwareID for the file.
+ <option>--generating-software "liblas.org"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ Transformation options:
+ <variablelist>
+
+ <varlistentry>
+ <term><option>--t_srs</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Coordinate system to reproject output LAS file to.
+ Use <option>--a_srs</option> or verify that your input LAS file
+ has a coordinate system according to lasinfo
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--point-translate</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ An expression to translate the X, Y, Z values of the point.
+ For example, converting Z units that are in meters to feet:
+ <option>--point-translate "x*1.0 y*1.0 z*3.2808399"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--color-source</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A string to a GDAL-openable raster data source.
+ Use GDAL VRTs if you want to adjust the data source
+ or set its coordinate system, etc.
+ <option>--color-source "afile.tif"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--color-source-bands</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A list of three bands from the <option>--color-source</option>
+ to assign to the R, G, B values for the point
+ <option>--color-source-bands 1 2 3</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--color-source-scale</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A number used by <option>--color-source</option>
+ to scale the input R, G, B values for the point.
+ For example, to scale the 8 bit color data from an input raster to
+ 16 bit, the 8 bit data should be multiplied by 257.
+ <option>--color-source-scale 256</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ Filtering options:
+ <variablelist>
+
+ <varlistentry>
+ <term><option>-e</option> <replaceable>arg</replaceable></term>
+ <term><option>--extent</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent window that points must fall within to keep.
+ Use a comma-separated or quoted, space-separated list, for example,
+ <option>-e minx, miny, maxx, maxy</option>
+ or
+ <option>-e minx, miny, minz, maxx, maxy, maxz</option>
+ <option>-e "minx miny minz maxx maxy maxz"</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--minx</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be greater than or equal to minx to be kept.
+ <option>--minx 1234.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--miny</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be greater than or equal to miny to be kept.
+ <option>--miny 5678.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--minz</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be greater than or equal to minz to be
+ kept. If maxx and maxy are set but not minz *and maxz,
+ all z values are kept.
+ <option>--minz 0.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--maxx</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be less than or equal to maxx to be kept.
+ <option>--maxx 1234.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--maxy</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be less than or equal to maxy to be kept.
+ <option>--maxy 5678.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--maxz</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Extent must be less than or equal to maxz to be kept.
+ If maxx and maxy are set but not maxz *and minz, all z
+ values are kept.
+ <option>--maxz 10.0</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-t</option> <replaceable>arg</replaceable></term>
+ <term><option>--thin</option> <replaceable>arg</replaceable> (=0)</term>
+ <listitem>
+ <para>
+ Simple decimation-style thinning.
+ Thin the file by removing every t'th point from the file.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--last-return-only</option></term>
+ <listitem>
+ <para>
+ Keep last returns
+ (cannot be used with <option>--first-return-only</option>)
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--first-return-only</option></term>
+ <listitem>
+ <para>
+ Keep first returns
+ (cannot be used with <option>--last-return-only</option>)
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-returns</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A list of return numbers to keep in the output file:
+ <option>--keep-returns 1 2 3</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-returns</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Return numbers to drop.
+ For example, <option>--drop-returns 2 3 4 5</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--valid_only</option></term>
+ <listitem>
+ <para>
+ Keep only valid points
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-classes</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A list of classifications to keep:
+ <option>--keep-classes 2 4 12</option>
+ <option>--keep-classes 2</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-classes</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ A comma-separated list of classifications to drop:
+ <option>--drop-classes 1,7,8</option>
+ <option>--drop-classes 2</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-intensity</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to keep intensity.
+ The following expression types are supported:
+ <option>--keep-intensity 0-100</option>
+ <option>--keep-intensity <200</option>
+ <option>--keep-intensity >400</option>
+ <option>--keep-intensity >=200</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-intensity</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to drop intensity.
+ The following expression types are supported:
+ <option>--drop-intensity <200 </option>
+ <option>--drop-intensity >400 </option>
+ <option>--drop-intensity >=200</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-time</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to keep time.
+ The following expression types are supported:
+ <option>--keep-time 413665.2336-414092.8462</option>
+ <option>--keep-time <414094.8462</option>
+ <option>--keep-time >413665.2336</option>
+ <option>--keep-time >=413665.2336</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-time</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to drop time.
+ The following expression types are supported:
+ <option>--drop-time <413666.2336 </option>
+ <option>--drop-time >413665.2336 </option>
+ <option>--drop-time >=413665.2336</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-scan-angle</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to keep scan angle.
+ The following expression types are supported:
+ <option>--keep-scan-angle 0-100</option>
+ <option>--keep-scan-angle <100</option>
+ <option>--keep-scan-angle <=100</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-scan-angle</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to drop scan angle.
+ The following expression types are supported:
+ <option>--drop-scan-angle <30</option>
+ <option>--drop-scan-angle >100</option>
+ <option>--drop-scan-angle >=100</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--keep-color</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to keep colors.
+ Define colors as two 3-tuples (R,G,B-R,G,B):
+ <option>--keep-color '0,0,0-125,125,125'</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--drop-color</option> <replaceable>arg</replaceable></term>
+ <listitem>
+ <para>
+ Range in which to drop colors.
+ Define colors as two 3-tuples (R,G,B-R,G,B):
+ <option>--drop-color '255,255,255-65536,65536,65536'</option>
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+
+ For more information, see the full documentation for las2las2 at:
+ <ulink url="http://liblas.org/utilities/las2las2.html">http://liblas.org/utilities/las2las2.html</ulink>
+ </refsect1>
+
+ <refsect1 id='example'>
+ <title>EXAMPLE</title>
+
+ <example>
+ <title>Clipping with a rectangle</title>
+
+ <screen>
+$ las2las in.las --output out.las --extent "63025000 483450000 63050000 483475000"
+ </screen>
+
+ clips points of in.las with x<=63025000 and y<=483450000
+ or x>=63050000 and y>=483475000 and stores surviving points to
+ out.las.
+
+ <screen>
+$ las2las in.las --output out.las --extent "63025000 483450000 0 63050000 483475000 100""
+ </screen>
+
+ clips points of in.las with x <= 63025000 and y <= 483450000 and z <= 100
+ or x >= 63050000 and y >= 483475000 and z >= 0
+
+ <formalpara>
+ <title>note</title>
+ <para>
+ The quotes around the extent values are important to aid the command line
+ parsing.
+ An error will likely result of not quoting the values.
+ Alternatively, you can use commas to separate the
+ <option>--extent</option> parameters to avoid quoting.
+ </para>
+ </formalpara>
+ </example>
+
+ <example>
+ <title>Eliminating specified returns</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --drop-returns 1
+ </screen>
+
+ eliminates all points of in.las that are designated first returns by the
+ value in their return_number field and stores surviving points to
+ out.las.
+
+ <screen>
+$ las2las --input in.las --output out.las --drop-returns 2 3 4 5
+ </screen>
+
+ eliminates all returns in the specified list.
+ </example>
+
+ <example>
+ <title>Limiting based on scan angle</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --keep-scan-angle "<=15"
+ </screen>
+
+ keeps all points of in.las whose scan angle is <= 15.
+ </example>
+
+ <example>
+ <title>Limiting based on intensity</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --drop-intensity "<=1000"
+ </screen>
+
+ eliminates all points of in.las whose intensity is below 1000 and stores
+ surviving points to out.las.
+ </example>
+
+ <example>
+ <title>Extract last returns</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --last-return-only
+ </screen>
+
+ extracts all last return points from in.las and stores them to out.las.
+ </example>
+
+ <example>
+ <title>Throw out invalid data</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --valid-only
+ </screen>
+
+ removes invalid (according to the ASPRS LAS file format specification)
+ points.
+ This switch should only be required in a few special circumstances.
+ Points that might be invalid include those with larger-than-required
+ scan angles.
+ </example>
+
+ <example>
+ <title>Eliminate ground points</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --drop-classes 2
+ </screen>
+
+ removes points with that have a classification of 2. Points with a
+ classification of 2 are conventionally called ground points, but that
+ convention may not be followed for older LAS 1.0 files.
+ </example>
+
+ <example>
+ <title>Eliminate ground and unclassified points</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --drop-classes 1 2
+ </screen>
+
+ removes points that have a classification of 1 or 2.
+ </example>
+
+ <example>
+ <title>Convert to 1.1</title>
+
+ <screen>
+$ las2las --input in.las --output out.las --format 1.1
+ </screen>
+
+ converts the in.las file to a 1.1-formatted file.
+ For the most part, this conversion is "in name only."
+ </example>
+
+ <example>
+ <title>Alter vertical datum information</title>
+
+ <screen>
+$ las2las in.las --a_vertcs 5703 "North American Vertical Datum of 1988 (NAVD88)" 5103 9001
+ </screen>
+
+ sets the vertical datum information for the file to be NAVD88 with
+ vertical units of meters.
+
+ <formalpara>
+ <title>note</title>
+ <para>
+ This may not be relevant depending upon the circumstances of the
+ coordinate system the file is already in.
+ This option only changes the *description* of the points.
+ It does not reproject them in any way.
+ Use a combination of <option>--a_srs</option> and
+ <option>--t_srs</option> to do perform reprojection of the file.
+ </para>
+ </formalpara>
+ </example>
+
+ <example>
+ <title>File splitting</title>
+
+ <screen>
+$ las2las in.las --split-mb 10
+ </screen>
+
+ splits the file into the required number of output-n.las files.
+ Other filters or operations may also be applied to the operation in
+ combination with splitting.
+ Each outputted file will have its extents and point counts properly set.
+
+ <screen>
+$ las2las in.las --split-pts 100000
+ </screen>
+
+ splits the file into the required number of output-n.las files with
+ 100000 points each in them.
+ Other filters or operations may also be applied to the operation in
+ combination with splitting. Each outputted file will have its extents
+ and point counts properly set.
+
+ <formalpara>
+ <title>note</title>
+ <para>
+ <option>--split-mb</option> and <option>--split-pts</option>
+ will not work exactly with <option>--min-offset</option>.
+ <option>--min-offset</option> will take the minimum offsets of
+ <emphasis>the entire file</emphasis>,
+ not each individual file that is a result of the split.
+ </para>
+ </formalpara>
+ </example>
+
+ <example>
+ <title>VLR addition</title>
+
+ <screen>
+$ las2las in.las --add-vlr CUSTOM_VLR 42 "A VLR description" "myfile.ext"
+ </screen>
+
+ adds a new VLR with name CUSTOM_VLR and an ID of 42.
+ "myfile.ext" can either be a location to a file to read to write into
+ the VLR, or properly escaped text that will be inserted directly into
+ the VLR.
+
+ <formalpara>
+ <title>warning</title>
+ <para>
+ VLRs have a size limitation of 65536 bytes.
+ Files that are read or escaped arguments that are larger than 64k
+ in size will cause an error to be thrown.
+ Automatic truncation will not happen.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>note</title>
+ <para>
+ If you attempt to add VLRs with an ID of 34735, 34736, or 34737, your
+ VLR will not be added.
+ This is because libLAS expects to manage the GeoTIFF keys for you.
+ You should use the SRS handling facilities if you need to set GeoTIFF
+ keys instead of attempting to overwrite them directly.
+ </para>
+ </formalpara>
+ </example>
+
+ <example>
+ <title>VLR removal</title>
+
+ <screen>
+$ las2las in.las --delete-vlr CUSTOM_VLR 42
+ </screen>
+
+ removes all VLRs from in.las when writing the new output.las file.
+ </example>
+
+ <example>
+ <title>Adding color from an image</title>
+
+ It is possible to use las2las to set RGB color information from an image
+ and set it on the points.
+ This requires a rewrite of the file and in some cases will require
+ changing both the format and point-format of the file.
+
+ The following example takes the <filename>input.las</filename> file,
+ sets its format to <literal>1.2</literal>,
+ and sets the point format to <literal>3</literal>
+ so it can store color information.
+ It also re-orders the color bands to have the 3rd band in the image be
+ red, 1st band be green, and second band be blue.
+ Additionally, the color values are then multiplied by the
+ <option>--color-source-scale</option> factor or 256 to rescale the 8 bit
+ image data to 16 bit color data.
+
+ <screen>
+las2las -i input.las \
+ --color-source image.img \
+ -o output.las \
+ --file-format 1.2 \
+ --point-format 3 \
+ --color-source-scale 256 \
+ --color-source-bands 3 1 2
+ </screen>
+
+ <formalpara>
+ <title>note</title>
+ <para>
+ If the coordinate system of <filename>image.img</filename> is not the
+ same as the input coordinate system of the LAS file, you should use
+ GDAL VRTs to cause the image to be warped and reprojected as part of
+ the read process.
+ See
+ <ulink url="http://www.gdal.org/gdal_vrttut.html">GDAL Virtual Format Tutorial</ulink>
+ for more detail.
+ </para>
+ </formalpara>
+
+ <formalpara>
+ <title>warning</title>
+ <para>
+ <ulink url="http://www.gdal.org">GDAL</ulink>
+ support must be enabled for this to work.
+ </para>
+ </formalpara>
+ </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