[pdal-commits] [PDAL/PDAL] 4ed1a6: Resolve some dangling references to deprecated ext...

[GitHub]

  Branch: refs/heads/1.5-maintenance
  Home:   https://github.com/PDAL/PDAL
  Commit: 4ed1a6c3b38cfc0b36a3e0cf28cc3f24c6bb853d
      https://github.com/PDAL/PDAL/commit/4ed1a6c3b38cfc0b36a3e0cf28cc3f24c6bb853d
  Author: Bradley J Chambers <brad.chambers at gmail.com>
  Date:   2017-04-17 (Mon, 17 Apr 2017)

  Changed paths:
    M doc/apps/translate.rst
    M doc/pipeline.rst
    M doc/stages/filters.outlier.rst
    M doc/stages/filters.pmf.rst
    M doc/workshop/exercises/analysis/denoising/denoise.json
    M doc/workshop/exercises/analysis/denoising/denoising.rst
    M doc/workshop/exercises/analysis/ground/ground-run-ground-only.txt
    M doc/workshop/exercises/analysis/ground/ground.rst
    M doc/workshop/exercises/analysis/ground/translate-run-ground-only.txt

  Log Message:
  -----------
  Resolve some dangling references to deprecated extract and classify options

extract and classify have been used in several filters, namely outlier and PMF.
With the release of PDAL v1.5, we removed these options, opting to always
classify points, and to force users to ignore or extract them as they see fit
in their pipelines.

The outlier filter's extract option can be replicated by adding a range filter
stage as shown following the outlier filter:

    {
      "type":"filters.range",
      "limits":"Classification![7:7]"
    }

The PMF filter's extract option can be replicated by adding the following range
filter:

    {
      "type":"filters.range",
      "limits":"Classification[2:2]"
    }

The intention here was to remove any ambiguity as to how individual filters
implement "extract", and to instead be explicit in the pipeline specification
as to how points are extracted.