Fig. 1: Tracking network as considered in CODE’s GNSS final analysis for GPS week 1795.

Fig. 2: Number of GNSS satellites since 1994 as considered in CODE’s analysis. With a total of 56 operational GPS+GLONASS satellites, two full constellations were reached on February 2, 2012 (see IGS Mail #6538).

Fig. 3: Polar motion from 19-Jul-1993 to 10-Jun-2014 as monitored by CODE.

Fig. 4: Global mean TEC extracted from the Global Ionosphere Maps (GIMs) produced by CODE covering almost two solar cycles. The red curve shows the interpolated mean TEC based on a least-squares collocation. The daily averaged mean TEC values, namely the zero-degree coefficients of the spherical harmonic expansion used to represent the global TEC, are indicated by black dots.

Fig. 7: Differential code biases (DCB) results as computed at CODE: GPS P1-C1 from indirect estimation (as provided to the IGS, top left), GNSS P1-C1 from the direct approach (bottom left),

Highlights

Two consistent solution series, a clean one-day (COF) and a three-day long-arc (COD) solution, are generated in parallel.Rigorously combined processing of GPS and GLONASS observations has been performed since mid of 2003 as an essential step towards multi-constellation analysis. Meanwhile the GPS-only tracking stations are in the minority in our network (see Fig. 1 and 2).Continuous parameterization, particularly for Earth orientation parameters (EOP, Fig. 3), troposphere zenith path delays (ZPD) and horizontal gradients, as well as for ionosphere parameters (Fig. 4), allows the connection of the parameters at day boundaries.Completion of GNSS orbit products with respect to all transmitting GPS and GLONASS satellites without exception. Reliable accuracy code information is provided.Generation of uninterrupted orbit information for the satellites being repositioned (Fig. 5). Corresponding events are identified with a maneuver flag in the SP3c orbit files. An orbit initialization procedure is implemented for easy inclusion of brand new GNSS satellites, even if they do not provide broadcast navigation messages.Automatic verification of IGb08 fiducial sites for consistent datum definition in the final, rapid, and ultra-rapid analysis chains.Comprehensive CODE analysis summaries with extended orbit validation information and datum verification results.Independent GNSS orbit validation on the basis of SLR data (see poster from Sosnica et al. in PS10).GNSS ambiguity resolution: ambiguities are resolved for GPS and GLONASS observations with a self-calibrating procedure for handling of GLONASS-DPCB (differential phase-code biases).Phase pre-processing for short(est) baselines: The test criteria for checking the geometry-free LC are a function of the baseline length. This ensures that the original L1 and L2 observations are clean for short(est) baselines (with less than 20km length).Monitoring parameters are set up in the final solutions for internal use: Satellite(-specific) antenna offset and pattern. GLONASS-GPS bias parameters with respect to

station coordinates and troposphere ZPD. Scaling factors for higher-order ionosphere (HOI)

and non-tidal atmosphere pressure loading (APL) corrections.

Geocenter coordinates (GCC).Note: These parameters are contained in the daily NEQs that are archived. For efficiency reasons the monitoring parameters are removed from the NEQs before generating the final solution (see Fig. 6).Differential code bias (DCB) retrieval for P1-C1, P1-P2, P2-C2 with different algorithms (e.g., direct and indirect P1-C1 retrieval, Fig. 7).GLONASS frequency numbers are verified on a regular basis.SINEX result files are generated in all processing lines: final, rapid and even ultra-rapid.Fully automated GNSS data processing with the latest development version of the Bernese GNSS Software including BPE (Bernese Processing Engine). The processing is embedded in a system of Perl modules. This includes instant alerting in case of BPE processing and technical failures, general data flow problems, changes in the GNSS constellations.

International GNSS ServiceWorkshop 201423 June - 27 June 2014, Pasadena, USA

1 2 2 1 1R. Dach , S. Schaer , S. Lutz , D. Arnold ,H. Bock , 1 1 1 1E. Orliac , L. Prange , S. Bertone , Y. Jean ,1 1 1 1U. Meyer , K. Sośnica , P. Walser and A. Jäggi

1Astronomical Institute, University of Bern, Switzerland

2Federal Office of Topography swisstopo, Wabern, Switzerland

Activities at the CODEAnalysis Center

Poster compiled by E. Orliac, June 2014Astronomical Institute, University of Bern, Bernetienne.orliac@aiub.unibe.ch

IGSWS2014-PS01

Contact addressRolf DachAstronomical Institute, University of BernSidlerstrasse 53012 Bern (Switzerland)rolf.dach@aiub.unibe.ch

Most important new developments and model changesare reported in poster contributions for this IGS workshop (same session): Lutz et al.:

Updating the CODE ultra-rapid procedure Steigenberger et al.:

CODE Contribution to the 2nd IGS ReprocessingSee also: IGS technical reports 2012 and 2013.

RINEX issue in final clock procedure

In 2013, the IGS final clock combination revealed some recurrent problems with the contribution from CODE, resulting in a high number of exclusions in the IGS combination protocol. After some investigations, it appeared that the problem was due to unexpectedly different contents of the RINEX files for one and the same station and time interval from different sources: either downloaded directly as daily/hourly RINEX files with a sampling of 30 s or reconstructed from the 15-minutes RINEX files with the 1 Hz sampling based on real-time stream data. The latter ones are used at CODE to produce the 5 s clock product. The clock procedure was therefore adapted to guarantee that the 1 Hz data is only used to densify the clocks down to 5 s but not for generating the 30 s products.

Fig. 5: Geographical locations (subprints) of all repositioning events of GPS satellites since 2004 as determined by CODE.

Fig. 6: Parameter types in the CODE final solution; the gray shaded parameters are so-called monitoring parameters that are removed from the NEQs before generating the final solution (in order to avoid potential numerical problems and to speed up the computation).

GNSS P2-C2 from direct approach (bottom right), and GNSS P1-P2 from the ionosphere analysis (top right).

The CODE Consortium

Astronomical Institute of the Federal Office of TopographyUniversity of Bern, AIUB swisstopo(Bern, Switzerland) (Wabern, Switzerland)

Federal Agency for Carto‐ Institut fuer Astronomische undgraphy and Geodesy, BKG Physikalische Geodaesie, IAPG

0.10.20.30.40.50.6

-0.2

-0.1

0

0.1

0.2

0.3

Y Pole Component (Arcseconds)

X P

ole

co

mp

on

en

t (A

rcse

con

ds)

Earth Rotation Axis as Monitored by CODE

1994

1995

1996

1997

1998

1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011 2012

2013

2014

2014/06/13

1993/07/19

-5

-4

-3

-2

-1

0

1

2

3

4

5

DC

B(p

1c1

) in

ns

Satellites

G0

3

G0

4

G0

8

G0

9

G1

0

G2

6

G3

2

G0

1

G0

6

G2

4

G2

5

G2

7

G3

0

G11

G1

3

G1

4

G1

6

G1

8

G2

0

G2

1

G2

8

G0

2

G1

9

G2

2

G2

3

G0

5

G0

7

G1

2

G1

5

G1

7

G2

9

G3

1

G0

3

G0

4

G0

8

G0

9

G1

0

G2

6

G3

2

G0

1

G0

6

G2

4

G2

5

G2

7

G3

0

G11

G1

3

G1

4

G1

6

G1

8

G2

0

G2

1

G2

8

G0

2

G1

9

G2

2

G2

3

G0

5

G0

7

G1

2

G1

5

G1

7

G2

9

G3

1

BLOCK IIA BLOCK IIF BLOCK IIR-A BLOCK IIR-BBLOCK IIR-M

-20

-15

-10

-5

0

5

10

15

20

DC

B(p

1p

2)

in n

s

Satellites

R26

G03

G04

G08

G09

G10

G26

G32

G01

G06

G24

G25

G27

G30

G11

G13

G14

G16

G18

G20

G21

G28

G02

G19

G22

G23

G05

G07

G12

G15

G17

G29

G31

R01

R02

R03

R04

R05

R06

R07

R08

R09

R10

R11

R12

R13

R14

R15

R16

R17

R18

R19

R20

R21

R22

R23

R24

R26

G03

G04

G08

G09

G10

G26

G32

G01

G06

G24

G25

G27

G30

G11

G13

G14

G16

G18

G20

G21

G28

G02

G19

G22

G23

G05

G07

G12

G15

G17

G29

G31

R01

R02

R03

R04

R05

R06

R07

R08

R09

R10

R11

R12

R13

R14

R15

R16

R17

R18

R19

R20

R21

R22

R23

R24

BLOCK IIA BLOCK IIF BLOCK IIR-ABLOCK IIR-B BLOCK IIR-M GLONASS-M

-5

-4

-3

-2

-1

0

1

2

3

4

5

DC

B(p

1c1

) in

ns

Satellites

R26

G03

G04

G08

G09

G10

G26

G32

G01

G06

G24

G25

G27

G30

G11

G13

G14

G16

G18

G20

G21

G28

G02

G19

G22

G23

G05

G07

G12

G15

G17

G29

G31

R01

R02

R03

R04

R05

R06

R07

R08

R09

R10

R11

R12

R13

R14

R15

R16

R17

R18

R19

R20

R21

R22

R23

R24

R26

G03

G04

G08

G09

G10

G26

G32

G01

G06

G24

G25

G27

G30

G11

G13

G14

G16

G18

G20

G21

G28

G02

G19

G22

G23

G05

G07

G12

G15

G17

G29

G31

R01

R02

R03

R04

R05

R06

R07

R08

R09

R10

R11

R12

R13

R14

R15

R16

R17

R18

R19

R20

R21

R22

R23

R24

BLOCK IIA BLOCK IIF BLOCK IIR-ABLOCK IIR-B BLOCK IIR-M GLONASS-M

-5

0

5

DC

B(p

2c2

) in

ns

Satellites

G0

1

G0

6

G2

4

G2

5

G2

7

G3

0

G0

5

G0

7

G1

2

G1

5

G1

7

G2

9

G3

1

R0

1

R0

2

R0

3

R0

4

R0

5

R0

6

R0

7

R0

8

R0

9

R1

0

R11

R1

2

R1

3

R1

4

R1

5

R1

6

R1

7

R1

8

R1

9

R2

0

R2

1

R2

2

R2

3

R2

4

G0

1

G0

6

G2

4

G2

5

G2

7

G3

0

G0

5

G0

7

G1

2

G1

5

G1

7

G2

9

G3

1

R0

1

R0

2

R0

3

R0

4

R0

5

R0

6

R0

7

R0

8

R0

9

R1

0

R11

R1

2

R1

3

R1

4

R1

5

R1

6

R1

7

R1

8

R1

9

R2

0

R2

1

R2

2

R2

3

R2

4

BLOCK IIF BLOCK IIR-M GLONASS-M

Receivers included: GPS/GLONASS (195) only GPS (60)

0

5

10

15

20

25

30

35

40

45

50

55

60

Num

ber

of sa

telli

tes

50000 51000 52000 53000 54000 55000 56000

MJD

0

5

10

15

20

25

30

35

40

45

50

55

60

Num

ber

of sa

telli

tes

50000 51000 52000 53000 54000 55000 56000

MJD

0

5

10

15

20

25

30

35

40

45

50

55

60

Num

ber

of sa

telli

tes

50000 51000 52000 53000 54000 55000 56000

MJD

94 95 96 97 98 99 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14

GPSGLONASStotal

1 10 100 1000

Velocity changes in mm/s

Posters and other publications from theAIUB Satellite Geodesy Group:http://www.bernese.unibe.ch/publist