Basically, we had decided to stop using them, they would stick in place like a calculated point when the base was moved from it's auto position to it's OPUS or CORS adjusted position. Measured points shifted but stake out points would be held in place and the vector would be changed, not cool 🙁
Yesterday the PC did a job and he likes using them so he sat down, took some time, and in TBC figured out how to make them work, so now we can make them move to where they should be............. with a little persuasion.......
Don't know why they get fixed, its never made any sense to me.
Don't know why they fix them either but it's only a few mouse clicks to change them to survey points.
Lee D, post: 401738, member: 7971 wrote: Don't know why they fix them either but it's only a few mouse clicks to change them to survey points.
Once you figure out which clicks to click, I may be doing it differently, I end up with two points, one with a -1 after the original name and still in the first located position.
Why that is done puzzles me, but they sure seem to want to keep that location........
I'm in the habit of converting as-staked points to survey points and then deleting the as-staked points. They almost always come in with error flags, especially when we're staking to a line, and as you said they don't update.
It's one of those strange things found in a computer program, why the programmer thought that those points have such significance that they can't change and that the vector needs to change is a head scratcher. I suppose someone, somewhere complained about something and a programmer at Trimble made it happen, clearly he/she isn't a surveyor.
Reminds me of early TGO. Change a rod height and the zenith changes...
Lee D, post: 401768, member: 7971 wrote: I'm in the habit of converting as-staked points to survey points and then deleting the as-staked points. They almost always come in with error flags, especially when we're staking to a line, and as you said they don't update.
The stake to line thing generated a sea of red in my project. I just want the topo shot of the lath I set so for some reason I selected them all and right clicked to see what would pop up, it said Convert As-Staked Points so I did and they changed to topo shots then I delete all the as-staked coordinates.
Part of the problem is I start a sf=1 with assumed coordinates job in the field then start traversing. Then I transform my calculated coordinates to the Survey when I have enough known monuments observed (don't, whatever you do, don't move your Survey which deletes all your observations up until that point which I find really weird). Later when the whole thing is brought into TBC and adjusted with GNSS observations it thinks the as staked points compared to calculated coordinates are way off. I don't need those anyway. So kill the as staked coordinates and the calculated coordinates and kill the sea of red flags.