while collecting opus data can you also begin a traditional ground survey with the tsc3 that you used to initialize the r10 ? (s6) ?
Absolutely. We do it daily. Not with the R10, but with our R8. The only time I do static shots with the R10 is when I lose cell service and I normally connect to the grid via CORS rather than OPUS in TBC.
You "may" depending on the method you're using to set your control, require a scale, rotate, and translate after the fact though in conjunction with some other adjustment of data.
Typically, because we have RTK on both, if we boot the R8, it's logging data and we set pairs of control points and run between them. Correct and adjust at the end, send off to OPUS, and if it's close, like under 50', a straight translation at one point (because your bearings aren't changing enough to notice) to the OPUS point and voila!
[USER=228]@Loyal[/USER] is correct when he says that EVERY transformation to OPUS SHOULD require a rotation, but when the rotation is in decimals of arc seconds, like in the second decimal of arc seconds, I don't sweat it. Works VERY well for connecting VERY large areas together with VERY minimal distortion, so long as everything stays on the grid.
We run R8 S7 TSC3 jobs in the same file all the time. If you import your data into TBC you can crunch it all together in about 5 minutes, provided you don't have tons of errors.
It used to be that Trimble had an issue with using the Data Collector and meshing it with a projection. If you were projected to state plane (doesn't have to be state plane, it's about any coordinate system) and you take a shot with the TS, the data collector would not reduce the distance to a state plane distance so the coordinate was a bit off. There was a update some years ago that fixed it and it works now, however, it's like anything, check, check, check........
My suggestion is give it a try, if you have a state plane you can use with a nice distortion say .3' in 1000' (you might try a nearby zone if you are in UTM 10, try UTM 9) and just check things out, set up your GPS in the zone, shoot a couple of points, set the TS up and check them and make sure they work together.
Always work with elevations in the TS and the GPS, and be very careful with stake-out points. When you shoot a stake-out point with an autonomous position and then move it to an OPUS position the state-out point will stay. Trimble considers a stake-out point to have the same value as the ark of the covenant.
The only way I've found to get them to move is to remove the state-out function from them which can be done in the points list in project explorer, they appear in a list in the bottom, select the ones you want to change, and under properties it will allow you to remove the stake-out tag from them. Then they will move with a recompute.
MightyMoe, post: 410142, member: 700 wrote: It used to be that Trimble had an issue with using the Data Collector and meshing it with a projection. If you were projected to state plane (doesn't have to be state plane, it's about any coordinate system) and you take a shot with the TS, the data collector would not reduce the distance to a state plane distance so the coordinate was a bit off. There was a update some years ago that fixed it and it works now, however, it's like anything, check, check, check........
My suggestion is give it a try, if you have a state plane you can use with a nice distortion say .3' in 1000' (you might try a nearby zone if you are in UTM 10, try UTM 9) and just check things out, set up your GPS in the zone, shoot a couple of points, set the TS up and check them and make sure they work together.
Always work with elevations in the TS and the GPS, and be very careful with stake-out points. When you shoot a stake-out point with an autonomous position and then move it to an OPUS position the state-out point will stay. Trimble considers a stake-out point to have the same value as the ark of the covenant.
The only way I've found to get them to move is to remove the state-out function from them which can be done in the points list in project explorer, they appear in a list in the bottom, select the ones you want to change, and under properties it will allow you to remove the stake-out tag from them. Then they will move with a recompute.
I've been using Trimble since 98 and never experienced that problem. We selected Trimble because it handled Datum and Coordinate systems better than anyone else at the time.
I did leave Trimble for a while and came back. Perhaps this was an issue during that time...
thebionicman, post: 410154, member: 8136 wrote: I've been using Trimble since 98 and never experienced that problem. We selected Trimble because it handled Datum and Coordinate systems better than anyone else at the time.
I did leave Trimble for a while and came back. Perhaps this was an issue during that time...
It was a long time ago, may have been prior to 98, it may also have been the differences in the total stations, I didn't have any trimble TS's back then, but I did use the DC with my Topcons. It was a vexing problem for a while but they did fix it.
Kris Morgan, post: 410107, member: 29 wrote: Absolutely. We do it daily. Not with the R10, but with our R8. The only time I do static shots with the R10 is when I lose cell service and I normally connect to the grid via CORS rather than OPUS in TBC.
You "may" depending on the method you're using to set your control, require a scale, rotate, and translate after the fact though in conjunction with some other adjustment of data.
Typically, because we have RTK on both, if we boot the R8, it's logging data and we set pairs of control points and run between them. Correct and adjust at the end, send off to OPUS, and if it's close, like under 50', a straight translation at one point (because your bearings aren't changing enough to notice) to the OPUS point and voila!
[USER=228]@Loyal[/USER] is correct when he says that EVERY transformation to OPUS SHOULD require a rotation, but when the rotation is in decimals of arc seconds, like in the second decimal of arc seconds, I don't sweat it. Works VERY well for connecting VERY large areas together with VERY minimal distortion, so long as everything stays on the grid.
+1
