Trimble Business Center

Hi all,

I am working on a traverse adjustment and I get distance errors as expected, but there is no angular adjustment happening at all. I'm not sure how to get TBC to recognize the angles between each leg. It knows the distance, how does it not know the angular errors? Very frustrating, if anyone has any input, would greatly help. It is only doing a distance adjustment which does not solve the problem. Attached is some more info but I'm not sure what to do. My colleague collected this data on Survey Pro and was exported using a .job file. I'm not sure how it can fail to calculate the angular misclosure. The entire report just has "?" for anything related to angles.

Thanks

------------------------------
A I
------------------------------

The issue is one of two things.  When I get this question, most of the time there is not a closed traverse.  in the image below, the traverse was started at point 2 backsighting 1.  The traverse was run around and the last angle was set at point 5 (same as 1) and turned to point 6 (same as 2).  I usually see people occupy point 4 and turn to 5 and end the survey there.  The closing angle is between points 5&6.  

The second issue that I see is that if you name a point as 1, it will always be point 1.  If you do have a closed traverse, try renaming the closing points to their original names.  In my example, I would have named point 5 as point 1, and point 6 as point 2.  When asked by the data collector if I wanted to average the points, I would have selected to store as another point.

------------------------------
Kris Fairley
Lead Support - Advanced Technology Group
AllTerra Central
Houston, TX
------------------------------

I've only done 2 or 3 traverses with TBC (I combine total station observations, RTK, and static - never need to do a traditional traverse as that is rather outdated with the dynamic Network adjustment of TBC), but with TBC you never use a "new" point name when observing a point that is already in your collector (though not sure if you did that).  Looks like you made an observation to your first setup point but didn't re-occupy it.

------------------------------
Robert Hoy
------------------------------