I've used CC for some time now, but had apparently never come across data provided as BIN files. I recently saw that annotated data had recently been made available for the Dublin City lidar collect [1]. Specifically, I started by looking at tile T_315500_234500_NE.
I was interested in exporting this data to use elsewhere in a more standard format, but I've been running into problems. I'm not sure if it's user error at this point, or if it's bug worthy, in which case I'm happy to file a ticket on GitHub. I am running the pre-built OSX binary for CC v2.10.2.
What I initially tried was to export a single building, (the data is hierarchically arranged as described at the link and evidenced in the sample dataset). Unfortunately, the building is further decomposed into parts such as roof/window/door. These children do not seem to be automatically merged and exported with the parent object. I then attempted to select the parent and all children, and then Edit->Merge. The first time I did this, I actually got two datasets, those points belonging to the parent and those points belonging to the children. I'm not sure what I did differently in that first attempt, because every attempt to merge since then has actually resulted in a hard crash. It seems no matter what I try I cannot export as a merged dataset all points belonging to a part and its children.
I'll be happy to provide more detailed steps to reproduce, if it seems like what I'm trying should be working, and is not just a case of user error. In the end, should I be able to export a part of a BIN file that includes all of the children parts?
[1] https://v-sense.scss.tcd.ie/DublinCity/
Help exporting nested structures in BIN file
Re: Help exporting nested structures in BIN file
Ah! I didn't know they released this dataset in the BIN format of CloudCompare :D
Anyway, it must be clearly confusing for CC as this use case (clouds below clouds) is clearly not 'standard'.
And I can confirm the crash. For now, if you want to do that, you should move all the children to the same level as the parent (and also children of children, etc.) before merging them.
And we should try to be more robust to this in the future, even though it might be a little tricky!
Dont' hesitate to file a bug on github, it will be useful.
Anyway, it must be clearly confusing for CC as this use case (clouds below clouds) is clearly not 'standard'.
And I can confirm the crash. For now, if you want to do that, you should move all the children to the same level as the parent (and also children of children, etc.) before merging them.
And we should try to be more robust to this in the future, even though it might be a little tricky!
Dont' hesitate to file a bug on github, it will be useful.
Daniel, CloudCompare admin