Merge branch 'doc'

doc/development/compilation/dependencies.rst

@@ -104,15 +104,6 @@ Point Cloud read/write support.
 .. note::
     MSVC should only require the oci.lib and oci.dll library and dlls.
 
-Hexer
-..............................................................................
-
-`Hexer`_ is a library with a simple `CMake`-based build system that
-provides simple hexagon gridding of large point sets for density surface
-generation and boundary approximation. It can be obtained via github.com at
-https://github.com/hobu/hexer It is used by :ref:`filters.hexbin` to output
-density surfaces and boundary approximations.
-
 Nitro
 ..............................................................................
 
@@ -186,7 +177,6 @@ used by :ref:`writers.tiledb` and :ref:`readers.tiledb`.
 .. _`KyngChaos`: http://www.kyngchaos.com/software/unixport
 .. _`Conda Forge`: https://anaconda.org/conda-forge/pdal
 
-.. _Boost: http://www.boost.org
 .. _GDAL: http://www.gdal.org
 .. _Proj.4: http://trac.osgeo.org/proj
 .. _GeoTIFF: http://trac.osgeo.org/geotiff

doc/development/compilation/unix.rst

@@ -287,6 +287,7 @@ location of our test file. This is similar to the :ref:`same command
     :alt: Setting the arguments for lasinfo
 
 
+.. _optional-libraries:
 
 Configure :ref:`Optional Libraries <dependencies>`
 ------------------------------------------------------------------------------

doc/development/overview.rst

@@ -10,8 +10,9 @@ PDAL Architecture Overview
 
 PDAL is a set of applications and library to facilitate translation of point
 cloud data between various formats.  In addition, it provides some facilities
-for transformation of data between various geometric projections and
-manipulations and can calculate some statistical, boundary and density data.
+for transformation of data between various geometric projections
+and can calculate some statistical, boundary and density data.  PDAL also
+provides point classification algorithms.
 PDAL provides an API that can be used by programmers for integration into their
 own projects or to allow extension of existing capabilities.
 
@@ -25,13 +26,14 @@ PDAL reads data from a set of input sources using format-specific readers.
 Point data can be passed through various filters that transform data or create
 metadata.  If desired, points can be written to an output stream using a
 format-specific writer.  PDAL can merge data from various input sources into a
-single output source, preserving attribute data where supported by the input and
-output formats.
+single output source, preserving attribute data where supported by the input
+and output formats.
 
 .. image:: pipeline.png
 
 The above diagram shows a possible arrangement of PDAL readers, filters and
-writers, all of which are known as stages.  Any merge operation or filter may be
+writers, all of which are known as stages.  Any merge operation or filter
+may be
 placed after any reader.  Output filters are distinct from other filters only in
 that they may create more than one set of points to be further filtered or
 written.  The arrangement of readers, filters and writers is called a PDAL
@@ -175,7 +177,8 @@ pipeline.
     implement the no-argument version.  Whether to place initialization code
     at this step or in prepared() or ready() (see below) is a judgement call,
     but detection of errors earlier in the process allows faster termination of
-    a command..
+    a command.  Files opened in this step should also be closed before
+    returning.
 
 3) void addDimensions(PointLayoutPtr layout)
 
@@ -222,9 +225,9 @@ is called once for each point view to be processed by the stage.
 3) void done(PointTablePtr table)
 
     This function allows a stage to clean up resources not released by a
-    stage’s destructor.  It also allows other termination functions, such
-    a closing of databases, writing file footers, rewriting headers or
-    closing or renaming files.
+    stage’s destructor.  It also allows other execution of termination
+    functions, such a closing of databases, writing file footers,
+    rewriting headers or closing or renaming files.
 
 Streaming Stage Execution
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~