I was hoping to find a method for adjusting the threshold distance between the current rover position and a stakeout point to allow recording the rover position.
My plan had been to enter crude global coordinates into my stakeout plan based off of open resources and not survey grade coordinates. I would then visit the site, perform the stakeout, and come up with my own precise coordinates (using an RS2+ base and RS3 receiver). Currently, the 2.5 cm requirement is preventing me from entering the coordinate as a staked-out point (it never turns green). My workaround is to back out of the stakeout workflow and enter the point by hand, which works, but is inconvenient.
I understand that this may be an uncommon use of the stakeout function. But I’m also hopeful that maybe I’m just overlooking something in the documentation.
You’re saying that you can’t record the point unless it is green? I haven’t experienced this yet, but don’t know that I have run into that scenario. If I am staking out my control it is tight and if I am setting a stake I am setting it within tolerance, but I can understand why it might be beneficial to stake something with lesser accuracy.
If I can record a point in stakeout mode prior to it turning green, then I am missing something!
Yes, I am using this to develop lists of control points and validation points for aerial survey. So, I might go into the stakeout with only a rough estimate of some of the features, e.g., corner of parking lot, that I then want to go and precisely survey with the rover.
@michaelL The goal is to establish GCPs and checkpoints. Of course, some will be determined in the field, especially if placing targets for GCPs, so this is really focused on locating other photo-identifiable features in the scene independent of the aerial collection itself.
Finally, went back out with ellipsoid height set to a reasonable value, and still am seeing this (no button to save the point). Note that while the screenshot does show that the IMU needs to be recalibrated, in my experience this made no difference. It was just quite difficult to get the screenshot at just the right time!
My rough coordinate was specified with an ellipsoid height of 0 m, hence the elevation delta of over 200 m. Perhaps this has to be closer before it can be saved? I’ll try manually adjusting the expected elevation to see if it makes a difference.
@adnaanparker1 Well, that’s embarrassing! I had read the documentation as the Survey Plan was required to run the stakeout report, but I had been under the impression that I could still save the points without it. I just saw the note that mentions points cannot be saved without a plan and saw that I also would have had issues due to the projection being in global coordinates, not local.
Could be that I got confused here, where “Point collection and stakeout” is listed in the Free column and “Stakeout reports” is in the Survey column. I wonder if it changed at some point along the way. Regardless, doesn’t change the answer. Thanks @michaelL and @adnaanparker1 for the pointers.
So essentially you are just using stakeout to get you close to a predetermined GCP/CHX location. Just hop out of stakeout mode and collect the point regularly. Stakeout mode is meant for high-accuracy staking of points and then providing a daily report of what the crews actually set. I do like the idea of being able to adjust the tolerance but there does need to be a tolerance. If their design is to make sure the stakeout is accurate to within industry standards I would say that the crews should be trusted to set stakes properly and the report can QC their work if needed.
I see that the question has already been cleared up. Thanks to everyone! Yes, you can collect and stake out points. But to save that staked-out point, you’ll need the Survey plan.
