Static Point Processing in Emlid Studio

This video walks through an example of static processing in Emlid Studio to improve the absolute accuracy of your field base station coordinates.

💡 Workflow Recommendations: For the highest precision, we always recommend checking the processing options in this order of priority:

• First choice: Utilize the PPP (Precise Point Positioning) service provided directly through your native NTRIP network.
• Second choice: Submit data logs through the OPUS Beta tool utility or standard NGS OPUS static processing pipelines.

If those preferred options fail to resolve a clean solution due to coordinate constraints, running an independent local baseline correction inside Emlid Studio provides an excellent backup path to improve a static point solution.

Overcoming Data Noise and Cycle Slips

When launching Emlid Studio, select the Static processing engine template. In some field instances, opening your base station's raw observation dataset displays significant tracking noise and structural cycle slips across the signal bars, which is typically why a submission to automated engines like OPUS will reject or return an abort error code.

To establish our own local differential correction baseline, import both the satellite observation asset (.25O file) and navigation telemetry data (.25P file). From there, we simply need a clean reference log from a nearby known base station layout.

Linking Nearby CORS Networks

For this walkthrough scenario, we utilize a stationary CORS hardware receiver station in the South Carolina Real-Time Network (SCRTN) situated only a few miles from our site. By logging into the regional network portal, you can download the matching time-stamped RINEX observation files corresponding precisely to the duration your field base was operating.

Before computing the fix, look at the internal application processing settings window. Here, you can adjust the timeframe parameters in case you need to cleanly truncate noisy structural window segments from the first few or last minutes of the field observation log. The interface also lets you choose between exporting the entirety of raw epoch paths or outputting the optimal statistical position filtered via Extended Kalman Filter (EKF) parameters.

Once parameters are locked, click the main Process command button. Emlid Studio uses the rigid reference values from the SCRTN network terminal to resolve a high-precision absolute position coordinate. Comparing this resolved coordinate back to the preliminary averaged single point tracked on-site reveals a major baseline transformation correction of approximately 5.5 feet.