Hello
We had a crew head out of state and begin a survey using the 'here' command when they set up the base.
Later, we sent another crew up to the same site. When I went to the TBC job, I noticed that someone else in my office had began a calibration. Hoping to avoid problems, I found the original .dc file and re-loaded it on the data collector they were taking. This crew set up the base on a point surveyed by the previous crew, but not the 'here' point. He also set additional control points to which we ran level loops.
Later a third crew finished out the job. He took the data collector of the 2nd surveyor, which had been downloaded, but not deleted.
Now I have an OPUS solution, Vert. control points etc., but when I try to calibrate, it tries to say that the control points are not global. (The 'here' point and control points set out by the second crew.) It suggests that I disable the grid data, which I do. But it still won't let me calibrate to those points.
Has anybody seen something similar?
Thanks
Nathan
I don't do a calibration in situations like you presented. I just change the coordinates (lat/long) for the "Here" point and anything shot subsequent to that will change. Any cogo or hand entered points will not. I do all this in the data collector.
I have not tried it on a file loaded to a second data collector. It may not work that way.
James
For what you are describing, I wouldn't calibrate that job.
You have established the control, so there would be no reason to.
Maybe I'm missing something, but there needs to be coordinates to calibrate into. Coordinates that someone else established and you need to tie, and you can't get them to work to their metadata, or there is no metadata.
Otherwise, set-up a projection, tie into CORS, adjust the control and you're good to go.
As long as the dc file hasn't been downloaded, erased out of the data collector then reloaded into the datacollector you should be good to process the control points and put them into the job file, then import the dc file and it should shift to the good points. But, no calibration should be done on the project. There's no reason to take good data and rubber sheet it.
Nathan
I seldom do calibrations so take what I say with a grain of salt. It sounds to me that you need to fix your control points as global rather than grid or local. I don't know what datum you are working in so watch out that TBC gets the coordinates correct because it might apply a datum transformation to the global coords.
Like I said I'm probably all wet so take my advice at your own peril :'(
I guess I need to give a little more info. The calibration I hope to do is a vert. calibration. I will hold the OPUS location and elevation, but need to calibrate so that the elevations throughout the project are consistant. We have run level loops through the control points.
If I import the origional .DC file into TBC, I can run the calibration function. But when I bring in the subsiquent .dc files, it won't let me run the calibration function becasue it says that the control points weren't derived from global data. It suggests that I disable the local and grid data and try again. When I go into properties for those points, I can disable the local and grid data, but it still won't let me run the calibration function.
Have you checked the Point Derivation Report for the points you want to use in the calibration after you disable the grid? I'm curious to see how the points are being calc'ed after getting rid of that data.
It seems to me that you are on the right track. I would think that importing the first DC file, then the second DC file, and then getting rid of the coords imported into the second DC file is the way to go. At least that is the I would have approached it...
make sure your loaded geoid model covers that area.
