[pdal-commits] [PDAL/PDAL] f85693: Add range filter

[GitHub]

  Branch: refs/heads/add-passthrough-filter
  Home:   https://github.com/PDAL/PDAL
  Commit: f85693fdc7257b20d72da9e9e2ac6ed90856c3ad
      https://github.com/PDAL/PDAL/commit/f85693fdc7257b20d72da9e9e2ac6ed90856c3ad
  Author: Bradley J Chambers <brad.chambers at gmail.com>
  Date:   2015-02-03 (Tue, 03 Feb 2015)

  Changed paths:
    A doc/stages/filters.sieve.rst
    M doc/stages/index.rst
    M filters/CMakeLists.txt
    A filters/range/CMakeLists.txt
    A filters/range/RangeFilter.cpp
    A filters/range/RangeFilter.hpp
    M include/pdal/Filters.hpp
    M src/StageFactory.cpp
    A test/data/filters/range_classification.xml.in
    A test/data/filters/range_z.xml.in
    A test/data/filters/range_z_classification.xml.in
    M test/unit/CMakeLists.txt
    M test/unit/apps/pcpipelineTest.cpp
    A test/unit/filters/RangeFilterTest.cpp

  Log Message:
  -----------
  Add range filter

This could obviously be more complicated, but as it is, I think it's a nice
alternative to the Python filters. The documentation, sample pipeline, and unit
tests should adequately explain the current feature set (basically
multi-dimensional, min/max/exact value criteria for passing points through to
the output buffer).