One of my surveyors is attempting to process some baselines in TBC and is having a tough time as TBC will not allow him to use the multiple occupations. Does anyone have any first hand knowledge on processing in TBC.
Thanks,
Lwilliams
L-
During the import (raw data, RINEX, ephemeris), your repeat obs need to be identified as the same point, prior to processing. The hard part is getting the points squared away (copious notes). There is probably an easier way to do it but I collect data on a point one day, say point # 101 and the next time I collect data on it I'll call it 1001. Then during the import, I scroll down to point 1001 and edit the point to 101. TBC will then process as the same point.
Hope this helps.
I will always call point 100 point 100. No matter how many times it is occupied. That way the processing will be seemless.
I had a guy go out and he used a different number each time he sat on a point. Boy did that take some time to sort out. It was something I didn't think I needed to explain; now I know better. TBC works well adjusting a network. It's faster and easier than TGO.
Static obs, sure, but fast-static with the DC or RTK to be post-processed; Survey Pro doesn't allow for duplicate point names. If it does, I need to be educated as to how. Surveys performed with the DC write the set-up data(ant. model/ant. height, point name, etc.) to the raw file in the receiver and makes it a much easier import process, at least it works for me.
Unless of course you hit all of your points once in one job file, then create a new job for repeat obs. But I like to stake out the previously tied point for comparison.