Base Rover Newbie
Norman OK's workflow is what I follow usually.
One suggestion - initially do some double checking as to how well the OPUS solution matches with the network solution to verify all your settings are matching up in the network/GNSS unit/collector chain. The first few jobs, I might go with getting the initial start point with the network unit - start base with this known point - collect data for OPUS - in office compare network and OPUS. Once comfortable that there are no significant differences, I would be more comfortable with holding the OPUS. It would suck if there was a difference and you ran out to a job for a "quick" pick-up and used the network for ease and it was just enough different to matter.
Base safety - contact neighbors to let them know you are doing a survey in their area and ask the one with the most open (sky view) and hidden (from shifty eyes) location if you can set up on their property. When in doubt of equipment safety, get an extra person to just babysit the gear.
One some the tunnel jobs I have ran, I would process and send for an OPUS solution to check my starting and ending control. I would think that that the project specifications would dictate whether this was needed. If I running base/rover for your everyday boundary survey then I don’t see the benefit in an OPUS position🤷🏻♂️. I am more concerned with the vectors in the raw file. If I am doing preconstruction design surveying or setting initial project control points then yeah I would run thru OPUS.
My Base/Rover technique varies depending on the scope, size and time frame of the project. If the job is short term and only requires one base I will use a method similar to Mark's. I set up the base at a random location that has good satellite views but bad road views. I'm not overly worried about radio suitability for the base since it has a built in UHF radio that I can transmit my repeater if needed. I also tend to use a cellular IP connection when possible. Fire up the base and broadcast based on an autonomous position while collecting raw data. Unlike Mark, I use the autonomous base value for the duration of the project. This limits a bit of possible confusion. When the project is complete I either post process the base data against adjacent CORS or send it off to OPUS. Then I translate the RTK derived coordinates to the final base value. In my case this is done in the manufacture's processing software.
If the project is long term or covers a larger area requiring several bases, I prefer to develop a static network before I begin RTK operations. It takes more time but I budget for that in my proposal.
I also tend to use a cellular IP connection when possible.
Interesting. Cellular connection between your local base and rover?
I like to examine and edit my data while my memories are still fresh. So I download and edit immediately after returning from the field. To prevent possible overwrites of my edits, I have a new data file for each day, rather than continuing with the previous day's file.
In spite of what I might have seemed to write in my first posting, I might go some days with the autonomous base position. But by the time I'm ready to go back to the site to set boundary monuments, for example, I'm going to be on a corrected basis. If I don't have that by then there is a danger of it never getting done. And I'm always thinking of jobs as the potential starting point for a future job in the neighborhood. I was assuming that the OPs typical job is boundary work, where he might spend a day collecting found monuments, spend some time in the office, then return to set missing monuments.
With a mind to reusing data in the future - If I establish points on the NAD83(2011) datum that I want to reuse 5 years from now when NAD2022 is de rigueur ...... If used an RTN to establish my coordinates then shifting them onto the new datum will be a translate-rotate-move operation. Probably OK, I guess, but a bit crude, IMO. If I use OPUS to position the base I case obtain a correct position for the base on any new datum by resending the data to OPUS, which I can enter into my StarNet project and have updated coordinates for everything in the new datum. So that influences my preference for using OPUS rather than an RTN solution.
Also an influence is the data sheet record OPUS produces, which I like to have over just a simple coordinate without metadata.