Closed spolloni closed 4 years ago
I find laspy's File object a bit more convenient to work with
I'm interested to hear what's missing in PDAL's Python API. I am unfortunately the designer of both APIs 😄 laspy's interface is just arrays too, or am I missing something?
@hobu thanks for responding so promptly!
The convenience is admittedly selfish, as I was hoping not to rewrite several existing functions that expect File
instances as argument -- and will call, say, somefile.return_num
instead of somearray['ReturnNumber']
.
With that said, I do find laspy's syntax a bit more elegant in that it feels more pythonic and object-oriented, though I guess that's a matter of taste. I enjoy being able to pass around a self-contained object having all attributes easily accessible, including everything in somefile.header
.
I am very new to PDAL's python API, however, so my take is probably biased.
Closing for now. Please reopen if there will be more discussion on the topic.
I find laspy's
File
object a bit more convenient to work with than the structured arrays obtained frompipeline.arrays
. I am trying to avoid the following workflow:by not writing any intermediate files to disk. Is this currently possible?