In this post, we’ll explain how to collect points in RTK with relative accuracy and correct them with a new base position afterward.
When you may need that? Remember we discussed how you can obtain precise coordinates in a remote area with no cellular network available? We told about PPP technique there, which can be used to find a known point for your base to collect points with absolute accuracy. Also, for this purpose, you can use AUSPOS or OPUS services.
But this workflow may take time: you need to go to a site, record raw data logs, process them to get base position, and then return to collect points in RTK with absolute accuracy. Sometimes, you don’t have enough time or just can’t attend a survey site twice.
Here is an alternative workflow:
In the field
- Average the base position in SINGLE.
- Write down the averaged coordinates.
- Go to the Logging tab and choose one of the presets we have in ReachView 3. They were made to match the requirements of different PPP, AUSPOS, or OPUS services.
- Start raw data log recording on the base.
- Collect points with the rover in RTK.
In the office
After the survey, download the raw data log from the base and submit it to the chosen PPP service, AUSPOS, or OPUS.
To calculate the shift between the new position and the base coordinates averaged in the field, subtract one coordinates from another. For example, in Excel.
But there is a pitfall: they should be in the same coordinate system. I’d suggest converting both of them to the coordinate system of your ReachView 3 project. Base coordinates averaged in SINGLE are always in WGS84.
Once you’ve calculated the difference, add it to the coordinates of the collected points. It can also be done in Excel, for instance.
The similar workflow can be used if you got a new base position by processing its logs with logs from NTRIP service. If this case requires clarification, don’t hesitate to ask!