The co-ordinates used for geo-referencing a TLS point cloud were not accurate and as a result, there is a mismatch between and the TLS data and an imported UAV point cloud (imported in OBJECTS>POINTCLOUDS). Is there any way to co-register the TLS data to the UAV data.
The UAV data cannot be moved in any way as it is closely linked to its trajectory file.
I thought I could just consider the UAV data like any other scan position and compute the planes followed by MSA by keeping the UAV cloud fixed. This is not possible as the 'Extract plane patches' is apparently not applicable to the point clouds in OBJECTS>POINTCLOUDS.
Is there a better way to co-register these datasets or a workaround in RiScan Pro 2.6.2
Thanks for your replies!
Co-registering an entire project with an imported point cloud in RiSCAN PRO
- landmeterbeuckx
- V.I.P Member
- Posts: 1615
- Joined: Tue May 01, 2012 5:19 pm
- 11
- Full Name: Lieven Beuckx
- Company Details: Studiebureau Beuckx
- Company Position Title: Owner
- Country: Belgium
- Linkedin Profile: Yes
- Has thanked: 183 times
- Been thanked: 548 times
Re: Co-registering an entire project with an imported point cloud in RiSCAN PRO
make a new scanposition and import the uav data.
make the planes and try msa with the scan of the uav data fixed.
backup your project file first for safety
make the planes and try msa with the scan of the uav data fixed.
backup your project file first for safety
- Jerzy Frydel
- I have made 10-20 posts
- Posts: 15
- Joined: Tue Sep 07, 2010 1:34 pm
- 13
- Full Name: Jerzy Jan Frydel
- Company Details: Polish Geological Institute
- Company Position Title: senior specialist
- Country: Poland
- Linkedin Profile: No
Re: Co-registering an entire project with an imported point cloud in RiSCAN PRO
Or perhaps you shall try manual 'Coarse registration' via selection of 4+
corresponding points in pointclouds from both sources.
This might deliver satisfactory results.
Depending on the data, accuracies of even ~1cm are possible to achieve this way.
corresponding points in pointclouds from both sources.
This might deliver satisfactory results.
Depending on the data, accuracies of even ~1cm are possible to achieve this way.