Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Stef

Pages: [1]
1
General / Re: Import Laserscan data -registration lost
« on: October 17, 2021, 02:22:04 PM »
Just want to say thank you for all these testing, I am actually trying to fit a registered laser scan cloud inside Metashape, but all this seems to go a little too far. I've been reading through all the posts, I've been lost a couple times, and my conclusion is: Metashape is treating laser scans as photogrammetry and that's not good at all, since it's a whole different thing based on direct measurements and not triangulations.

For the times to come, until Metashape is ready (because I'm sure it will be), I'll keep doing the way I do it right now: E57 file from Drone and E57 file from Scanner, both in CloudCompare for the alignment.

Thank you to Dieter and Paulo for the in-depth tests and to Alexey for the support.

2
Thanks a lot for what you're doing Alexey.

Basically, I need to complete the terrestrial scanner cloud with the data collected from air, for rooftop, balcony and such. Laser scanner point cloud is already produced and registered, I do not want Metashape to build it again from dome photos, it would not make sense. I just want Metashape to take the scanner cloud as it is and align it with photogrammetry cloud. Since a year I'm doing this align operation using CloudCompare, which is a powerful tool but not so stable and reliable, so I think it is time to learn how to do it in Metashape.

The process you listed seems like complicated, I'll read carefully every step and I'll try to apply it to my case. I'll be back with results as soon as possible.

EDIT: Thank you for pointing me to the linked thread 'Import Laserscan data -registration lost'. That is exactly my same situation, I'm going to read it all and see what the ending conclusions are, if any.
In my mind Metashape should not try to align or position anything when dealing with stations, it is counter-productive because the (relative) position in the 3D space is already given. Metashape should just take it and eventually transform coordinates to align and match it to its georeferenced photogrammetry cloud.

3
Thank you Alexey, I'm actually trying to follow the helpdesk article and I'll be back maybe tomorrow with the results.

I'm most doubtful about what will happen to the scanner registration. Because Cyclone REGISTER 360 already did the registration of the stations and it is very precise (globally ±3mm), so the thought of scanner spherical photo aligniment is scary, to say the least.

4
Hello, I've been widely searching for this subject but found not a proper solution, so I'm starting a new topic.

My purpose is to merge drone photogrammetry with terrestrial scanner point cloud, pretty much an actual theme. I'll list what I am trying to do:

  • create 2 chunks, one for the photogrammetry data, and the other one for the scanner data
  • in chunk #1 load all the drone photos and produce the dense cloud, referenced by GCPs in use
  • in chunk #2 import the scanner point cloud, unreferenced (Local System), using a .E57 file published by Cyclone REGISTER 360
  • align and merge chunks

I was expecting to simply pick common points and all come in place at once. Evidently I'm thinking wrong, because 'Align chunks' function is greyed and I can't execute it, probably because chunk #2 is not referenced.
The only thing about this argument I've found so far is this article from the helpdesk.

Isn't enough to have one chunk referenced for the alignment to happen?
I have a drone and a Leica RTC360, what is the procedure I should rely on, to merge everytime the work of both instruments in Metashape?

Pages: [1]