Version 2018 of FME supports LAZ 1.1, 1.2, 1.3 but not LAZ 1.4 that was released on https://laszip.org/
Page 1 / 1
A lot of LIDAR users are now using LAS 1.4 that has large benefits over older LAS versions ... and it would be great FME supports the new compression LAZ 1.4 format
see : https://www.usgs.gov/faqs/how-do-i-access-usgs-lidar-data-laz-14-format
I tried with FME 2018.1 beta build 18462 ... and it's not yet supported
message from FME :
LAS writer: Compression is not currently supported for point format 7. The file will not be compressed. To enforce a point format that supports compression, change the version to 1.4-legacy-compatible or earlier
It's not great to go to 1.4-legacy compatible ... as if we do so, we loose information from the LAS 1.4 format
I guess FME is using liblas ? ... found this info on https://liblas.org/
As of 2018, libLAS has been replaced by the PDAL project and it is in hibernation or maintenance mode. libLAS does not provide support for LAS or LAZ 1.4, which PDAL does
As a workaround you could use las-tools in a systemcaller to do the decompression and / or compression.
Thanks for the workaround ... it will help waiting it to be in next FME release with LAZ 1.4 support
Hi @mriedo, our very latest FME 2018.1 betas now have support for LAZ 1.4. Download the beta here to try it out!
I tried it out ! It works great. You guys are incredible. Thanks so much !
Hi @mriedo, our very latest FME 2018.1 betas now have support for LAZ 1.4. Download the beta here to try it out!
I tried it out ! It works great. You guys are incredible. Thanks so much !
Hi @mriedo, our very latest FME 2018.1 betas now have support for LAZ 1.4. Download the beta here to try it out!
After detailed analysis from Martin Isenburg who developped LAZ compression, there seems to be 2 problems with the FME implementation of LAZ 1.4
(1)
Unpopulated extended_number_of_points_by_return
(2) Extended
classification codes disappear / get remapped.
Could you please get in touch with Martin at info@rapidlasso.com for more information or send me a contact person ?
Hi,
Unpopulated extended_number_of_points_by_return
(2) Extended
classification codes disappear / get remapped.
After detailed analysis from Martin Isenburg who developped LAZ compression, there seems to be 2 problems with the FME implementation of LAZ 1.4
(1)
Unpopulated extended_number_of_points_by_return
(2) Extended
classification codes disappear / get remapped.
Could you please get in touch with Martin at info@rapidlasso.com for more information or send me a contact person ?
Hi,
Unpopulated extended_number_of_points_by_return
(2) Extended
classification codes disappear / get remapped.
After detailed analysis from Martin Isenburg who developped LAZ compression, there seems to be 2 problems with the FME implementation of LAZ 1.4
(1)
Unpopulated extended_number_of_points_by_return
(2) Extended
classification codes disappear / get remapped.
Could you please get in touch with Martin at info@rapidlasso.com for more information or send me a contact person ?
The problem 1 was solved in last beta version 18154
The problem 2 was not a bug ... but a bad manipulation on my side
So you can SAFEly use FME to compress/decompress LAZ 1.4
Thanks SAFE !!!
Hi,
The problem 1 was solved in last beta version 18154
The problem 2 was not a bug ... but a bad manipulation on my side
So you can SAFEly use FME to compress/decompress LAZ 1.4
Thanks SAFE !!!