Bearing rotation stake out error

Sounds like a similar situation I'm fixing.

I picked an arbitrary 270?ø back sight, and I accidentally clamped my ground to my grid, and whammo. I'm undoing what I did one day at a time.?ÿ Start the search for if your ground was rotated prior to the import.

?ÿ

Good luck.

?ÿ

?ÿ

Thanks for the reply Jitter,

Tell me more about "clamping my ground to my grid" maybe that's what I did, and specifically how do I unclamp it on the Trimble?

?ÿ

Thanks,

Rick

https://surveyorconnect.com/community/construction-mining/building-layout-issues/

?ÿ

This is a discussion about the same thing,

I'm not well versed enough to explain the switch, but I screwed up my own project by doing the exact opposite of what you're doing, and trying undo currently.

A workaround thought. ?ÿCopy your raw gps located points say they are numbered 1-100. ?ÿRename the new points 101-200. Leave the pure raw located gps points unadulterated in the exact same place they were located. ?ÿThen move 101-200 down to N5000 E5000 then rotate away. ?ÿOr copy the job and rename the new job and then rotate that oneƒ???

In Trimble NEVER translate your survey, always translate your Calculated points. Translating your survey creates no end of problems.

If this is GPS, then as Dave said, you shouldn't be rotating your field shots, since they're already on SPC.?ÿ Take your control/input plan and points and rotate them onto your field points

This thread scares me.

@mightymoe?ÿ

Be very scared.

?ÿ

I'm readjusting to life not in the LDP utopia I was living in, so it's my fault for not paying attention.

Luckily it's a relatively small project and in house with my engineering team so I'll just get some pretty healthy ribbing for not know my @$$ from a hole in the ground, and will be better for it when I'm troubleshooting some other newbie who makes the same mistake in the future

?ÿ

I have been field calculating for 25 years. In this case, all I am doing is setting a basis of bearings in order to find and or set points. Yes this is GPS, but all of this was working normally until fairly recently. I shoot up my points.. set my basis.. calculate a theoretical point, try to stake it and it is off. I rotate back.. and all is good.

And again, this was all working fine 2 weeks ago. ???

???

@rick13 I'm with everyone else. Never rotate field data, don't adjust field data. Make the plat or whatever information you have match what you have found in the field. You can accomplish the same objectives and you do not risk corrupting your field data.

Posted by: @brad-ott

A workaround thought. ?ÿCopy your raw gps located points say they are numbered 1-100. ?ÿRename the new points 101-200. Leave the pure raw located gps points unadulterated in the exact same place they were located. ?ÿThen move 101-200 down to N5000 E5000 then rotate away. ?ÿOr copy the job and rename the new job and then rotate that oneƒ???

When rotating onto control, I always had my initial observations in one file, copied the coordinates into a new job(file) and worked on them.

@lurker?ÿ

I'm doing that, essentially I created a new assumed coordinate system, and have to run with it for the now.

I'm hoping this doesn't work into a black check mark to be a reason to fire me someday.... painful but true, I screwed this one up by not reading the words on the screen.....ouch.

@lurker?ÿ

Ok then, how do I do that in the field? "Make the plat match the field"?

?ÿ

Sounds like everything rotated if your still off the intended rotation #.?ÿ

I'm with Lurker, never rotate your field data, ever.?ÿ In fact we don't rotate anything in the field, too many possibilities for errors.?ÿ All our data is uploaded to the office, if adjustments are necessary, prior to continuing.?ÿ Obviously that doesn't work for everyone as you have a tried and true process...until something goes haywire with know simple solution.