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. Initial Phase Ambiguities and Ambiguity Resolution<br />

Table 8.1: The most important <strong>GPS</strong> ambiguity resolution strategies supported by the<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> .<br />

Case Baseline length Occupation “P”-code Ambiguity resolution (AR)<br />

time available? strategy<br />

1A short<br />

(< 20–40 km)<br />

> 1hr no SIGMA: L1&L2 or L1 or L2<br />

1B short (< 5–10 km) ca. 1–5 min no SEARCH : L1&L2, no TRP<br />

estimation<br />

alternatively<br />

SEARCH : L1, in<br />

reoccupation modea 2b c medium >2–4 hr no (0) Ambiguity float (network)<br />

(< 100-200 km)<br />

solution:<br />

NONE: L3, estimate/save<br />

CRD and TRP<br />

(1) Wide-lane ambiguity<br />

resolution:<br />

SIGMA: L5, introduce (fix)<br />

CRD, TRP, and ION;<br />

save wide-lane ambiguities<br />

(2) Narrow-lane ambiguity<br />

resolution:<br />

SIGMA: L3, introduce<br />

wide-lane ambiguities;<br />

estimate CRD and TRPd ;<br />

save narrow-lane ambiguities<br />

3A b e long (< 6000 km) >8–24 hr yes (1) Wide-lane ambiguity<br />

resolution:<br />

SIGMA: MELWUEBB f ,<br />

introduce P1–C1 DCBs g ;<br />

save wide-lane ambiguities<br />

(2) Narrow-lane ambiguity<br />

resolution:<br />

SIGMA: L3, introduce<br />

wide-lane ambiguities;<br />

estimate CRD and TRP d ;<br />

3B b c long<br />

(< 1000–2 000 km)<br />

save narrow-lane ambiguities<br />

>8–24 hr no QIF: L1&L2, estimate SIPs h ,<br />

CRD and TRP d ; introduce<br />

(or estimate) ION<br />

save L1/L2 ambiguities<br />

a Two (or more) baseline sessions (separated by more than 1 hr) must be processed together<br />

b<br />

Use of precise orbits required<br />

c<br />

Use of deterministic ionosphere (ION) models recommended<br />

d<br />

Introduction of TRP results coming from ambiguity-float network solution possible, if not recommended<br />

e<br />

No assumption concerning ionosphere necessary<br />

f<br />

Phase must be processed together with code tracking data<br />

g<br />

P1–C1 differential code bias (DCB) information required in case of a mixture of receiver tracking tech-<br />

nologies<br />

h (Epoch-specific) stochastic ionosphere parameters (SIPs) must be pre-eliminated every epoch<br />

Page 182 AIUB

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

Saved successfully!

Ooh no, something went wrong!