Please select a RINEX observation file to calculate a PPP solution. The RINEX versions 2, 3, and 4 are supported. However, RINEX version 2 files containing more GNSS than GPS and Glonass might fail. RINEX version 3+ is recommended for multi-GNSS observations.
Analyze: By pushing this button, raPPPid will analyze the RINEX file currently loaded into the GUI and its raw measurements. Please also check the output of the command window providing helpful information about the RINEX file. Note that this might take some time and depends somehow on the actual settings of the GUI (e.g., processed GNSS and signals (ranking!)). All plots are created using only the data and raw measurements directly from the RINEX File.
real-time (experimental): Enable this checkbox to perform real-time processing (experimental) in conjunction with a running version of the BKG Ntrip Client (BNC). Make sure that you have selected a RINEX observation file, a RINEX navigation file, and a correction stream file currently streamed and written by BNC. Furthermore, define a start-time and end-time in GPS time, usually corresponding to the time stamps in the RINEX file. Make sure that the defined start-time is slightly in the future (e.g., 30 seconds). After hitting the RUN button, raPPPid will wait for the first data epoch in the defined timespan and perform real-time processing until the defined end-time.
The approximate position is automatically read from the header of the RINEX file. These approximate coordinates are used to initialize the position in the first epoch of the processing. You can manually enter values if the RINEX header does not provide an approximate position. If no approximate values for the coordinates are available, enter [0 0 0]. raPPPid will calculate a simple code-only solution during the first epoch to initialize the coordinates in the filter.
GPS, GLONASS, GALILEO, BEIDOU: With the checkboxes, you can in/exclude the related observations from processing.
Frequency checkboxes: The drop-down-menus allow selecting the processed frequencies of each GNSS
Ranking: If multiple observation types exist on a processed frequency, the observation ranking decides which observation type is processed. Therefore, the characters of the RINEX version 3+ specifications are used. Observation types on the left have a higher order and are preferred to observation types on the right. For example: GPS L1 is processed, and C1C and C1W were observed. The ranking defines which code observation raPPPid will process. Of course, the corresponding phase observation is taken - if missing, another phase observation is used. In such a case, the ranking is used again.
Jump to Table of Content