Wrong Station Setup .

I believe if you change the statuon or backsight coords all the obsevauons from the station change as well.?ÿ

It can certainly be done. You have collected raw data and that data can be recomputed. I use StarNet everyday to do such a thing.?ÿ With a laptop, I can do it onsite.?ÿ It could be done with a pencil, trig book, and slide rule. So, yeah. All that.?ÿ

I believe that you are actually asking is whether updating the station setup coordinates in the data collector will cause the raw data attached to that?ÿ station to be recomputed?ÿ to match.?ÿ I don't know the answer to that. But I'm interested to hear about the results when you try it.?ÿ ?ÿ

If you change it wrong in the filed it is almost impossible to go back. If you change it without first explaining it to your boss you could be committing fraud.

Wrong instrument setups can come in many forms, wrong IH or RH, easy to change. Wrong occupation and/or backsight number, harder to change. Better to copy your file and work in he copy for the rest of the day. Depending on your software, points can be translated and rotated in the filed, best done in the copy file. The toughest ones to change in the filed are when your control is in one file and your shots are in another file.

Better to do any changes in the office where you can think and plan it out before doing it. again you work in a copied file.

Paul in PA

I wont profess to be an expert as on this particular board, my 15 years experience is pretty small here. That being said, assuming you know precisely what went wrong, I can only think of a few occasions it cant be fixed in the office.

The fact that the question was raised makes me want to stress on the other advice you received, discuss the issue with the party responsible for your work. Fix or resurvey is their call.?ÿ

In the field? maybe, it depends on your software... high chance of loosing it all unless you make a backup of all your data and work on a Copy.

I agree with @norman-oklahoma

Star*Net is the tool.

loosen up the centering error setting to a reasonable (your best guess) and see how it closes.?ÿ
Open traverse? then what Accuracy do you need. Your Bad setup could not be more than a tenth I think

Let's hear how it comes out

Agree with making the fix in the office. ?ÿI recently had an I-man use completely wrong point numbers for Occupied Point and Backsight Point. He even ran a backsight check three times during a radial topo from that setup but never looked at the residuals to see he had a bad setup. Prior to that he was nearly flawless as an I-man. Completely through me for a loop when I looked at the data. Bottom line, I made a copy and fixed it all in the office without a return trip and without losing the original raw data file.?ÿ

Agree with making the fix in the office. ?ÿI recently had an I-man use completely wrong point numbers for Occupied Point and Backsight Point. He even ran a backsight check three times during a radial topo from that setup but never looked at the residuals to see he had a bad setup. Prior to that he was nearly flawless as an I-man. Completely through me for a loop when I looked at the data. Bottom line, I made a copy and fixed it all in the office without a return trip and without losing the original raw data file.?ÿ

I agree with the others here.?ÿ I can't think of a reason to do it in the field in the DC.?ÿ Maybe there's something I'm not thinking about, but I'd just make an obvious note in the fieldbook that a correction needs to be made, and continue with the traverse.

.... Prior to that he was nearly flawless as an I-man. ....

Probably you didn't mean it this way, but you make it sound like the man is now no good because of one mistake. That's a little severe.

It's an easy and not so uncommon thing to have happen. For?ÿ this reason I run?ÿ everything that comes back from the field through StarNet. I can run my finger down the raw data listing and get a good feel for how the day went. I can see that the control used is the latest. I can check the check shots for myself. If the data is good it takes 5 minutes. If not, whatever time I spend fixing it (if that's possible and it almost always is) is worth it.?ÿ

Quality Assurance is not so much about eliminating mistakes but rather it is about setting up processes to minimize them, knowing they are there, detecting them when they occur, and fixing them before they become a problem.?ÿ Quality Checking, BTW, is about monitoring your QA procedures - it's not bleeding on the final map with red pen.?ÿ

in my opinion this very circumstance is one of the most basic and clear cut reasons i decided long ago to always deal with raw data files instead of ascii coordinates.

also happens to be one of the simplest fixes in a raw file if, like you do, you know what the exact procedural error was.

guessing your raw file format would be .fbk, in which case you'd go into the raw file and change something that looks like this:

STN 1 5.35

BS 2 0.00000

PRISM 5.10

to this:

STN 2 5.35

BS 1 0.00000

PRISM 5.10

so long as the coordinates for your control points are good, it's that simple.

field data file management is something i am a bit... fastidious about.?ÿ so, for instance- i would take your "bad" file, download it and keep it as is.?ÿ (i save each day's work in a dated folder, and the raw file is dated for each day).?ÿ then i "save as" each day's file as the editable file with the tag "edited" on the end of the file name.?ÿ that is where fixes are made, the extra ephemera present in all raw files gets cleaned out, linework can be adjusted, yadda yadda.?ÿ that file is what goes into cad.?ÿ a good, orderly system like this can eliminate all kinds of confusion, lost data, paper waste.?ÿ?ÿ

i still remember the first time i was tasked with repairing a bad raw file, and thinking it looked like mandarin to me.?ÿ fifteen or so years later, and processing raw files has become so fundamental to my process i can't imagine even feeling like i have a good grip on a job without doing it.?ÿ even if it's a day's worth of rtk shots where a raw file is essentially just an inefficient ascii file, i still process the raw file every time.

Youƒ??re right Mark, I didnƒ??t mean it that way at all. What I meant was that this guy making a mistake is so rare that it was quite a surprise and the last thing I expected. Part of our field QA procedures requires shooting the backsight and noting the residules before taking the first shot, again every few minutes during a radial topo, and as the very last shot of the setup. Because those observations were in the raw file I was able to diagnose and fix the problem quickly. He just had a bad day in a very tough environment. Everyone has been there. I donƒ??t harbor any ill feelings toward him. Heƒ??s one of the best people that has ever worked for me. The example was given to show how even the best I-man can make a mistake and this particular fix can and should be fixed in the office.

?ÿ

Posted by: Jim Jacaruso, PLS

Youƒ??re right Mark, I didnƒ??t mean it that way at all. What I meant was that this guy making a mistake is so rare that it was quite a surprise and the last thing I expected. Part of our field QA procedures requires shooting the backsight and noting the residules before taking the first shot, again every few minutes during a radial topo, and as the very last shot of the setup. Because those observations were in the raw file I was able to diagnose and fix the problem quickly. He just had a bad day in a very tough environment. Everyone has been there. I donƒ??t harbor any ill feelings toward him. Heƒ??s one of the best people that has ever worked for me. The example was given to show how even the best I-man can make a mistake and this particular fix can and should be fixed in the office.

?ÿ

Understood. Things happen.?ÿ?ÿ

Thanks guys lovely reading your comets and advises really.

I did take another bs and fs and?ÿ?ÿthat is it. As far as I understood , they will be able to adjust everything in office.?ÿ

?ÿ