So I am somewhat new to both these programs (TBC/Access and Starnet). I have been given more responsibility at work and have had the chance to familiarize myself with these programs more and more. So far my Starnet experience has been great, but my TBC experience not so much and especially working with these programs together.
Work Flow Goal
My original goal was to be able to view my data from multiple data collectors in TBC, since it has a nice GUI to pan and investigate and then do my adjustment in Starnet as an export of TBC (using the StarNet/TBC Traverse Sheetstyles or .JXML and then using a Starnet conversion utility). It seems I cannot get this to work after data is uploaded into TBC. When I run a report from TBC or export as JXML from TBC, I just get a bunch of Coordinate Values that are set to free and no observation data (For Example, C 12 100000 100000 * *).
Current Solution
I did find a solution to getting my observation data into Starnet, but I could not do it from TBC it had to be done from Access (exported as a .JXML) and then converted using a StarNet utility.
Questions & Background
So I have a few question for people on this forum, who may be more familiar with TBC and Starnet.
I believe one of the reasons I cannot get this to work is because of the way TBC treats conventional data. I am a true believer of observations, but it seems that TBC isn't. Allow me to explain...
I use the following steps to get my Data into TBC.
- Conventional Data is collected by Trimble Access with a Trimble S6 and TSC2/3 Data Collectors
- The control is keyed into Access via N/E grid coordinates (Adjusted or Unadjusted)
- The data is then uploaded into TBC by copying the Job File from the TSC2/3 and then imported using the import command.
Okay so once when all this is said and done I have all my project data, control, observations and coordinates in TBC. So I know the observations are there!
This next part is the part that really gets me. If i go into TBC and and modify the coordinates of my control all my observations change, not the coordinates of my points.
So my first question is...How does this even make sense? Is this a setting in my TBC or is this just how TBC is? Is it my data collection method? Import Method? Is there a way I can change TBC to hold my observations instead of the coordinates?
My second question is...Does anyone else currently use the workflow method I described above and get successful observation data? If so then how?
I often perform least squares adjustments on job files in both tbc and starnet. They don't necessarily give the same results as they operate somewhat differently. Depends on the network and for DTM work I generally use starnet for my control network and then run the whole job through TBC.
To get starnet dat files out of TBC, use the job report generator found under the survey tab in TBC. Select the starnet style sheet from this trimble site:
http://www.trimble.com/globalTRLTAB.asp?nav=Collection-32914 . This procedure will let you convert a job file to a dat file in tbc.
As to your question regarding changing control coordinates and what results from that, I think that will take some one on one time at the computer to see what buttons you are pushing to know for sure what you are doing.
Clearcut,
Yes, I know this. I believe I explained earlier I have done this, but when I do this method my observations (such as a ground shot) do not get recorded, only my coordinates are. The only observations the Sheet files exports is an open or closed traverse from control to control. Even then if I adjust the coordinate value in TBC from my StarNet adjustments my connected ground shots do move in TBC....my observations do. That shouldn't be.
This is what happens when I export from TBC as a Job XML or Sheet Style.
C 7 1844474.405 6821850.948 1604.565 * * *
C 4 1844744.777 6822425.062 1615.290 * * *
C 31 1844492.381 6822363.755 1610.509 * * *
C 100 1844742.739 6822429.616 1615.310 * * *
C 101 1844474.539 6821854.550 1604.567 * * *
C 102 1844476.884 6822395.945 1613.457 * * *
C 103 1844476.905 6822395.980 1613.453 * * *
C 104 1844478.835 6822389.555 1609.992 * * *
C 105 1844476.463 6822394.559 1610.110 * * *
# C ........(For All Observations, but no observation Data)
##
.DELTA OFF
A 31-7-4 106-45-03
DV 31-7 509.613 90-52-28 5.715/3.900
DV 31-4 258.949 88-52-43 5.715/6.000
##
This is Trimble Access .JXML export
C 14 1845065.99100 6819699.82800 1554.66500 *** '60D-TP14
C 16 1845214.92700 6819073.59600 1539.19500 *** '60D-TP16
C 18 1845339.29700 6818532.02300 1528.91500 *** '60D-TP18
DM 16 283-22-40.90 643.9434 91-23-21.74 5.239/5.130 '60D-TP16
DM Auto0001 158-16-04.88 16.1799 87-31-14.51 5.239/6.000
DM 16 110-26-00.89 259.8817 88-45-45.81 5.399/5.130 '60D-TP16
DM 6293 183-53-14.65 79.6304 90-46-07.91 5.399/6.000 'T36INRCP
DM 6294 211-27-56.32 25.4272 88-28-21.93 5.399/6.000 'BSW
DM (For All Observations, No Coordinate Values)
I don't have a lot of time, and it's a little complicated, but TBC stores coordinate values in multiple locations. I bring in the control points as a separate file like start and end stations. Delete the coordinate values out of the job file after importing. Expand the points area and expand each point. Keep only the points in your control file. The value has the source file in parantheses next to it. If you have RTK vectors to control your traverse, import that job file. The base coordinate would be the only coordinate value remaining.
Coordinates can be hidden in many places. In the job file, expand each observation and single backsight and look for coordinates.
Pay attention to the flag pane. This can tell you what points to look at. It's not a complete answer, just a guide.
Also, TBC isn't always good about disabling unused observations. You may have to go to the optical spreadsheet to figure out the unused and disable them.
Also, you only need to drag and drop files into TBC. No need to use the importer.
There's a lot to the program and it's become my favorite conventional adjustment but there's a lot of little things to look for.
