Geoscience Reference
In-Depth Information
"Red": "208",
"Green": "206",
"Blue": "187"
}
}
An interesting concept in PDAL is the pipeline . It links subsequent operations
that are described in an XML file. Each operation is represented by a stage , being
either a reader, writer or filter. The idea is similar to the operations described in XML
files on GDAL virtual formats (see Sects. 2.6 and 11.3 ) . Pipelines provide maximum
flexibility to the user, yet avoid building utilities custom to individual needs with
arbitrary options, filters, etc. With the XML file shown below, we can use pdal
pipeline to obtain the same result as for the example on las2las we provided
in Sect. 15.3.1 .
pdal pipeline -i pdal.xml
In this simple example, there is only a single filter ( filters.cache ). Subse-
quent operations including cropping or mosaicing data can easily be combined by
nesting filters in the XML file.
<? xml version ="1.0" encoding="utf-8"?>
<Pipeline version ="1.0">
<Writer type="drivers.las.writer">
<Option name="filename">
st-helens_pdal.laz
</Option>
<Option name="compression">
true
</Option>
<Filter type="filters.cache">
<Reader type="drivers.las.reader">
<Option name="filename">
st-helens.las
</Option>
<Option name="spatialreference">
EPSG:26919</Option>
</Reader>
</Filter>
</Writer>
</Pipeline>
A special type of filter is the filters.pclblock filter. It enables a link to
the Point Cloud Library (PCL). This is another C++ library released under the terms
of the BSD license 13 with a focus on advanced algorithms on 2D and 3D data.
13 http://pointclouds.org
 
 
Search WWH ::




Custom Search