Registration in cyclone with scanpositions and RTK
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Registration in cyclone with scanpositions and RTK
Hi All
I have measured a scanning position with a totalstation and got the RTK position to the same scanning position.
Now my question is if it is possible to use the totalstation measurement of the scannerposition in the cyclone registration?
After the registration is done, i would like to translate the scaningstations upon the RTK measurement, there the geometry between the different scanstations is keept from the totalstation measurement.
Anyone who has any experience in this field?
I have measured a scanning position with a totalstation and got the RTK position to the same scanning position.
Now my question is if it is possible to use the totalstation measurement of the scannerposition in the cyclone registration?
After the registration is done, i would like to translate the scaningstations upon the RTK measurement, there the geometry between the different scanstations is keept from the totalstation measurement.
Anyone who has any experience in this field?
-
- V.I.P Member
- Posts: 537
- Joined: Mon Jun 16, 2014 1:45 pm
- 9
- Full Name: James Worrell
- Company Details: Bennett and Francis
- Company Position Title: Director
- Country: Australia
- Linkedin Profile: Yes
- Location: Brisbane, Queensland, Australia
- Has thanked: 14 times
- Been thanked: 87 times
- Contact:
Re: Registration in cyclone with scanpositions and RTK
If I understand correctly .. yes.
Did you also use targets? OR are you relying on cloud-to-cloud for orientation?
Either way you need to create "constraints" between the scans for the registration.
First step is to import your TS control to create a scanworld .. simple Pt,X,Y,Z type thing. Does your measured control include height of instrument - that is did you measure with a prism and smart handle on top of scanner and put that in as height of target? Or did you measure via normal traverse, and have a height of target off the ground? If ground, add to match the height of instrument - assuming you did standard setup on the scanner - so the centre of the scan is 0,0,0. StdSetup is 0,0,0 at scanner centre - you just need "control" to match.
Probably a few ways to tackle the next step - and someone more enlightened might have an easier way.
If you have targets - skip this bit - just use the target coordinates .. that is a different answer. Assuming no targets ..:
In each scan - create a vertex at 0,0,0 and add a Registration Label that matches it's control point ID - needs to match exactly - also case sensitive. (You could go -Z offset here to match the ground position as opposed to adding the instrument height in previous step)
How big is the site? Are you planning on using ground distance coordinates or grid/geodetic coordinates? Or are you looking to apply a scale factor to the rtk coordinates? I assume you haven't used a P40 here and applied a scale factor during scanning ..
We typically pick a scale point and calculate a scale factor .. to translate the GPS coords to ground.
Going with ground .. you should have a control scanworld with the control points matching the instrument centres on a local assumed system.
Create a registration.
Add the control scanworld.
Add the other scanworlds.
Auto-add constraints - target ID only. This should basically match up the scanner centre with your control by name. Now you haven't got a rotation for the scan unless you also used targets. Then you head into the cloud-to-cloud world .. visual align .. wizard .. take your pick. You can give this a lesser weight to ensure the total station values have a higher priority.
So once you have the cloud-to-cloud added - you have constraints for the centre and rotation from cloud .. You can auto-add cloud as well.
Freeze rego .. you are on local coords .. audit it.
Next - to get to a pseudo real world - albeit ground distance coordinates .. pick one of the RTK positions - probably near the middle (we usually aim for a permanent survey mark) .. calculate the azimuth to a second - prob furthest away .. you can then set coordinates by 2 points .. pick point 1 (middle) .. then 2 .. run the command .. type in coords .. type in bearing .. done.
Set default scan world coords .. save the coord system etc.
If you want to use RTK across the thing and try and stretch/shrink the data .. instead of TS control - use the RTK coords. You might put more weight on the cloud-to-cloud then and average the overall position. There is no nice way to do this and to be honest - never had to try.
Hope this helps.
Did you also use targets? OR are you relying on cloud-to-cloud for orientation?
Either way you need to create "constraints" between the scans for the registration.
First step is to import your TS control to create a scanworld .. simple Pt,X,Y,Z type thing. Does your measured control include height of instrument - that is did you measure with a prism and smart handle on top of scanner and put that in as height of target? Or did you measure via normal traverse, and have a height of target off the ground? If ground, add to match the height of instrument - assuming you did standard setup on the scanner - so the centre of the scan is 0,0,0. StdSetup is 0,0,0 at scanner centre - you just need "control" to match.
Probably a few ways to tackle the next step - and someone more enlightened might have an easier way.
If you have targets - skip this bit - just use the target coordinates .. that is a different answer. Assuming no targets ..:
In each scan - create a vertex at 0,0,0 and add a Registration Label that matches it's control point ID - needs to match exactly - also case sensitive. (You could go -Z offset here to match the ground position as opposed to adding the instrument height in previous step)
How big is the site? Are you planning on using ground distance coordinates or grid/geodetic coordinates? Or are you looking to apply a scale factor to the rtk coordinates? I assume you haven't used a P40 here and applied a scale factor during scanning ..
We typically pick a scale point and calculate a scale factor .. to translate the GPS coords to ground.
Going with ground .. you should have a control scanworld with the control points matching the instrument centres on a local assumed system.
Create a registration.
Add the control scanworld.
Add the other scanworlds.
Auto-add constraints - target ID only. This should basically match up the scanner centre with your control by name. Now you haven't got a rotation for the scan unless you also used targets. Then you head into the cloud-to-cloud world .. visual align .. wizard .. take your pick. You can give this a lesser weight to ensure the total station values have a higher priority.
So once you have the cloud-to-cloud added - you have constraints for the centre and rotation from cloud .. You can auto-add cloud as well.
Freeze rego .. you are on local coords .. audit it.
Next - to get to a pseudo real world - albeit ground distance coordinates .. pick one of the RTK positions - probably near the middle (we usually aim for a permanent survey mark) .. calculate the azimuth to a second - prob furthest away .. you can then set coordinates by 2 points .. pick point 1 (middle) .. then 2 .. run the command .. type in coords .. type in bearing .. done.
Set default scan world coords .. save the coord system etc.
If you want to use RTK across the thing and try and stretch/shrink the data .. instead of TS control - use the RTK coords. You might put more weight on the cloud-to-cloud then and average the overall position. There is no nice way to do this and to be honest - never had to try.
Hope this helps.
- James Hall
- V.I.P Member
- Posts: 220
- Joined: Tue Feb 02, 2010 5:13 pm
- 14
- Full Name: James E Hall
- Company Details: Dewberry Engineering Inc
- Company Position Title: Survey Technician - Cyclone Modeler
- Country: USA
- Location: Frederick, MD
- Has thanked: 5 times
- Been thanked: 37 times
Re: Registration in cyclone with scanpositions and RTK
In cyclone you can replace the Known Coordinate Scan world. The RTK coordinates or the Total station coordinates would be interchangeable.
Navigator window, file Import txt file. (.svy) It has formatting options you will have to play around with to get your Nothing, Easting and Units right.
Specify "Target ID" as you description field and cyclone will automatically ID the point and add it to the control space.
In register you would Remove the old (Known Coordinate file) and add the new one, then add constraints ID only.
This will update your Registration scan with the Total stations coordinates.
James,
Navigator window, file Import txt file. (.svy) It has formatting options you will have to play around with to get your Nothing, Easting and Units right.
Specify "Target ID" as you description field and cyclone will automatically ID the point and add it to the control space.
In register you would Remove the old (Known Coordinate file) and add the new one, then add constraints ID only.
This will update your Registration scan with the Total stations coordinates.
James,
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Re: Registration in cyclone with scanpositions and RTK
jamesworrell wrote: ↑Thu May 17, 2018 12:17 pm If I understand correctly .. yes.
Did you also use targets? OR are you relying on cloud-to-cloud for orientation?
Either way you need to create "constraints" between the scans for the registration.
First step is to import your TS control to create a scanworld .. simple Pt,X,Y,Z type thing. Does your measured control include height of instrument - that is did you measure with a prism and smart handle on top of scanner and put that in as height of target? Or did you measure via normal traverse, and have a height of target off the ground? If ground, add to match the height of instrument - assuming you did standard setup on the scanner - so the centre of the scan is 0,0,0. StdSetup is 0,0,0 at scanner centre - you just need "control" to match.
Probably a few ways to tackle the next step - and someone more enlightened might have an easier way.
If you have targets - skip this bit - just use the target coordinates .. that is a different answer. Assuming no targets ..:
In each scan - create a vertex at 0,0,0 and add a Registration Label that matches it's control point ID - needs to match exactly - also case sensitive. (You could go -Z offset here to match the ground position as opposed to adding the instrument height in previous step)
How big is the site? Are you planning on using ground distance coordinates or grid/geodetic coordinates? Or are you looking to apply a scale factor to the rtk coordinates? I assume you haven't used a P40 here and applied a scale factor during scanning ..
We typically pick a scale point and calculate a scale factor .. to translate the GPS coords to ground.
Going with ground .. you should have a control scanworld with the control points matching the instrument centres on a local assumed system.
Create a registration.
Add the control scanworld.
Add the other scanworlds.
Auto-add constraints - target ID only. This should basically match up the scanner centre with your control by name. Now you haven't got a rotation for the scan unless you also used targets. Then you head into the cloud-to-cloud world .. visual align .. wizard .. take your pick. You can give this a lesser weight to ensure the total station values have a higher priority.
So once you have the cloud-to-cloud added - you have constraints for the centre and rotation from cloud .. You can auto-add cloud as well.
Freeze rego .. you are on local coords .. audit it.
Next - to get to a pseudo real world - albeit ground distance coordinates .. pick one of the RTK positions - probably near the middle (we usually aim for a permanent survey mark) .. calculate the azimuth to a second - prob furthest away .. you can then set coordinates by 2 points .. pick point 1 (middle) .. then 2 .. run the command .. type in coords .. type in bearing .. done.
Set default scan world coords .. save the coord system etc.
If you want to use RTK across the thing and try and stretch/shrink the data .. instead of TS control - use the RTK coords. You might put more weight on the cloud-to-cloud then and average the overall position. There is no nice way to do this and to be honest - never had to try.
Hope this helps.
Hi James
First of all, thanks for your reply.
The orientation is given by C2C.
It includes a 360 prism on a smart handle, where the distance to the instrument is known, so that i have a known height of the instrument.
After i have none the prism measurement, i change that to my RTK antenna, so i have a global coordinate.
Do i have to go into each scan manually to create a new vertex? For some of this scanjobs i got 200 stations?
Isnt there some way, where i just adds them as constraints and can apply the txt coordinate file to all 200 at once?
And i use a leica p20 scanner with a max to 30m, so the quality should be really good.
But if i got 200 rtk measurements and want to use an least squares adjustment, this command wont apply?
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Re: Registration in cyclone with scanpositions and RTK
Oh, so basically i can just handle the station coordinate, as an target?James Hall wrote: ↑Thu May 17, 2018 3:30 pm In cyclone you can replace the Known Coordinate Scan world. The RTK coordinates or the Total station coordinates would be interchangeable.
Navigator window, file Import txt file. (.svy) It has formatting options you will have to play around with to get your Nothing, Easting and Units right.
Specify "Target ID" as you description field and cyclone will automatically ID the point and add it to the control space.
In register you would Remove the old (Known Coordinate file) and add the new one, then add constraints ID only.
This will update your Registration scan with the Total stations coordinates.
James,
So it should work, if i import the stationfile and apply it to the scanworld, by a constraint target, use the rtk file as homescanworld and give that one a minimal weight?
- James Hall
- V.I.P Member
- Posts: 220
- Joined: Tue Feb 02, 2010 5:13 pm
- 14
- Full Name: James E Hall
- Company Details: Dewberry Engineering Inc
- Company Position Title: Survey Technician - Cyclone Modeler
- Country: USA
- Location: Frederick, MD
- Has thanked: 5 times
- Been thanked: 37 times
Re: Registration in cyclone with scanpositions and RTK
Yes the total station coordinate comes in as a target vertex. Setting the wight on your constraints to .05 is what I would recommend. It is the lowest setting that will force a rotation translation and still has some wiggle room.
James,
James,
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Re: Registration in cyclone with scanpositions and RTK
Thanks! i will try it out!James Hall wrote: ↑Fri May 18, 2018 4:33 pm Yes the total station coordinate comes in as a target vertex. Setting the wight on your constraints to .05 is what I would recommend. It is the lowest setting that will force a rotation translation and still has some wiggle room.
James,
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Re: Registration in cyclone with scanpositions and RTK
Hi All
I have now scanned 13 stations with the pærism on top and measured to my prism, with a totalstation.
I import the scanstations as useal and import the measurements as a regular targetfile. I have checked the setting; Add verrtex to scanner location.
I create a registration but it cant match the targetfile with the scanlocations, even though, they have the same name (SW-001, SW-002 etc).
Can any of you guys make a quick video that shows the principe?
I have now scanned 13 stations with the pærism on top and measured to my prism, with a totalstation.
I import the scanstations as useal and import the measurements as a regular targetfile. I have checked the setting; Add verrtex to scanner location.
I create a registration but it cant match the targetfile with the scanlocations, even though, they have the same name (SW-001, SW-002 etc).
Can any of you guys make a quick video that shows the principe?
- James Hall
- V.I.P Member
- Posts: 220
- Joined: Tue Feb 02, 2010 5:13 pm
- 14
- Full Name: James E Hall
- Company Details: Dewberry Engineering Inc
- Company Position Title: Survey Technician - Cyclone Modeler
- Country: USA
- Location: Frederick, MD
- Has thanked: 5 times
- Been thanked: 37 times
Re: Registration in cyclone with scanpositions and RTK
Hello,
With each of your setups you needed to record a Instrument Height for your prism. I'm attaching images to illustrate the process.
Open your control file in Notepad. If there is a header delete it and if you are having problems with .txt importing change the extension to .svy.
Make sure your Northing and Easting are defined correctly in the import utility. 450LH,6944696.770,11868435.308,109.263,NS
451LH,6944505.230,11868299.270,105.407,NS
452LH,6944570.791,11868461.450,107.698,NS
453LH,6944621.873,11868248.679,103.526,NS
When you import your file and it is still not picking up the Target ID you can Manually assign them. You will need to set the HI for Each Target in the Control space. Each setup control space will have a vertex at the scanner head position. You will need to determine the offset between Prism and this vertex. This scanner position vertex also needs a Reg ID and HI applied to it.
Any vertex in Register can be constrained to another. If you can't get anything to work you can always select two vertexes and add a constraint by right clicking to pull up the menu.
With each of your setups you needed to record a Instrument Height for your prism. I'm attaching images to illustrate the process.
Open your control file in Notepad. If there is a header delete it and if you are having problems with .txt importing change the extension to .svy.
Make sure your Northing and Easting are defined correctly in the import utility. 450LH,6944696.770,11868435.308,109.263,NS
451LH,6944505.230,11868299.270,105.407,NS
452LH,6944570.791,11868461.450,107.698,NS
453LH,6944621.873,11868248.679,103.526,NS
When you import your file and it is still not picking up the Target ID you can Manually assign them. You will need to set the HI for Each Target in the Control space. Each setup control space will have a vertex at the scanner head position. You will need to determine the offset between Prism and this vertex. This scanner position vertex also needs a Reg ID and HI applied to it.
Any vertex in Register can be constrained to another. If you can't get anything to work you can always select two vertexes and add a constraint by right clicking to pull up the menu.
You do not have the required permissions to view the files attached to this post.
-
- V.I.P Member
- Posts: 200
- Joined: Mon May 05, 2014 11:19 am
- 9
- Full Name: Malte Holm
- Company Details: TLS
- Company Position Title: Surveyor
- Country: Norway
- Linkedin Profile: Yes
- Has thanked: 2 times
- Been thanked: 1 time
Re: Registration in cyclone with scanpositions and RTK
I tried, but when i do my registration, does my targets get the error of their own coordinate, because they a in a georefrenced system and my scanworlds is in a local. This seems pretty strange for me, doing to, it is the same exercise as useal.