Getting .laz file into Rhino?

Rhino currently supports .e57 but not .las (uncompressed) or .laz (compressed). I looked for an online converter but most go the other way (e57 to las). Aside from using QGIS (which I really dislike), anyone have an easy solution?

Hey Mitch, try CloudCompare.

_
c.

Hi Clement,

Yeah, I thought about that after I posted above - I used to have it installed on a computer somewhere, but not any more. I guess that’s one way to go, I was hoping for some kind of automatic converter though.

Hi Mitch, the most automatic (local) way to do this is to create a *.bat file for CC. If you don’t want to download it again i can offer to convert it.

_
c.

Hi @Helvetosaur

The latest Heron version (package manager) has a laz importing component.
The advantage of laz/las files that points keep classifications.

4 Likes

FWIW, I’ve added the file format request to RH-64850 - Support .las/.laz file IO for LiDAR data (not open for public viewing).
-wim

5 Likes

Hi,
I have been experimenting with this. It appears that the laz file can be improted but de E57 is much more effective when it comes to handling large datasets. Does anyone know the limits in iwch it is reasonnable to work with the heron approach ?

Hi @raoufdjema15

Importing large LAZ files with Heron can take some time. A 200Mb file around 12 minutes. If you just need a clipped part of the LAZ file las2las is the most efficient way. Part of the 200MB file just 12 seconds.

Clipping is done before unpacking. This saves time! It has been developed by Martin Isenburg.
He has put some nice video’s on his youtube chanel:

If you want to use the E57 format Volvox has some tools for it.

For working with point-clouds inside grasshopper I have the best experience with cockroach.

Hey,

Thanks for your answer, i appreciate =)

We are using large LAZ files (more then 1 gb) to reconstitute large urban and landscape areas.

I’ve been experimenting with different file sizes and i come to the same conclusions.
Handling larger files (more then 300 mb) in LAZ format seems a bit too much to handle for rhino.

In the other hand, using e57 makes it really easy in display. The problem with e57 is the data loss.

I think that a good approach is to pre-process the LAZ file using cloud compare and then export pointclouds in e57 format. I know that there is also a plugin called rhino city / rhino terrain that might be able to handle all of this directly in rhino.

I ll be trying cockroach, heron and volvox. Will give and update if i get something interesting.

What data are you losing going from laz to e57?

Hi,

Mainly the pointcloud classification data

1 Like