[pdal] Filters.assign: not all filters applied

[Eric Robeck]

Andrew,

I was busy using PDAL for batch exporting, so I just got back to this now.
I see my mistake- that should be '0.50'. I hadn't noticed it before because
PDAL didn't throw an error. However, when I make that the LAST assignment,
I get the same error. So this:

    {
      "type":"filters.assign",
      "assignment":"Classification[:]=0",
      "assignment":"Window[:]=12",
      "assignment":"Slope[:]=0_50"
    },

returns this:

PDAL: filters.assign: Invalid value for argument 'assignment'.

As I said before, my PDAL instance must be skipping all but the last
assignment, so it didn't throw an error until I made it the last
assignment. Even in the instance above, the Classification and Window
assignments are not made.

Even when I strip out everything but the reader, writer, filter and assign
stages (as below), PDAL still ignores the Slope value error and fails to
assign all but the Red value. I am using PDAL 1.7.1. This isn't an
impediment to my workflow, as I got around it using multiple stages with
single assignments.

Thanks for your help!

Regards,
Eric

{
  "pipeline":
  [
    {
      "filename":"C:/data/forest_park/forest_park_orig_dtm.laz",
      "type":"readers.las",
      "count":100000
    },
    {
      "type":"filters.ferry",
      "dimensions":"=>Window, =>Slope"
    },
    {
      "type":"filters.assign",
      "assignment":"Classification[:]=0",
      "assignment":"Window[:]=12",
      "assignment":"Slope[:]=0_50",
      "assignment":"GpsTime[:]=3000",
      "assignment":"Red[:]=255"
    },
    {
      "type":"writers.las",
      "minor_version":"4",
      "compression":"true",
      "extra_dims":"Window=uint8, Slope=float",
      "filename":"c:/data/forest_park/filters_assign_test.laz"
    }
  ]
}


On Mon, Apr 16, 2018 at 9:20 AM, Andrew Bell <andrew.bell.ia at gmail.com>
wrote:

> Eric,
>
> I can't recreate the issue with the assignment problems.  I'm a little
> suspicious of your test because you should get an error with the following
> assignments:
>
>       "assignment":"Classification[:]=0",
>       "assignment":"Window[:]=12",
>       "assignment":"Slope[:]=0_50",
>       "assignment":"GpsTime[:]=3000",
>       "assignment":"Red[:]=255"
>
> That's because "0_50" isn't a valid value to assign for Slope.  When I run
> a pipeline with a similar construct, I get:
>
> $ bin/pdal pipeline test.json
> PDAL: filters.assign: Invalid value for argument 'assignment'.
>
> Please try to reproduce your issue using a pipeline with limited stages.
>
>
> On Sat, Apr 14, 2018 at 9:50 PM, Andrew Bell <andrew.bell.ia at gmail.com>
> wrote:
>
>> A change that was made to filters.ferry for version 1.7 broke dimension
>> creation. I'll fix shortly.
>>
>> On Sat, Apr 14, 2018, 9:34 PM Howard Butler <howard at hobu.co> wrote:
>>
>>>
>>>
>>> > On Apr 14, 2018, at 8:15 PM, Eric Robeck <erobeck at gmail.com> wrote:
>>> >
>>> > Thanks, everyone! I'll get back to work and stop spamming your inboxes.
>>>
>>> On the contrary, keep it up. Your documentation of your learning journey
>>> with the tools is helping us find sticky spots that we can document,
>>> illustrate, and patch to make them work better.
>>>
>>> If you’re spamming us, we will let you know (privately).
>>>
>>> Howard
>>>
>>> _______________________________________________
>>> pdal mailing list
>>> pdal at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/pdal
>>
>>
>
>
> --
> Andrew Bell
> andrew.bell.ia at gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pdal/attachments/20180418/31de99f5/attachment.html>