For the complete documentation index, see llms.txt. This page is also available as Markdown.

PPP (Precise Point Positioning)

Precise Point Positioning in Rinexlab: static and kinematic PPP from a single receiver, precise product options, convergence, expected accuracy, cost and result files.

PPP computes the position of a single receiver from precise satellite orbits and clocks. No base station is involved, so PPP works anywhere in the world.

Typical performance

Horizontal

Centimetre-level

Vertical

2 to 3 cm

Solution

Float

Modes

Static and kinematic

These figures apply to good static data of two hours or more. Shorter sessions reduce precision, especially in height. Rinexlab PPP returns a float solution: this is expected for the method.

How Rinexlab computes PPP

  • One PPP run per pair of orbit and clock products from the same analysis centre, then a robust mean of the runs after outlier filtering. Using several independent centres guards against a single faulty product.

  • Modelling of satellite and receiver clocks, tropospheric delay, antenna phase centre variations, Earth tides and relativistic effects.

  • Static jobs are computed on 5 s data: over sessions of hours, closer epochs do not improve a static solution.

  • If the receiver antenna is missing from the RINEX header or has no published calibration (some UAV files leave it blank), the job runs without receiver antenna corrections instead of failing, and the result says so.

Static PPP

Use static PPP for the precise position of a point occupied by one receiver for the whole session.

Static PPP (video, about 80 s)
  1. Open your file and click Process with PPP.

  2. Mode: keep Static.

  3. Precise products: keep Best available (see below).

  4. Data to process: process the whole file, or narrow the window in 15-minute steps. Two hours or more give the best static result. Under one hour, expect several centimetres.

  5. Output datum: positions are computed in ITRF2020 at the observation epoch. Pick a regional datum to get them there as well.

  6. Check the cost, then click Start processing.

The job runs in the background: you can leave the page, and an email tells you when it is done. The result shows on the file page: the position, its standard deviations north, east and up, the number of solutions kept after outlier filtering, and the frame. You can also use the result as the reference coordinates of the file when it serves as a base.

Kinematic PPP

Use kinematic PPP for a receiver that moves: a vehicle, a drone, a pole walked along a line. You get a position for every epoch instead of a single point.

Kinematic PPP (video, about 75 s)
  1. Open the file menu and choose Process with PPP, then set the Mode to Kinematic.

  2. Keep the precise products on Best available.

  3. Keep the convergence time. The first 20 to 30 minutes of a PPP solution converge. Keep the start of the file in the window, or accept a less precise beginning. If possible, keep the receiver static for the first 20 to 30 minutes of the recording.

  4. Choose a regional datum if you need the trajectory there as well as in ITRF2020.

  5. Check the cost and start the processing.

The file page shows the mean of the epochs with its standard deviations and the number of epochs computed. Download the trajectory as CSV files, in ITRF2020 and in the datum you chose. When the job used two product pairs or more, a combined trajectory (positions_combined_...csv) averages the pairs at every epoch, with the spread between them. It is shown first.

Precise products

Option
What it uses
Credits

Best available

Final products when enough analysis centres have published them, rapid ones otherwise

x1

Final only

Final products

x1

Rapid only

Rapid products

x1

All available

Every final and rapid product pair, averaged

x1.5

Rapid products appear about 17 hours after the observation day, final products after 12 to 18 days. Best available is the right default. If you processed early with rapid products, you can process again with final products later: that is a new job.

Cost

One credit per hour of processed data, rounded up to the quarter hour, minimum 1 credit per job.

  • Static: x1 whatever the recording interval, since static jobs are computed on 5 s data. A 1 Hz file costs the same as a 5 s file.

  • Kinematic: every epoch is a result, so high-rate data carry a multiplier: x2 at 0.5 s and 0.2 s, x3 at 0.1 s.

  • All available products: x1.5.

Examples: static, 3 h, Best available: 3 credits. Static, 8 h, All available: 12 credits. Kinematic, 1 h at 1 s: 1 credit. Kinematic, 8 h at 0.2 s: 16 credits.

The cost shows before you start. A job that fails or is rejected is refunded automatically.

When to choose something else

For better height on a short session, or where 2 to 3 cm vertical is not enough, a differential job against a nearby base, your own or a virtual one, usually does better.

Last updated: 28 October 2026

Was this helpful?