Hi Spencer,
Thanks for your question. I’ve actually thought about updating Wb’s LAS writer to use LAS v1.4 several times in the past. The reader already handles v1.4 without issue. The problem is that my lidar processing workflow does use some software that cannot handle v1.4, specifically the plas.io point cloud visualization software. That’s the main reason why I haven’t updated it as of yet. Also, the LAS reader/writer is custom code built into Wb itself (I wrote it) and I’d like to as much as possible offload file i/o to libraries where I don’t need to maintain as much. For example, for LAZ support, Wb uses a Rust library for reading and writing that data format. I’ve thought about doing the same for LAS files. I sure would love to do that for raster data i/o too, but sadly GDAL isn’t Rust code and can’t be directly embedded into the Wb codebase…but one can dream of a life where I don’t spend endless hours trying to support the countless forms of a GeoTIFF file! Anyhow, I hope that answers your question.
Regards,
John
--
You received this message because you are subscribed to the Google Groups "WhiteboxTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
whiteboxtool...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/whiteboxtools/4044afb3-d6ec-49a4-8662-91e84c648f94n%40googlegroups.com.