[pdal] how to work around issue 225

Steven M. Ottens steven at minst.net
Tue Apr 8 07:57:09 PDT 2014


Howard Butler schreef op 4/8/2014 4:02 PM:
> UUID in PDAL is really about which driver produced the dimension, not so much the dimension itself. This is kind of confusing and may be removed soon.
>
> You have to normalize your data so the "apparent schema" that's presented to pgpointcloud is always the same. The way to do this is to
>
> a) use a filters.scaling to re-offset all your data to the same offset. Because your data are 0.01, you should be able to find a scale/offset combo that can work for all the files
>
> b) use a filters.selector to explicitly select the set of dimensions you want to load. This set needs to be the same for every file that is loaded
>
> c) Load the first file
>
> d) set the pc_id Option to 1 for all of the subsequent files to override the schema
>
Setting the filters.scaling to X: offset:0 scale 0.01 and Y: offset: 
300000 scale 0.01 seems to do the trick. It is happy crunching again, 
even through the LAZ files with a different schema as the initial file. 
Should be done in a couple of days....

Thanks again
Steven



More information about the pdal mailing list