Upgraded from TBC 2.81 to 3.7, I have two job files of the same job taken from two different controllers , one was shifted 80mm onto found property beacons by means of site calibration, the other not, just picked up topo shots.
When bringing into TBC, the shifted file gets converted to the "imported files project coordinate system", however when bringing in the second file, it picks up the 2 different coordinate systems, I tell it to Keep the existing project definition, it then trys to merge the grid control points common to both jobs.
If you merge the points it averages them out, not acceptable, if not then it shifts them 80mm as well, also not acceptable.
No matter what I do it either merges and averages out my grid control or duplicates the grid control, with one set being shifted 80mm out.
TBC 2,81 only used to shift the observations, not the grid control.
How do I import the second job file so that only the observations shift, not the grid control?
Here are the links to the two job files and the control file
https://dl.dropboxusercontent.com/u/16999220/TBC%20query/surv-2894.job
https://dl.dropboxusercontent.com/u/16999220/TBC%20query/surv-2894cw.job
https://dl.dropboxusercontent.com/u/16999220/TBC%20query/surv-2894.csv
Any help will be much appreciated
I imported surv-2894.job and kept the data collector definition. I fixed the coordinate for the PRS. I then imported the surv-2894cw.job file and kept the data collector definition. The only flag I received was for 693 which was an out-of-tolerance as-staked point. The coordinates stored in both files matched each other. FYI - I did import keeping the project definition first and received the 0.081m flag.
Thanks for trying, I noticed that if you reversed the order you import the two job files, the problem does not occur, looks a bit buggy to me.
