Hi,
I have imported RTC360 scan data which has been aligned in the field on Field360.
I have handful of scan targets coordinated amongst about 24 scan targets used to assist in positioning scans together.
I imported a control file into Cyclone along with the scan data. Although not all coordinated targets have been identified... I have about 3 out of 7 coordinated scan targets in the registration, although cannot seem to get Cyclone to identify all.
I have tried using all the options on Advanced Auto-Add Constraints (2, 3 and 'all').
Anyone else had this issue?
Importing RTC360 data & Control not aligning
- kamac93
- I have made <0 posts
- Posts: 7
- Joined: Tue Nov 06, 2018 8:01 am
- 5
- Full Name: Kamil Machaj
- Company Details: RM Surveys
- Company Position Title: Surveyor
- Country: Australia
- Linkedin Profile: No
-
- I have made 50-60 posts
- Posts: 50
- Joined: Wed Oct 25, 2017 9:33 am
- 6
- Full Name: Matthias S
- Company Details: TPI
- Company Position Title: 3D-Team Coordinator
- Country: Germany
- Linkedin Profile: No
- Has thanked: 13 times
- Been thanked: 6 times
Re: Importing RTC360 data & Control not aligning
Maybe the targets dont match the tolerance threshold you can define under "Preferences -> Registration -> Auto-Add Constraint Tolerance" (Default is 9mm)
- pburrows145
- V.I.P Member
- Posts: 2152
- Joined: Wed Sep 12, 2007 9:16 am
- 16
- Full Name: Paul Burrows
- Company Details: Leica Geosystems Europe
- Company Position Title: Scanning Solutions Manager - Europe
- Country: UK
- Linkedin Profile: Yes
- Location: UK
- Has thanked: 109 times
- Been thanked: 123 times
Re: Importing RTC360 data & Control not aligning
Also, have the vertexes been extracted for the control? Are they accurate? Do they exist in the control space? Do the names of the targets in the control file match the targetID's?
-
- V.I.P Member
- Posts: 643
- Joined: Mon Aug 11, 2008 4:13 pm
- 15
- Full Name: James Rye
- Company Details: Merrett Survey Partnership
- Company Position Title: Spatial Analyst
- Has thanked: 28 times
- Been thanked: 69 times
Re: Importing RTC360 data & Control not aligning
Yes. The last two projects with the RTC360 have been a big problem to accurately register. It's because the tilt sensor isn't accurate enough (at 3 minutes is it?). The scans aren't auto-aligned well enough and some of them are still coming into Cyclone way off level (though it's the subtly tilted ones that are hardest to correct). In the field, we tried waiting for 10 seconds at each setup prior to scanning and even using a proper tripod and levelling the thing. In the preview window, everything looks great, but once imported and checked, it's clear that it's not aligned nicely. You need to colourise each scan a different color in the scanworld explorer and then create thin slices to identify the problem scans. The tighter you can get the registration, the better the fit will be at the control points.Anyone else had this issue?
We partially solve the issue by using targets and then manually adding cloud constraints using visual alignment. But, you can still see 5mm to 1cm of misalignment between scans, so we have to use the 3 point pick method......for each scan. Otherwise, at distances of say 50m, you can see 2-3cm of data misalignment. This can propagate through your network.
In practice, if you want accurate registration, you need LOTS of control points, and some want to be just outside your survey area. Target placement is also key, if they are all in a line then the data could fit at the control points but still be tilted badly away from them.
As you cannot fine scan control targets in the field, you need a field sketch/notes so that you can locate them in the scan data. Then you need to add in the target name and height. Are you adding the control points into the registration? or are you registering the data and then fitting to the control in a separate registration?
I don't want to name them, but the hire company that we have used have also advised us that getting tight registrations with the RTC360 is a problem and you start to see other people on the forum having issues also.
Like the BLK360, this scanner might seem to be simple and easy to use, but I think you are far better off using a proper surveying instrument like the P40 or the ever trusty C10 - a scanner that was certainly built to be reliable and built to last.
- landmeterbeuckx
- V.I.P Member
- Posts: 1616
- 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: Importing RTC360 data & Control not aligning
get a vz400i or a z&f and your problems will be solved
- stevenramsey
- Global Moderator
- Posts: 1937
- Joined: Sun Aug 12, 2007 9:22 pm
- 16
- Full Name: Steven Ramsey
- Company Details: 4DMax
- Company Position Title: Technical Specialist Scanning
- Country: UK
- Skype Name: steven.ramsey
- Linkedin Profile: Yes
- Location: London
- Has thanked: 30 times
- Been thanked: 72 times
- Contact:
Re: Importing RTC360 data & Control not aligning
For my own interest I would love to dig deeper in to the issues your having. Having been registering RTC data for over 18 mouths now and can honestly say I have never had your issue bar the few scans that arrive on the Tablet tilted when the VIS lost track which is very easy to fix. There seems to be two questions here, Registering together RTC data where you say they are miss aligned (please ignore the tilt sensor in this aspect) then you say that it doesn't match to control which is the only way to get scanners like this in to the real world. Levelling the instrument on a tripod will make no difference at all (don't get me started on the whole Scan and Go)Jamesrye wrote: ↑Fri Jun 14, 2019 1:57 pmYes. The last two projects with the RTC360 have been a big problem to accurately register. It's because the tilt sensor isn't accurate enough (at 3 minutes is it?). The scans aren't auto-aligned well enough and some of them are still coming into Cyclone way off level (though it's the subtly tilted ones that are hardest to correct). In the field, we tried waiting for 10 seconds at each setup prior to scanning and even using a proper tripod and levelling the thing. In the preview window, everything looks great, but once imported and checked, it's clear that it's not aligned nicely. You need to colourise each scan a different color in the scanworld explorer and then create thin slices to identify the problem scans. The tighter you can get the registration, the better the fit will be at the control points.Anyone else had this issue?
We partially solve the issue by using targets and then manually adding cloud constraints using visual alignment. But, you can still see 5mm to 1cm of misalignment between scans, so we have to use the 3 point pick method......for each scan. Otherwise, at distances of say 50m, you can see 2-3cm of data misalignment. This can propagate through your network.
In practice, if you want accurate registration, you need LOTS of control points, and some want to be just outside your survey area. Target placement is also key, if they are all in a line then the data could fit at the control points but still be tilted badly away from them.
As you cannot fine scan control targets in the field, you need a field sketch/notes so that you can locate them in the scan data. Then you need to add in the target name and height. Are you adding the control points into the registration? or are you registering the data and then fitting to the control in a separate registration?
I don't want to name them, but the hire company that we have used have also advised us that getting tight registrations with the RTC360 is a problem and you start to see other people on the forum having issues also.
Like the BLK360, this scanner might seem to be simple and easy to use, but I think you are far better off using a proper surveying instrument like the P40 or the ever trusty C10 - a scanner that was certainly built to be reliable and built to last.
So would love to dig in to your workflow settings and process I'm not sure I have had a job that has been mathematically and visually worse than a few mm (note only C2C) with jobs between 50 and 1600 scans in them
- gsisman
- V.I.P Member
- Posts: 898
- Joined: Fri Oct 07, 2016 1:51 pm
- 7
- Full Name: Steve Long
- Company Details: Montgomery County DOT _ MD
- Company Position Title: Land Survey Supervisor
- Country: United States
- Skype Name: gsisman1
- Linkedin Profile: Yes
- Has thanked: 767 times
- Been thanked: 149 times
Re: Importing RTC360 data & Control not aligning
I can't really speak to Cyclone, but I know that when you bring in RTC data from Field 360 you basically have one tie registration to the previous scan, or two or three if you have branches of scan runs. You have to create a lot more cross link cloud to cloud links in Reg 360 in order to Tighten up the registration. And a lot of these you may need to three point pick- depending on the environment. The outdoor scans or indoor ones with little or no Vertical and horizontal planes (i.e. Parking Garages) in them are difficult in my opinion than just running through a regular building. I'd like to see an advanced processing class offered online for Register 360 that handles problem data and how to deal with it efficiently.Jamesrye wrote: ↑Fri Jun 14, 2019 1:57 pmYes. The last two projects with the RTC360 have been a big problem to accurately register. It's because the tilt sensor isn't accurate enough (at 3 minutes is it?). The scans aren't auto-aligned well enough and some of them are still coming into Cyclone way off level (though it's the subtly tilted ones that are hardest to correct). In the field, we tried waiting for 10 seconds at each setup prior to scanning and even using a proper tripod and levelling the thing. In the preview window, everything looks great, but once imported and checked, it's clear that it's not aligned nicely. You need to colourise each scan a different color in the scanworld explorer and then create thin slices to identify the problem scans. The tighter you can get the registration, the better the fit will be at the control points.Anyone else had this issue?
We partially solve the issue by using targets and then manually adding cloud constraints using visual alignment. But, you can still see 5mm to 1cm of misalignment between scans, so we have to use the 3 point pick method......for each scan. Otherwise, at distances of say 50m, you can see 2-3cm of data misalignment. This can propagate through your network.
In practice, if you want accurate registration, you need LOTS of control points, and some want to be just outside your survey area. Target placement is also key, if they are all in a line then the data could fit at the control points but still be tilted badly away from them.
As you cannot fine scan control targets in the field, you need a field sketch/notes so that you can locate them in the scan data. Then you need to add in the target name and height. Are you adding the control points into the registration? or are you registering the data and then fitting to the control in a separate registration?
I don't want to name them, but the hire company that we have used have also advised us that getting tight registrations with the RTC360 is a problem and you start to see other people on the forum having issues also.
Like the BLK360, this scanner might seem to be simple and easy to use, but I think you are far better off using a proper surveying instrument like the P40 or the ever trusty C10 - a scanner that was certainly built to be reliable and built to last.