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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8.4 Resolution Strategies<br />

(1) For very short baselines (up to several kilometers) the ambiguities may be resolved<br />

independently on L1 and L2 using the SIGMA algorithm (it is possible to do that in<br />

one program run, if both carriers are processed). This case is similar to processing<br />

single frequency data.<br />

(2) For longer baselines (up to approximately 2000 km) it is possible to process both<br />

carriers together and to try to resolve both (L1 and L2) ambiguities in the same<br />

run. The recommended strategies are QIF for long sessions and baselines of almost<br />

arbitrary length and SEARCH for short sessions and short baselines.<br />

(3) Using the so-called wide-laning technique case each baseline is processed twice. First<br />

the L5 or Melbourne-Wübbena linear combination is processed, the wide-lane (L5)<br />

ambiguities are resolved and stored in the observation header file. In the subsequent<br />

run the L3 linear combination is processed, the wide-lane ambiguities are introduced<br />

as known, and the narrow-lane (L1) ambiguities are resolved.<br />

It was stated above that in the first step of the third strategy (wide-laning technique)<br />

either the L5 or the Melbourne-Wübbena linear combination is processed. Using L5 (phase<br />

observations only) gets satisfactory results up to baseline lengths of about 100 km (or longer<br />

if a good a priori ionosphere model is used). In this case the processing steps are:<br />

• Ambiguity-free L3 solution saving the coordinate results to get good a priori coordinates<br />

for the next step.<br />

• Wide-lane (L5) ambiguity resolution fixing all coordinates on the values obtained in<br />

the previous step.<br />

• L3 solution introducing the resolved L5 ambiguities and solving for the narrow-lane<br />

ambiguities. In this third step the estimation of station-specific troposphere parameters<br />

is highly recommended (see Chapter 11 because the geometrical term ρ (including<br />

the tropospheric refraction) has to be accurately known – considering the small wavelength.<br />

Note that the estimation of troposphere parameters is always recommended<br />

for long baselines when doing narrow-lane ambiguity resolution or when using the QIF<br />

strategy.<br />

The approach given above (using phase observations only) does not seem to have advantages<br />

over the QIF strategy.<br />

Resolving wide-lane ambiguities using the Melbourne-Wübbena linear combination is very<br />

reliable and almost baseline-length independent. However, the quality of the code measurement<br />

is crucial. The use of smoothed code generated by the program RNXSMT may<br />

help.<br />

The recommended strategies are summarized in Table 8.1.<br />

The ambiguity resolution for GLONASS is only possible with the SIGMA strategy in a<br />

phase–only mode because inter-frequency code biases (caused by the FDMA technology of<br />

GLONASS, see, e.g., [Dach et al., 2006a]) are not handled in the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong>. The<br />

so-called single difference bias term for GLONASS was derived in Section 2.3.7. It is usually<br />

quite small and not explicitly handled in the software. For that reason we recommend to<br />

use the ambiguity resolution for GLONASS for test purposes, only. However, in the case of<br />

a combined <strong>GPS</strong>/GLONASS analysis you have to make sure that no ambiguities between<br />

the different <strong>GNSS</strong> are resolved.<br />

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

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

Saved successfully!

Ooh no, something went wrong!