Post Processing Survey Points in Emlid Studio (Stop and Go with Emlid Flow PPK)

This guide will walk through the process of collecting topo points in Emlid Flow and post-processing them in Emlid Studio to dramatically correct their absolute spatial accuracy using a Stop & Go PPK routine.

Field Execution & Baseline Conditions

Before launching your site survey, confirm that raw data logging is actively running on both your base station and rover receivers. As a best practice, it is highly recommended to configure your devices to auto-backup source data directly into standard RINEX formats.

In this specific workflow example, we begin by referencing an average single positioning solution on our base receiver, knowing we will step its accuracy up later using a calculated OPUS coordinate correction. To demonstrate the robust capacity of post-processing, we purposefully collect half of our asset points with a solid base-corrected RTK fix, while capturing the remaining half using an uncorrected single solution. Every collected node in this dataset represents the exact northeast physical corner of regional catch basins.

Data Export & Flow 360 Visuals

Logging into the cloud-based Flow 360 portal reveals our preliminary raw collection map. Overlaying a high-resolution drone orthomosaic background layer instantly confirms our baseline error: the raw recorded points visibly do not align with the true catch basin corners on the ground canvas. To initiate corrections, we export our raw collected data table as a standard CSV format and pull down the concurrent tracking logs from our base and rover units recorded during that exact timeframe.

Resolving the Trajectory in Emlid Studio

With our fieldwork assets collected, open Emlid Studio and select the Stop & Go with Emlid Flow processing configuration. From here, follow these steps to resolve your point data:

• Drag and drop the native RINEX observation logs from your base and rover modules directly into the input parameters box (or import the raw system .ubx backup logs).
• Modify the base coordinate fields, overriding the preliminary values stored inside the raw RINEX file header with your precise, corrected values obtained from your processed OPUS solution sheet.
• Fine-tune the mathematical parameters inside the advanced processing settings window to optimize your forward/reverse baseline trajectory passes.

Click the main Process command button. The computation engine should return a high percentage of resolved "Fix" solutions across the rover's trajectory path.

Applying Corrections to the Point Table

The final step is loading our exported project CSV point table into the resolved trajectory matrix. Filter through the computed metrics, select the highly acceptable resolved solutions, and overwrite the uncorrected coordinate paths.

Re-importing the final corrected CSV file back onto our map verification canvas proves the immense value of this workflow. As anticipated, the initial RTK points scale smoothly through a uniform baseline shift into place. More importantly, the points collected as loose, floating single solutions are transformed—now resting precisely on the physical northeast corners of the targeted catch basin structures.