These are chat archives for PDAL/PDAL

24th
May 2018
Luigi Pirelli
@luipir
May 24 16:12
Hi... my first message. I know that the common use fo pdal is ingesting a pipeline... btw I'm exploring it's functions before via command line. I'm not sure how to parse a text file (2 line header, space separator, plus las data + 2 column more) using the diriver readers.text
it's obscure to me how to pass options via command line
any simple example how to pass e.g. options like "skip", "header", "separator" and so on?
Adam Steer
@adamsteer
May 24 19:58

Hi @luipir - I found the path of least resistance is to begin at pipelines. You can still pass command line options in.

What have you tried so far? can you give an example of something that didn’t work?

Adam Steer
@adamsteer
May 24 20:07
…but you thought should have?
Mateusz Loskot
@mloskot
May 24 20:21
@luipir I have never used readers/writers directly myself (I stick to API and very basic pdal queries for metadata while testing), but if you look at the last command here https://pdal.io/workshop/exercises/batch_processing/batch-processing.html, you will see --filters.reprojection.out_srs option. That is 'path' to the out_srs option as listed on https://pdal.io/stages/filters.reprojection.html#options
@luipir Now, by the basic rule of patterns, I'd risk expectation that --readers.text.skip should work, etc.
Luigi Pirelli
@luipir
May 24 20:56
tnx @mloskot and @adamsteer so I'll try --<class>.<type/factory>.<option> I remember I did some similar test, but probably adding --options
Adam Steer
@adamsteer
May 24 20:59
Hi @luipir no problem. Would a specific document about how to mix and match pipelines and command line options have helped - ie a cheatsheet or similar? I also went to the workshop but was not as fast as @mloskot at finding an example!
Luigi Pirelli
@luipir
May 24 21:02
works thanks :)
I would PR something into the documentation
Adam Steer
@adamsteer
May 24 21:06
yup that was my plan also :) PDAL/PDAL#2035