It would eliminate a very easy source of error if we could record the base coordinate after a single observation averaging, including receiver height adjustments, i.e. ground coordinates.
I have on a few occasions used the coordinate provided by the points’ base station coordinates to come back the next day to manually set the base coordinate, only to find I’m off in vertical by the pole length + adapter + receiver height. Obviously the base coordinate that is getting recorded is the receiver phase center, but it’s actually rare we ever use the receiver coordinates for anything. It’s much more useful to know the coordinate of the control point, and that’s what the base settings expects as well.
Please improve the workflow whereby we can set up over a point previously occupied by the base with any or all of the following, in order of most helpful:
Most preferred: Record the single averaging ground coordinate as a point in the project once the observation is complete.
Ensure the manual base input can directly receive this point as input without having to manually adjust for receiver height.
Indicate somehow in the point list that the base coordinate is at the receiver height and not ground.
Add ground coordinate for the base point to the point list.
Thank you for sharing your detailed explanation of the improvements you’d like to see in Emlid Flow. We currently don’t have this feature available, but I will definitely pass your request along to our development team for consideration in future updates.
Open or create a project. Select the Measure option and specify your rod height and preference for recording. In the case of your example, select the amount of time and Average Single. Name the point something like “Base”.
The next time you come to the site, set your receiver up on the point and in Base Settings select Manual, Configure, Select from Project. Select “Base”, or whatever you named it before. It will auto populate the base coordinate fields.
I’m like @dpitman … it’s fairly easy to record to your base as a “conventional” point. It’s just like having a recorded “here” position (Trimble, Javad and others) at the base.
I think you’ll like using Dave’s suggestions, I do !
But when using a BASE and a ROVER set up, when the base is set up over a arbitrary point and AVERAGE SINGLE, how would you be able to record that point for manual use later if the ROVER is used to record survey projects?
Are you switching between BASE and ROVER to create a project and record point using the BASE or something? Then bouncing back to the ROVER?
I haven’t tried your method yet, I just note manually, but will have to try it.
If you show up on a site and set up your base on an arbitrary point, you can simply collect a point just the same as when you are collecting a point with your rover. A point is a point, no difference. The difference is how you collect it. By default, the base point is collected automatically using whatever parameters you have set for rod, time, single, fix, etc., without associating it to a project.
But, you can also just open a project and collect the point from within the project. By collecting the point in the project, you get the same base coordinate as the first (default) method, but it is recorded in the project and is easily recalled later at any time, including immediately, and input into the base settings.
Do you mean after the BASE determines its average SINGLE LLH location upon 1st set up. Just cut/paste the LLH information as a NEW POINT (i.e. called BASE) into the survey project to refer to later as a MANUAL base set up?
Ok, i see. I’m just used to immediately setting BASE over arbitrary point that will be AVERAGE SINGLE, then note the base LLH and antenna height on paper or phone the hard way, then connect the ROVER and go from there.
Your method just uses the ROVER 1st to collect that INTENDED point (AVERAGE SINGLE), then set BASE over it and select that point from project or enter data manually then go from there.
My order of operation was different and not optimal.
If not already, Emlid should consider adding your method as a TIP in their DOCS.
The way you are doing it was the only way a couple of years ago. A few of us worked with the team here to add a way to not have to do any manual coordinate copy paste nonsense. They came up with the mechanism to use a project coordinate to populate the base settings.
I think you are somehow getting mentally stuck in “base” “rover” roles.
Whether you use corrections or not, it is the same workflow.
If NTRIP is not available, I also just specify “Average Single” when I collect the point. No difference.
The receiver is doing the exact same thing in my case as it is in your case. The only difference, is that it is recording it within a project in my case. And it is not in your case. Otherwise, exactly the same under the hood.
I guess I don’t understand why you would call that “rover” use in my case and not in your case? But it doesn’t really matter.
I was able to record a Single averaged from the base before even turning the rover on.
Previously, the project settings needed to be unchecked for “Fix only” to do this, which I never did to prevent bad shots. Apparently now that setting is in the point settings, which I never noticed until this thread, so thank you Dave. It worked great. It would be nice if the base settings feature was better streamlined, but this method works great.
