> For the complete documentation index, see [llms.txt](https://docs.premium-positioning.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premium-positioning.com/rinexlab/differential-processing.md).

# Differential processing (PPK)

Differential processing (PPK) in Rinexlab: process a rover against up to 10 bases of your own or a virtual base, in static or kinematic mode. Base selection, output frame, cost and result files.

Differential processing computes the position of your rover relative to one or more bases with known coordinates. Errors common to both receivers cancel out, which gives the best precision Rinexlab offers.

| Validation results |                                              |
| ------------------ | -------------------------------------------- |
| Horizontal         | Within 1 cm                                  |
| Height             | 1 to 2 cm                                    |
| Modes              | Static and kinematic, up to 10 bases in both |

These figures come from our validation campaign against reference stations of known coordinates. Height differences grow with the distance to the bases: keep baselines short where you can.

### What you need

* A **rover** file, imported into Rinexlab.
* One or more **bases** that overlap the rover window:
  * base files of your own, imported into Rinexlab, each with [reference coordinates](https://docs.premium-positioning.com/rinexlab/base-reference-coordinates.md), or
  * a **virtual RINEX at the rover position**, generated for the job (see [PPK with a virtual base](#ppk-with-a-virtual-base)).

A virtual base counts as one of the 10 bases.

### Static PPK

Use static mode when the rover stayed on one point for the whole session.

{% embed url="<https://www.youtube.com/watch?v=Nu-qFwYnIfU>" %}
Static PPK (video, about 80 s)
{% endembed %}

1. Open the rover file and click **Process differential**.
2. **Mode**: keep **Static**.
3. **Base stations**: pick your bases among your files that overlap the rover window. Each line shows the overlap, the distance and where its reference coordinates come from. A map shows the rover, the candidate bases and the baselines; a click on a base selects it.
4. **Data to process**: process the whole window, or narrow it in 15-minute steps.
5. **Output datum**: the result follows the frame of the base coordinates (see [Output frame](#output-frame)).
6. Check the cost, then click **Start processing**.

The result is the robust mean of the baselines after outlier filtering, with its standard deviations north, east and up, and the list of baselines used.

### Kinematic PPK

Use kinematic mode for a moving rover: a vehicle, a drone, a pole walked along a line.

{% embed url="<https://www.youtube.com/watch?v=DetjktdXU90>" %}
Kinematic PPK (video, about 70 s)
{% endembed %}

{% hint style="info" %}
The video shows a kinematic job with one base. Kinematic jobs now accept up to 10 bases, like static jobs.
{% endhint %}

1. Open the file menu and choose **Process differential**, then set the **Mode** to **Kinematic**.
2. Select the bases that overlap the rover.
3. Process the whole file, or narrow the window in 15-minute steps.
4. Choose the output datum and check the cost. In kinematic mode, high-rate data carry a multiplier.
5. Start the processing.

The result gives, for each baseline, a positions CSV with, per epoch, the solution type, the number of satellites, the PDOP and the formal standard deviations north, east and up. The file page shows their median. With two bases or more, a **combined trajectory** (`positions_combined_...csv`) averages the baselines at every epoch. The position file written by Wa2 for each baseline (`wa2pos_<n>.txt`) can be downloaded too.

### PPK with a virtual base

No base receiver on site? Rinexlab can generate a virtual RINEX at the rover position for the job, so the baseline is short wherever the rover is.

{% embed url="<https://www.youtube.com/watch?v=S2oR8EYjYZA>" %}
PPK with a virtual base (video, about 80 s)
{% endembed %}

1. Open your rover file and click **Process differential**.
2. Under **Base stations**, tick **Virtual RINEX at the rover position**.
3. Choose static or kinematic mode. You can combine the virtual base with bases of your own.
4. Check the cost: the virtual base is billed like a [virtual RINEX order](https://docs.premium-positioning.com/rinexlab/virtual-rinex.md#cost), on top of the processing. Both appear in the cost.
5. Start the processing. The virtual base is generated first, then the baseline is computed.

The virtual base needs:

* a known rover position,
* a window on a single UTC day,
* within the last 60 days,
* inside the [virtual RINEX coverage](https://docs.premium-positioning.com/rinexlab/virtual-rinex.md#check-coverage-first).

### Output frame

The result is expressed in the frame of the base coordinates. If you declared the datum of every base, you can also pick an output datum. Coordinates taken from an SPP or a PPP result are in ITRF2020.

If the result is not in the frame you expected, check the datum declared on each base: see [Base reference coordinates](https://docs.premium-positioning.com/rinexlab/base-reference-coordinates.md).

### Cost

The same rules as PPP, plus the bases:

* One credit per hour of processed rover data, rounded up to the quarter hour, minimum 1 credit per job.
* Static: x1 at any recording interval. Kinematic: x2 at 0.5 s and 0.2 s, x3 at 0.1 s.
* **+0.25 credit for each base beyond the first.**
* A virtual base is billed on top, like a virtual RINEX order on the same window.

Examples: static, 3 h, one base of your own: 3 credits. Static, 3 h, three bases: 3.5 credits. Static, 2 h, with a virtual base at 1 s: 2 + 2 = 4 credits.

Last updated: 28 October 2026
