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.

13. Differential Code Biases<br />

Prominent examples for the second receiver class are: Rogue and old Trimble (4000) models.<br />

The latest generations of Leica, Novatel, Trimble receivers belong to the third class<br />

(providing C1 with a quality absolutely comparable to that of P1).<br />

Well-established <strong>GPS</strong>/GLONASS-combined receiver models, such as Ashtech Z18,<br />

Javad/Topcon, typically are P1/P2 receivers. However, we are already confronted with<br />

<strong>GNSS</strong> receiver models that must be attributed to two classes: the new Trimble NetR5<br />

behaves like a C1/P2 receiver for <strong>GPS</strong> and like a P1/P2 receiver for GLONASS.<br />

13.1.3 Differences of Code Biases<br />

Instrumental biases, BC1, BP1, BP2, are present with respect to C1, P1, P2. These biases<br />

are not accessible (in the absolute sense). It is common to consider the following differences<br />

of code biases:<br />

• BP1 − BP2 = BP1−P2,<br />

• BP1 − BC1 = BP1−C1.<br />

BP1−P2, BP1−C1 are called differential code biases (or simply DCBs). BP1−P2 is addressed<br />

in [<strong>GPS</strong>-ICD, 1993] as group delay, τGD (see also [Wilson et al., 1999]). The relation between<br />

τGD and BP1−P2 may be given as<br />

τGD = −1.55 · BP1−P2 + B0, (13.1)<br />

where B0 is an arbitrary offset (irrelevant to our applications).<br />

Figure 13.1 shows the order of magnitude of BP1−P2 DCB values for the current <strong>GPS</strong> satellite<br />

constellation. These values are a by-product from the global ionosphere analysis performed<br />

at CODE. The minimum-to-maximum value is about 13 nanoseconds (corresponding<br />

to approximately 24 TECU). For the GLONASS satellite constellation, the minimum-tomaximum<br />

value for the BP1−P2 DCB is, with about 22 nanoseconds, comparably big (see<br />

Figure 13.2).<br />

<strong>GPS</strong> BP1−C1 DCB values are shown in Figure 13.3. Compared with <strong>GPS</strong> BP1−P2 values,<br />

the order of magnitude of BP1−C1 values is approximately 3 times smaller: the minimum-tomaximum<br />

value is about 4 nanoseconds. Nevertheless, expressed in units of widelane cycles,<br />

this corresponds to a maximum inter-satellite BP1−C1 DCB of 1.4 cycles!<br />

Figures 13.1, 13.2, and 13.3 show, furthermore, that the individual PRN-specific DCB values<br />

are rather stable in time. Note that the daily DCB retrievals are indicated with dots, the<br />

30-day averages with circles. The day-to-day reproducibility is observed around 0.05 nanoseconds<br />

rms (for satellite bias retrievals responding to BP1−C1). Finally, it should be stated<br />

that it is common practice to impose a zero-mean condition on the set of DCB estimates<br />

(with respect to each <strong>GNSS</strong>) for datum definition. This implies that DCB results may be<br />

shifted by a common offset value, B0 (cf. Eqn. (13.1)).<br />

It is worth mentioning that updated versions of Figures 13.1, 13.2, and 13.3 may be found<br />

at http://www.aiub.unibe.ch/ionosphere/ [Schaer, 1998].<br />

Page 280 AIUB

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

Saved successfully!

Ooh no, something went wrong!