08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PID 221 SMTBV3: Set the “Sampling interval” to 30 seconds.<br />

PID 302 PPPEDT P: Set the “Sampling interval” to 30 seconds.<br />

20.5 Processing own Data With Example BPEs<br />

If you plan to analyze data with a higher sampling than 30 seconds you need satellite<br />

clock information with a corresponding high sampling. These satellite clocks must be fully<br />

consistent with the satellite orbits and Earth orientation parameters.<br />

The <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> reads satellite clock files with a tolerance of 30 seconds. Thus if<br />

1 Hz data should be analyzed one and the same satellite clocks value is used for 30 epochs<br />

leading to an increased noise in the residuals and results (the thresholds for the last data<br />

screening iteration in script PID 302 PPPEDT P possibly have to be increased slightly). The<br />

reduced accuracy may be acceptable if PPP is only used to generate good a priori positions<br />

for subsequent processing steps.<br />

20.5.5.2 Double-Difference Solution (RNX2SNX.PCF)<br />

As prerequisite we assume that we have station positions flagged with K for all epochs in<br />

the kinematic coordinate file (e.g., from a previous PPP solution). Follow the listed steps<br />

to perform a double-difference solution including kinematic stations:<br />

PID 222 CODSPP P:<br />

• Introduce a priori kinematic coordinates (e.g., from PPP)<br />

• Disable the coordinate estimation by setting “Estimate coordinates” in panel “COD-<br />

SPP 2: Input Options” to NONE<br />

PID 301 SNGDIF: Parameters for kinematic coordinates are estimated from a quite low<br />

number of observations. It makes sense to ensure that as few observations of the<br />

kinematic station as possible are lost during baseline creation.<br />

If you have, e.g., only one kinematic station in your network you can achieve this by<br />

choosing the “Processing strategy” STAR with the kinematic station as “Reference station<br />

for STAR strategy”.<br />

PID 312 MAUPRP P:<br />

• Introduce the a priori kinematic coordinates file from PPP.<br />

• It is recommended to activate “Do not accept cycle slip corrections” in panel<br />

“MAUPRP 8: Cycle Slip Detection/Correction”. New phase ambiguities are set up<br />

instead.<br />

• Adapt the “Sigma of L1/L2 observations” to the accuracy of the kinematic coordinates<br />

from PPP.<br />

• Kinematic coordinate estimation in MAUPRP is not necessary if you have excellent<br />

kinematic coordinate results from PPP.<br />

You should activate the “Kinematic coordinate estimation” in panel “MAUPRP 6:<br />

Epoch-Difference Solution” if you have to increase the “Sigma of L1/L2 observations”<br />

too much (e.g., 0.005 m allows to pass slips of up to three cycles). In that case<br />

the “A priori coordinate/baseline vector sigmas” should be as strong as possible.<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 461

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!