How often do you go and run a traverse some distance from the office and then return to the office hoping it is closed? Or you run an open traverse between two known points?
For a closed traverse it does not matter if you do not have a coordinate system.
First you need to have a data recorder set to record the normal data , a TS that can have FL and FR compensate the pointing errors, and its software able to compute a coordinate for every measured point and recorded with the point's conventional data.
I simply call up the IS station point with coordinate or if no point coordinate system add an arbitrary coordinate. I then add an artificial BS coordinate and temporary point number for the BS and point the TS to that BS target. The TS is then orientated to the BS and a coordinated point automatically generated for the BS from measuring. Then FS coordinate point recorded. I then use software to then Set out FS to record and visually see on screen the delta x,y, z discrepancies, before then setting out BS to record and see on screen the delta x,y, z discrepancies. Depending on job I then make side shot radiations to cadastral marks first and if also doing topo survey, then locate that info before closing to see if instrument creep to a set out and record of BS or FS having visually viewed on screen that the delta x,y, z discrepancies are with in accepted limits to ensure intermediate shots on same orientation and that no instrument knock or bad reading to BS or FS . The process repeated for each set up, so that by time get to last point you will get a raw delta x,y, z on screen which is misclosure of raw data. You will immediately know in field if traverse is acceptable while on job ! To close off the angles on last point I call the first instrument station the same number and add a suffix C for close, so that I have that generated point as my software only permits unique point number.
With open traverse you need to know end coordinates before start. Be they from earlier field or precomputed from original data.
Hopefully a tip or two for those venturing into TS electronic surveying.
RADU
I remember when the first manual data collector was used by anyone I knew. A crew chief bought one himself because the owner was el cheapo.
It was also noticed that his abilities as an instrument man to close a traverse became greatly improved overnight. He never turned in anything outside the boss's tolerance curve again.
Fortunately enough, he never learned to alter raw data.....
He and a few other characters I have worked with have proven many tall tales to be true horror stories.
What kind of data collector are you using? I've been using TDS since 1992, and checking traverse closures in the field is simple and has been the norm since day 1.
You can have your chainman "rock" you to sleep. You know get a rock and...
PR It was written for sake of safety blanket field bookers.
RADU
For a closed traverse, you can just use the N and 180 thing like we did for years before data collectors.
Who do you think you're schooling here? If you needed to be told this, then you don't need to have an office where you can read about it on the internet.
PR It was written for sake of safety blanket field bookers.
Wow! I should have held my reply until I read the entire thread. Just because we use field books, now we have safety blankets. Well, then I guess I'm in good company since Kent, Matthew and several others still use them regularly.
Maybe you should have asked if we still keep notes in the same manner as before data collectors.
FWIW, we've been using data collectors on nearly every job since 1992. I know what my closure on a traverse is before the gun is boxed up.
You're just like a peacock strutting your feathers, and not knowing, just like the peacock, no one gives a damn.
MR MORGAN U seem to have a huge B in your Bonnet...
This board caters for all . If the caps does not fit then simply move on .
Many who log on are students of surveying . The post was written because many still write everything manually in the FB.
BTW No peacocks were hurt during the typing of this post.
RADU
Richard abbot
Nope. You're simply acting like normal where you give your resume and why your right and if you don't agree with you, well your wrong. Your an arrogant SOB and it gets old. So does your typing style. You would have thought when you went to college you would have learned to communicate better than you do here. You gripe about being professional but type in a 15 year olds text lingo.
You're probably a decent surveyor, but your problem is you've started believing your own press and your head is now too big.
You're a peacock, or banny rooster. Take it however you want.
Lol! It is simple....I agree!
Tie back in...inverse between number uno and the new number..check bearing-distance for closure error.
Optional Coordinates?
Does Leica DC software still allow uncoordinated stations? I remember demoing their stuff in the late '80s or early '90s and finding it strange that you had to tell the DC to generate coordinates for a station. We were using TDS back then, and if a point didn't have coordinates it couldn't exist. As others have noted, requiring coordinates for all points makes checking in a snap -- no need to futz around creating dummy coordinates to see if you've got a problem.
The one thing about the Leica software that initially appealed to me was the ability to have alphanumeric station names. At first, when moving from a field book to a DC, I chafed at having to use only point numbers, no point names. But I quickly got over it, and don't miss alpha names a bit. I still use them occasionally for CORS stations in Star*Net, but that's about it.
