PPP with gpsrinex
In my previous blog PPP Precise Point Positioning 3 years ago I used the method “averaging” to get a precise position.
This time I used this Canadian service for post-processing the data.
So I prepared my GNSS receiver ZEF-F9P for this job. This is well documented in the man page for “gpsrinex”.
So I run over several days commands like this:
gpsrinex -i 30 -n 1440 -f gpsrinex2025322205923.obs
This would collect the information for a period of 12 hours.
2025322205923 means: year 2025 day number 322 of this year at 20:59:23 h
If this job is finished it’s theoretical possible to upload this file immediately to the Canadian service. But then you get a result as product type “ultra fast”. If you wait a day or so it’s “fast” and if you wait more than a week you get the “final” version. Because it takes some time for them to get all the correction data to make a qualitativ high post processing with my collected data.
If one submits this file one will get the result per e-mail. This e-mail may take several hours but it could also be available after several minutes. It depends on how much requests are in the queue.
As processing mode I selected “Static” and “ITRF”
This is the final result
| date | latitude | longitude |
|---|---|---|
| gpsrinex2023117170821 | 48.14929225833 | 16.28384379721 |
| gpsrinex2025322205923 | 48.14929171666 | 16.28384437221 |
| gpsrinex2025323171908 | 48.14928167499 | 16.28384415555 |
| gpsrinex2025323203540 | 48.14929222499 | 16.28384461388 |
| gpsrinex2025324091707 | 48.14929101388 | 16.28384304444 |
| gpsrinex2025327220019 | 48.14929243888 | 16.28384382777 |
| gpsrinex2025330191355 | 48.14929198610 | 16.28384486110 |
| average | 48.149291939807 | 16.283844086102 |
If I compare this result with the result of “averaging” then there is a gap of about 47 cm.
This is the result as graph without the outlier in line 3 at 2025323171908
