[pdal] how to work around issue 225

[Steven M. Ottens]

Howard Butler schreef op 4/8/2014 4:58 PM:
> On Apr 8, 2014, at 9:57 AM, Steven M. Ottens <steven at minst.net> wrote:
>> It is happy crunching again, even through the LAZ files with a different schema as the initial file.
> Your data is likely to be bunk if you are overriding the schema but loading data of different schemas.
I loaded a few LAZ files with different schema's using the scaling 
filter and a set PCID pipeline and they are at the correct location now 
(not so at the first attempt). So I assume this works (?)
>> Should be done in a couple of days....
>>
>> Did you cook up a queuing system? You should be able to run enough simultaneous pipelines to stomp your available i/o.
A very simple one: I divided the data in three folders and I have three 
simple bash scripts going through all three folders file by file. This 
way I keep 3 of my four cores busy and have the fourth available for 
other stuff (like checking if my data is in the correct spot ;)
Since I need to unzip the LAZ files anyway, I use a static output.xml 
which always takes /home/geodan/output.las and let the script unzip 
files to output.las and cleanup after import

script:

declare -i COUNT
COUNT=$( ls -l part1/*.laz | wc -l )
i=0
for file in ./part1/*.laz
do
   echo 'Volgende file: '
   echo $file
   pc2pc $file /home/geodan/output.las
   pdal pipeline output.xml
   rm /home/geodan/output.las
   mv $file ./gedaan/.
   let  "COUNT -= 1"
   let "i += 1"
   echo '##### ' $i ' bestanden gedaan, nog' $COUNT 'te gaan.... #####'
done