Traverse Adjusting Procedures

View Only

A I posted 12-04-2023 05:49

Hi all,

I'm relatively new to using TBC and have been mostly teaching myself the software through this forum and videos on YouTube. Definitely super handy and improves a lot of our capabilities and data processing speed in the office. Recently I went out on a pretty insignificant project and had some extra time so I decided to run a loop. The project definitely didn't need one, but was mostly looking to have some data to mess around with. The loop was run close enough that there probably wouldn't need to be an adjustment especially for a project of this scope, but I've been messing around with it regardless so that I'm ready to tackle it when the situation arises.

That being said, I've had mixed success with this feature in the past. Usually, some combination of merging points or shooting them as check shots is the fix. The problem I have is usually with getting the software to identify the last leg of the loop. Often times it will stop short of the last leg and not want to connect the line back to the place of origin, even though there is a shot on that point. Sometimes merging the points fixes it, sometimes it doesn't. In this case I've tried pretty much all I can think of and cannot get the loop to "close" on the starting point. Again, the project is not contingent on a loop or adjustment being run, but it was more of giving myself some practice material.

The specific issue I am running into here is that as soon as I hit the 3rd leg, the last leg is not connecting back to the starting point as mentioned above.

I have a dropbox link attached with all of the files exported from my data collector. If anyone has any insights or any ways to help, please let me know.

Dropbox Link

Thanks in advance,

A.I.

A I posted 12-04-2023 14:05

Back again to answer my own post after messing around some more. Combining all of my redundant shots together seemed to allow TBC to see the loop. I guess the fix from here on out will likely be just combining points in the office, not sure why the field shot on my first setup as a check shot wasn't viable for the loop. Also not sure why it interpreted my first backsight of the loop as a mean angle, but if it works, it works.

Robert Hoy posted 12-07-2023 10:46

Maybe show screen grabs of your issue? One thing is you need to use the same Point Name with Trimble for duplicate observations of points. So if you start a traverse with points 1 and 2, you can't names those last 2 points 9 and 10 and have it see something to adjust. This of course necessitates you bringing in the JOB file into TBC and not an exported CSV file.