Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Re-saving LAS file removes meta-data (.las .laz) #515
Comments
|
Indeed, CC doesn't handle LAS meta-data at all. We use libLAS (for now), but I don't know how easy to extract or push these pieces of information when loading and saving a file. I'll see what I can do, otherwise I'll add a warning message as suggested. |
dgirardeau
self-assigned this
Mar 4, 2017
dgirardeau
added the
enhancement
label
Mar 4, 2017
|
I've updated the online 2.9 beta version: the 'Spatial Reference System' (SRS) of the LAS file is now saved as meta-data and exported (if available) when saving the cloud as a new file. I'm just not sure that the SRS contains everything... Can you test it on your side and see if any important stuff is missing? |
|
Note that I uploaded the wrong version yesterday ;). It's should now be ok. |
dbworth
commented
Mar 8, 2017
|
Great. Thanks for the feedback! |




dbworth commentedMar 3, 2017
Thanks for the great open-source tool!
Current Behavior
When I open a .las file in CloudCompare and then immediately re-save the cloud as a .las file, lots of the meta-data is removed with no warning.
For example, if the .las file was georeferenced with a datum (e.g. "this is my location in the world"), this is removed and this affects processing files for GIS applications.
Expected Behavior
The header and meta-data should be written back out again, the same.
Steps to Reproduce
To verify this you need a geo-tagged LiDAR cloud from the DEM section here: https://earthexplorer.usgs.gov/
I can upload a sample file somewhere if you like.
For the original file, use the
lasinfotool (http://lastools.org/download/LAStools.zip) to view the meta-data. Then load the .las file in CloudCompare and re-save it. Uselasinfoagain to see the meta-data has been changed.Below is included a full screen dump.
Context/Comments
I'm not sure what LAS library is being used. Perhaps at a minimum, CloudCompare should warn "stripping LAS meta-data".
A nice example is MeshLab that when you re-save a mesh file, it prompts you for Binary VS. ASCII, Color Vs. no-color, etc.
Your Environment
Windows 7 64-bit.
CloudCompare 2.8 beta
.
This is the meta-data of original file
.
This is the meta-data of the file re-saved with CloudCompare