Lidar data

Comments

9 comments

  • Avatar
    Wilbert van den Broek

    I forgot to mention that I succesfully imported .LAX in Cloudcompare but had to rescale it on import in CloudCompare in order for it to work. I could then export a e.57 that RC would read but the results are incorrect and messy.

    0
    Comment actions Permalink
  • Avatar
    Jasper Mink

    Hi Wilbert,

    What kind of results did you get in RC when you've imported the converted .e57 file from CloudCompare?

    In the past I've imported .e57 files in RC to create polygon meshes but the results were always so-so because of the relatively low point density of the lidar point cloud.

    Any idea what the density of the .LAZ file is?

     

    Met vriendelijke groet ;)

    0
    Comment actions Permalink
  • Avatar
    Wilbert van den Broek






    0
    Comment actions Permalink
  • Avatar
    Wilbert van den Broek

    I don't know why but step number two was uploaded last :-(

    Anyhow, you can see my progress in importing the e57 data in RC.

    First I import it in cloud compare, scaled it than exported it and import in RC.

    As you can see the cloud data in RC looks real 'thin' like there are a lot less points.

    After that mesh that is generated is real bad. Same issues I'm having with this method in

    Recap Pro.

    Any thoughts?

    0
    Comment actions Permalink
  • Avatar
    Wilbert van den Broek

    I also noticed that the imported laser data in RC is treated as if there was a single camera viewpoint.

    I don't know if this is correct.

    0
    Comment actions Permalink
  • Avatar
    Not_Nick

    Hi Wilbert

    The single point for the camera, and where the software decided to create that single camera point will cause some issues.

    I went through a similar thing, converting an unstructured point cloud to a sudo .e57 file. I found it lost lots of my data points. It was almost like it was using line of sight from the camera position to decide what should be modeled. So any objects in the way it totally disregarded the potential data collected behind them. I guess that could be fixed by setting up more camera positions when it structures the points but I couldn't find a way to do that.

    The impression I got was unstructured data is a bit tricky and will need more development before its supported by RC.

    0
    Comment actions Permalink
  • Avatar
    Oswaldo Sequera

    Hi all

    You need to export from the software you used to register the scans. Use PTX format. As far as my knowledge goes, you can't convert from LAS/LAZ/PTS/XYZ to PTX in such a manner that CR will reconstruct the scanned area. When you export PTX from the software used for point cloud registration, it includes data related to the scanner stations, which is not included in the other formats.

    Cheers!

    0
    Comment actions Permalink
  • Avatar
    Wilbert van den Broek

    Hye guys thanks for your replies, I will have a chat with our data supplier to come with a solution.

    0
    Comment actions Permalink
  • Avatar
    hlee

    Hi all,

    I'm trying to do the exact same thing: converting unorganized point cloud to .e57. Does anyone have ideas how to do this?

    I have a Velodyne VLP-16 LiDAR, I use MATLAB to read and save point cloud in .ply format. Then I use CloudCompare to convert .ply to .lax, then to .e57. But RC failed to import this file.

    Any thoughts?

    1
    Comment actions Permalink

Please sign in to leave a comment.