Split PDAL into multiple packages

[hobu]

This PR starts on PDAL 2.6

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-trajectory because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-hdf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-tiledb because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-pgpointcloud because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-draco because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-arrow because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].
• pin_compatible should be used instead of pin_subpackage for libpdal-nitf because it is not a known output of this recipe: ['libpdal', 'pdal-trajectory', 'pdal-hdf', 'pdal-draco', 'pdal-tiledb', 'pdal-pgpointcloud', 'pdal-arrow', 'pdal-nitf', 'libpdal-all', 'pdal-split'].

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.