The technique of PPP requires accurate satellite orbits and clocks. On the panel “Orbit/Clock,” you can select the (precise) source for these. There are two possibilities: You can either use precise products from the IGS or a specific AC. These precise products are available in different latencies (e.g., ultra-rapid, final). Furthermore, broadcast products can be used with correction streams (available in RT).
Please note that satellite products change their filename occasionally. Furthermore, some FTP servers are not completely stable and are not accessible sometimes. Therefore, the automatic download might fail. Please consider manually downloading the data from CDDIS and using the function CopyData2Folders() in such a case.
Select the Source (IGS or a specific AC) with the drop-down menu. Depending on this choice, different types are available (e.g., ultra-rapid, final). The selectable products correspond to the products the AC delivers for the IGS combination (most likely GPS+GLONASS). The MGEX product matches the multi-GNSS solution the AC calculates. The MGEX product might also be available at different latencies.
Use ORBEX: If available, you can decide to use the corresponding ORBEX file (satellite attitude). Without an ORBEX file, the IGS convention is used to model the satellites' orientation (described in the ANTEX file description).
You have to select the source of the navigation file. Select either a Multi-GNSS navigation file (*MN.rnx) for all GNSS or separate navigation files for GPS (*.*n), Glonass (*.*g), Galileo (*.*l), and BeiDou (*.*c). Multi-GNSS navigation files can be downloaded automatically or selected manually. Single-GNSS navigation files have to be selected manually.
Optionally, you can use a correction stream with the drop-down menu at the bottom. Some real-time correction streams are available as an archive and can be selected (e.g., CNES Archive and IGC01 Archive). You can manually choose a recorded real-time correction stream (e.g., with BNC Ntrip). Keep in mind that the files of recorded real-time correction streams are huge and the first read-in will take a considerable time (e.g., a few minutes). Currently, only recorded streams referring to the APC are supported.
Corrections age limit: Define how long orbit, clock, and bias corrections from the real-time corrections stream are valid (in seconds). If the last orbit message does not contain, for example, orbit corrections for a specific satellite, raPPPid will check older corrections. The satellite is excluded if the last set of (e.g., orbit) corrections is older than the defined value.
Jump to Table of Content