Hi,
I'm trying to copy classification from one point cloud to the other due to broken extra bytes. Everything is working fine until I want to save the data as LAS 1.4.
1. when I try to save as LAS 1.4 I can't select the Riegl extra bytes (echo width, amplitude, scalar fields) and therefore they are also not saved.
2. when I try to save as LAS 1.4 then it saves it as LAS 1.2.
3. Everything is fine when I save it as LAS 1.2 (including extra Bytes).
Can sombody confirm that this is not working with the 2.10-alpha realease? Or am I doing something wrong (I tought maybe I miss something because I cant choose between save to LAS 1.3 and LAS 1.4).
thanks and best regards
benjamin
las 1.4 export with extra bytes
Re: las 1.4 export with extra bytes
The 'LAS 1.3 and 1.4' option is not using the same library than the default filter. Clearly this additional filter was meant to load FWF data from 1.3+ or 1.4 data).
The default filter is using PDAL. I guess it doesn't save LAS 1.4 file if this is not needed? I'm not the author of this filter, therefore I'm not 100% sure about this.
The default filter is using PDAL. I guess it doesn't save LAS 1.4 file if this is not needed? I'm not the author of this filter, therefore I'm not 100% sure about this.
Daniel, CloudCompare admin
Re: las 1.4 export with extra bytes
ok understood thanks. You are right I think. afaik you have to tell pdal the minor version and the point dataformat for LAS 1.4 with
--writers.las.minor_version=4 //for LAS 1.4
--writers.las.dataformat_id=6 //point format 6 for returns above 7 returns
--writers.las.minor_version=4 //for LAS 1.4
--writers.las.dataformat_id=6 //point format 6 for returns above 7 returns
Re: las 1.4 export with extra bytes
hi,
i was able to compile cc in windows "successfully" with option_use_gdal and option_pdal_las. Unfortunately I cannot load LAS files in CC.
The console writes when I try to open a file:
[09:08:09] [I/O] CC has caught an exception while loading file 'C:/temp/04_trafo_neu/1_01_20151109_151109_225733_1_originalpoints - Cloud2122323423.las'
[09:08:09] [I/O] Exception: bad allocation
attached are my cmake settings. I tried tu use osgeo4w pdal. I hope this is possible.
Do I also have to install the QLAS_FWF_IO_Plugin to be abel to read LAS?
thanks
i was able to compile cc in windows "successfully" with option_use_gdal and option_pdal_las. Unfortunately I cannot load LAS files in CC.
The console writes when I try to open a file:
[09:08:09] [I/O] CC has caught an exception while loading file 'C:/temp/04_trafo_neu/1_01_20151109_151109_225733_1_originalpoints - Cloud2122323423.las'
[09:08:09] [I/O] Exception: bad allocation
attached are my cmake settings. I tried tu use osgeo4w pdal. I hope this is possible.
Do I also have to install the QLAS_FWF_IO_Plugin to be abel to read LAS?
thanks
- Attachments
-
- cmake2.jpg (166.22 KiB) Viewed 2916 times
-
- cmake1.jpg (134.96 KiB) Viewed 2916 times
Re: las 1.4 export with extra bytes
Hum, this error seems to be related to a shortage of memory actually (not a missing third party library or unsupported format/version).
How big is your file?
How big is your file?
Daniel, CloudCompare admin
Re: las 1.4 export with extra bytes
hmm it is 1.6GB.
I could open it in your build 2.10 alpha version.
I also tried a smaller 400mb file, did also not work.
I could open it in your build 2.10 alpha version.
I also tried a smaller 400mb file, did also not work.
Re: las 1.4 export with extra bytes
i have to check tomorrow at my computer but I'm pretty sure it is 1.7.2 maybe 1.7.1
Re: las 1.4 export with extra bytes
the PDAL version is 1.7.2 (it is the osgeo4w version) I used for building CC
Re: las 1.4 export with extra bytes
On my side I compiled CC with version 1.6. I don't know if it is related to the problem?
Daniel, CloudCompare admin