Next Article in Journal
The Benefits of the Ka-Band as Evidenced from the SARAL/AltiKa Altimetric Mission: Quality Assessment and Unique Characteristics of AltiKa Data
Next Article in Special Issue
Weighting of Multi-GNSS Observations in Real-Time Precise Point Positioning
Previous Article in Journal
Tracking of a Fluorescent Dye in a Freshwater Lake with an Unmanned Surface Vehicle and an Unmanned Aircraft System
Previous Article in Special Issue
Spatiotemporal Evaluation of GNSS-R Based on Future Fully Operational Global Multi-GNSS and Eight-LEO Constellations
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

Investigation on Reference Frames and Time Systems in Multi-GNSS

Department of Geosciences, University of Padova, 35131 Padova, Italy
*
Author to whom correspondence should be addressed.
Remote Sens. 2018, 10(1), 80; https://doi.org/10.3390/rs10010080
Submission received: 24 November 2017 / Revised: 18 December 2017 / Accepted: 3 January 2018 / Published: 9 January 2018

Abstract

:
Receivers able to track satellites belonging to different GNSSs (Global Navigation Satellite Systems) are available on the market. To compute coordinates and velocities it is necessary to identify all the elements that contribute to interoperability of the different GNSSs. For example the timescales kept by different GNSSs have to be aligned. Receiver-specific biases, or firmware-dependent biases, need to be calibrated. The reference frame used in the representation of the orbits must be unique. In this paper we address the interoperability issues from the standpoint of a Single Point Positioning (SPP) user, i.e., using pseudoranges and broadcast ephemeris. The biases between GNSSs timescales and receiver-dependent biases are analyzed for a set of 31 MGEX (Multi-GNSS Experiment) stations over a time span of more than three years. Time series of biases between timescales of GPS (Global Positioning System), GLONASS (Global Navigation Satellite System), Galileo, BeiDou, QZSS (Quasi-Zenith Satellite System), SBAS (Satellite Based Augmentation System) and NAVIC (Navigation with Indian Constellation) are investigated, in addition to the identification of events like discontinuity of receiver-dependent biases due to firmware updating. The GPS broadcast reference frame is shown to be aligned to the one (IGS14) realized by the precise ephemeris of CODE (Center for Orbit Determination in Europe) to within 0.1 m and 2 milliarcsec, with values dependent on whether IIR-A, IIR-B/M or IIF satellite blocks are considered. Larger offsets are observed for GLONASS, up to 1 m for GLONASS K satellites. For Galileo the alignment of the broadcast orbit to IGS14/CODE is again at the 0.1 m and several milliarcsec level, with the FOC (Full Operational Capability) satellites slightly better than IOV (In Orbit Validation). For BeiDou an alignment of the broadcast frame to IGS14/CODE comparable to GLONASS is observed, regardless of whether IGSO (Inclined Geosynchronous Orbit) or MEO (Medium Earth Orbit) satellites are considered. For all satellites, position differences according to the broadcast ephemeris relative to IGS14/CODE orbits are projected to the radial, along-track and crosstrack triad, with the largest periodic differences affecting mostly the along track component. Sudden discontinuities at the level of up to 1 m and 2–3 ns are observed for the along-track component and the satellite clock, respectively. The time scales of GLONASS, Galileo, QZSS, SBAS and NAVIC are very closely aligned to GPS, with constant offsets depending on receiver type. The offset of the BeiDou time scale to GPS has an oscillatory pattern with peak-to-peak values up to 100 ns. To characterize receiver-dependent biases the average of six Septentrio receivers is taken as reference, and relative offsets of the other receiver types are investigated. These receiver-dependent biases may depend on the individual station, or for the same station on the update of the firmware. A detailed calibration history is presented for each multiGNSS station studied.

Graphical Abstract

1. Introduction

As part of the contribution of the University of Padova to the MGEX program [1] and to the activities of the MultiGNSS Working Group within [2], 31 European GNSS sites have been monitored since 2014 with five different receivers (Javad, Leica, Septentrio, Topcon, Trimble). The location of the sites is shown in Figure 1 and the equipment at each site is described in Table 1. Three issues which are critical for the interoperability of the different GNSS constellations are considered from the user point of view:
  • Alignment of the spatial reference frame implied by the broadcast orbits to a common frame aligned to ITRF (International Terrestrial Reference Frame), such as the one implied by the preciseephemeris of CODE (Center for Orbit Determination in Europe) at the University of Bern.
  • Offset among the time scales of different GNSS constellations: are the reference time scale of the various GNSSs synchronized among each other?
  • Do different receivers measure different offsets? Does the receiver dependent offset change subject e.g., to a firmware update?
GPS, GLONASS, Galileo and BeiDou are the systems taken into account. For some receivers at higher latitude (e.g., KIRU, Kiruna, Sweden; WROC, Wroclaw, Poland; NYA2, Ny Alesund, Svalbard; DLF1, Delft, The Netherlands; GANP, Ganovce, Slovak Republic) QZSS data are also available. A Septentrio receiver has also delivered data from the Indian NAVIC (formerly IRNSS) constellation. SBAS data are received from satellites S27 and S28, both belonging to the Indian overlay system GAGAN (GPS Aided Geo Augmented Navigation) in geostationary orbits. No data usable for positioning are available from other SBAS systems.
This paper is organized in two parts. In the first part, the offset between broadcast reference frames and ITRF has been evaluated, together with a comparison between broadcast and precise orbits and clocks. This part is described in Section 2. The second part of the paper focuses on the misalignment of the time scales adopted by GNSSs, and is described in Section 3 and Section 4.
Montenbruck et al. [3] have carried out a similar analysis for the whole of 2013. In their study, they evaluate the signal-in-space ranging error (SISRE), which describes the error contributions due to broadcast orbits and clocks. They found that the GPS broadcast ephemerides show the best accuracy, with a RMS (Root Mean Square) orbit error of 0.18, 1.05 and 0.44 m in radial, along-track and cross-track directions respectively, and 2 ns as clock errors. For the other GNSS systems they found errors two to three times higher. The computed SISRE values confirm the better accuracy of GPS orbits compared to other GNSS’s, since the global average SISRE values are 0.7 ± 0.02 m (GPS), 1.5 ± 0.1 m (BeiDou), 1.6 ± 0.3 m (Galileo) and 1.9 ± 0.1 m (GLONASS). These results apply to data available in 2013. Since then the quality of the signals and orbits have considerably improved, and a re-evaluation of the whole issue is justified.
MATLAB-based multiGNSS software (The MathWorks, Inc., Natick, MA, USA) is used for this purpose [4], which allows the estimation at each epoch of the three receiver coordinates, one Tropospheric Zenith Delay and nGNSS receiver time offsets, where nGNSS is the number of tracked GNSS constellations. The latter unknowns are the sums of the receiver clock offset and the offset of the GNSS time scale relative to a common, interGNSS time scale [5]. Differentiation of such an offset relative to the GPS data yields, epochwise and for each receiver, estimates of the GNSS time offset to GPS. Comparing across different receivers it can be seen that such offsets can be biased relative to each other by as much as several tens of nanoseconds. The average of six Septentrio receivers was arbitrarily selected as reference to estimate the receiver biases relative to the average Septentrio. For a given receiver brand, the bias relative to Septentrio for the various GNSS is very repeatable, with a few exceptions. It turns out that updating the firmware often affects the GNSS-dependent receiver bias. There are however examples of changes of the receiver-dependent bias which are uncorrelated with a firmware update. A table of “individual” calibrations, for each receiver and each GNSS time offset is presented.

2. Quality Check of Broadcast Orbits

To study the accuracy of the broadcast orbits relative to the precise orbits provided by CODE [6] SP3 (Extended Standard Product 3 Orbit Format), the alignment of the reference systems adopted by broadcast orbits with respect to that provided by precise orbits is analyzed. The reference frames adopted by the several GNSSs in the broadcast ephemeris are different from each other, namely WGS84 (GPS), PZ-90.11 (GLONASS), GTRF (Galileo) and CGCS2000 (BeiDou), whereas the reference frame adopted by precise orbits is typically unique. According to [7,8], current GLONASS broadcast ephemerides and all those since 31 December 2013 should be referred to PZ-90.11 as it is aligned to ITRF at millimeter level. The reference frame adopted by CODE during week 1950 is IGS14.
Broadcast and precise orbits are referred to different points of space vehicles: the antenna phase center (APC) and the center of mass (CoM), respectively. The relative distance of APC to CoM is the antenna phase offset (APO). Montenbruck et al. [3] decided not to apply any reference frame transformation in their comparative analysis. They inferred the APO from the comparison between broadcast and precise orbits except for BeiDou, for which they assumed that the broadcast ephemeris is referred to the CoM.
In this section the coordinate differences in the RSW (radial, along-track, cross-track) reference system (Figure 2) are also analyzed and computed on the post-fit residuals of the seven-parameter Helmert transformation [9] between broadcast and precise ephemeris, for each day and satellite of the four GNSSs: GPS, GLONASS, Galileo, BeiDou. To achieve this goal, the Bernese software [10] was used with a maximum threshold of 5 m as a condition for coordinate rejection.

2.1. Comparison of Reference Systems

The study focuses on GPS week 1950, i.e., from 21 May 2017 to 27 May 2017. For each day a set of Helmert parameters are obtained, which define the transformation from precise to broadcast reference systems, and consist of three translations (Tx, Ty, Tz), three rotations (Rx, Ry, Rz) and one scaling factor (k) according to Equation (1).
[ x y z ] = [ T x T y T z ] + ( 1 + k ) [ 1 R z R y R z 1 R x R y R x 1 ] [ x y z ]
The weekly average values of each Helmert parameter has been computed. With these mean values the broadcast reference systems relative to precise reference system have been represented. Figure 3, Figure 4, Figure 5 and Figure 6 show the rotations magnified in order to be visible (milliarcsecs are treated as degrees). The figure also contains a table with the sets of mean Helmert parameters and their standard deviation, for each block of satellites. Translations are measured in meters, rotations in milliarcsec and the scaling factor is expressed in μm/km (1 μm = 10−6 m).
Precise orbits refer to CoM whereas broadcast orbits refer to APC. The relative distance between APC and CoM is the APO (Antenna Phase Offset). Among the three (x, y, z) APO components, the z component, which correspond to the boresight direction, is the prevalent one. Since APO is constant, the satellite orbits described by CoM and APC differ mainly by the constant offset given by the boresight component of APO, which is oriented in radial direction. So we assume that APO is absorbed by the scale factor of Helmert transformation.
For GPS and Galileo FOC (Full Operational Capability) satellites, the reference systems adopted by broadcast orbits are quite similar to those provided by precise orbits: the translation of the origin is less than 0.10 m and rotations are less than 2 milliarcsec. For Galileo IOV (In Orbit Validation), GLONASS and BeiDou higher differences are apparent. The Galileo IOV broadcast reference frame is offset to ITRF by at most 0.23 ± 0.04 m in Y (Figure 5).
The GLONASS M broadcast reference frame is offset to ITRF by at most 0.27 ± 0.05 m in Y and the maximum rotation is 4 ± 2 milliarcsec of arc about Y. The GLONASS K broadcast reference frame is offset to ITRF by at most 1.06 ± 0.18 m in Y and the maximum rotation is 19 ± 2 milliarcsec about X (Figure 4).
The BeiDou IGSO broadcast reference frame is offset to ITRF by at most 0.31 ± 0.08 m in Y and the maximum rotation is 3.6 ± 2.0 milliarcsec about Z (Figure 6). For BeiDou MEO satellites we find Helmert parameters of the same order of magnitude of those found for IGSO satellites, but with a higher uncertainty. This margin of error is probably due to the limited number of available satellites (only three). The BeiDou MEO broadcast reference frame is offset to ITRF by at most 0.38 ± 0.35 m in X and the maximum rotation is 4.3 ± 2.9 milliarcsec about Z (Figure 6).

2.2. RSW Components of Coordinate Differences and Clock Differences

Coordinate differences of broadcast vs. precise ephemeris of GPS are generally continuous. There are however occasional discontinuities, which affect mostly the along-track components. The coordinate differences in the radial and cross-track components may have an oscillatory pattern with a period of about 12 h. The average values of standard deviations are 0.15, 0.71, 0.34 m and 1.1 ns for the radial, along-track, cross-track and clock component, respectively.
As to the satellite clocks, it is found that all satellites are equipped with atomic rubidium clocks, except G08 and G24, which are equipped with cesium atomic clocks and belong to block IIF. The average values of clock differences range between −3.4 and 2.0 ns.
The magnitude of discontinuities is up to 0.3, 1.5, 0.2 m and 1 ns for the radial, along-track, out-of-plane and clock component, respectively. Mean values and standard deviations of coordinates and clock differences for each satellite are reported in Table 2. The complete time series of coordinates and clock differences for all GPS satellites are shown in Figure A1.
GLONASS coordinate and clock differences show an oscillating trend, with a period of about 12 h, and discontinuities, which affect mostly the along-track and clock components. The average values of standard deviations are 0.48, 1.35, 0.74 m and 5.6 ns for the radial, along-track, cross-track and clock component, respectively. Average values of clock differences are different from one satellite to another, varying from −20 to 24 ns. The magnitude of discontinuities is up to 0.3, 3.0, 0.3 m and 8 ns for the radial, along-track, out-of-plane and clock component, respectively.
Mean values and standard deviations of coordinates and clock differences for each satellite are reported in Table 3. The complete time series of coordinates and clock differences for all GLONASS satellites are shown in Figure A2.
BeiDou coordinate and clock differences show discontinuities, which affect mostly the along-track, especially for Medium Earth Orbit (MEO) satellites (C11, C12, C14), and clock components. Furthermore coordinate differences show an oscillating trend, with a period of about 12 h for MEO satellites and about a whole day for the other satellites (Inclined Geosynchronous Satellite Orbit—IGSO). The average values of standard deviations are 0.43, 0.81, 0.63 m and 2.3 ns for the radial, along-track, cross-track and clock component, respectively (except clock RMS of C11, for which a higher standard deviation is found, about 27 ns, due to two large discontinuities). Average values of clock differences are different from one satellite to another, varying from 56 ns to 122 ns. The magnitude of discontinuities is up to 0.3, 1 (IGSO) or 3 (MEO), 0.3 m and 5 ns for the radial, along-track, cross-track and clock component, respectively.
Mean values and standard deviations of coordinates and clock differences for each satellite are reported in Table 4. The complete time series of coordinates and clock differences for all BeiDou satellites are shown in Figure A3.
For Galileo, it is important to remember that three types of ephemeris are available: I/NAV E1-B, F/NAV E5a and I/NAV E5b. I/NAV E1-B ephemeris has been chosen because this type of ephemeris is updated more frequently in the timeframe considered. Referring to Galileo ICD (Interface Control Document) [11], I/NAV blocks with Health Status equal to 1 (Signal out of service) have been rejected and others accepted. Of the 17 satellites, 11 are found to have a SV health value of 0, which means Data Validity Status = “Navigation Data Valid” and Health status = “Signal OK”. For the other six satellites the same value is 455, which means Data Validity Status = “Working without guarantee” and Health status = “Signal Component currently in Test”. These satellites are the last four launched on 17 November 2016 (E03, E04, E05, E07) and the two launched on 22 August 2014 (E14, E18) into non nominal elliptical orbit [12]. The week analyzed is later than the epochs of orbit circularization, which were concluded in December 2014 and March 2015, respectively.
For Galileo, gaps have been found in the spacing between I/NAV ephemeris blocks larger than the validity period of the ephemeris block, i.e., ±3600 s. This prevents the computation of satellite coordinates and clock in the gaps. The availability of broadcast ephemeris is shown in Figure 7, where each block of healthy ephemeris is plotted with a circular black marker and each block of unhealthy ephemeris is plotted with a cross-shaped gray marker. In the studied days all the ephemeris blocks were set to healthy. In the periods of continuity of validity of ephemeris, it is possible to notice discontinuities in satellite coordinates (mostly in the along-track component) and clock.
For Galileo, the coordinate differences show an oscillating trend with a period of about 12 h. The average values of standard deviations are 0.14, 0.29, 0.16 m and 1.3 ns for the radial, along-track, cross-track and clock component, respectively. The average values of clock differences range between 0.7 and 7.8 ns. The magnitude of discontinuities is up to 0.2, 1.0, 0.3 m and 2 ns for the radial, along-track, cross-track and clock component, respectively.
E14 and E18 show scattered coordinate differences with very large (>5 m) values, so about 75% of coordinates are rejected by Bernese and not considered in the estimating of Helmert parameters. Their clock differences show an offset of about 4–8 ns, with the same standard deviation of the other satellites.
Mean values and standard deviations of coordinates and clock differences for each satellite are reported in Table 5. The coordinate and clock accuracy of In-Orbit Validation (IOV) satellites is consistent with that of the Full Operational Capability (FOC) satellites. Both generations of satellites are equipped with passive hydrogen maser (PHM) clocks. The complete time series of coordinates and clock differences for all Galileo satellites are shown in Figure A4.

3. Data Used and Adopted Model of the Pseudorange

RINEX (Receiver Independent Exchange Format) 3.x [13] observation data was used for all receivers except Topcon, for which the provided RINEX 2.x files are converted to RINEX 3.x with the utility gfzrnx of the German Research Centre for Geosciences (GFZ) [14]. As to the orbits, satellite clocks and other ancillary data (e.g., quality flags), broadcast ephemeris in RINEX format downloaded from the MGEX FTP servers was used [1].
Several codes are available in the carriers at several frequencies, for the different GNSS constellations. The well-known “iono-free” linear combination of dual frequency code observations was used in order to remove first order ionospheric delay [9]. Table 6 summarizes the GNSS specific frequency bands and observation codes. The GPS broadcast clock model refers to iono-free combination of precise codes, i.e., C1W-C2W. We decided to analyze the combination C1C-C2W because about half of the stations (more precisely all the Leica and Trimble stations) do not track C1W. The error introduced using C1C in place of C1W depends on GPS satellite and varies between about −1 and 1 m. This means about ±3 nanoseconds which is within the accepted tolerance. For GLONASS, the k factor varies from −7 to +6 according to the satellite [15]: such information is provided in the header of the observation RINEX file. For Galileo the I/NAV combination of codes and the related navigation message is used [11].
The model of the pseudorange p(t) is described in Equations (2)–(6). In Equation (2) the effect of the Differential Code Bias (DCB) as listed in files provided by CODE has been ignored. For GPS the DCBs are up ±2 nanoseconds which is within our error budget. For GLONASS the DCBs are station-dependent and the estimates are provided only for a small subset of stations, for the other constellations no DCBs are provided (ftp://igs.bkg.bund.de/IGS/products/mgex/). Table 7 contains the explanation of the variables. The matrix of partial derivatives is shown in Equation (7), where seven GNSS are considered: GPS, GLONASS, Galileo, BeiDou, QZSS, NAVIC and GAGAN. The term ρ indicates the geometric range between satellite and receiver.
In Equation (8) y is defined as the column vector of observed minus computed: each element of y is the difference between iono-free linear combination of pseudoranges and the right side of Equation (2). The number of elements of y is equal to the number of satellites in view.
The column vector of the solution, denoted as x, is the solution of the normal equations expressed by Equation (8). The vector x consists of three coordinates, n terms TSCX + dTRec, where n is the number of GNSS’s considered, and one TZD (Tropospheric Zenith Delay). The explicit form of the solution is given in Equation (9). Term TSCX is a GNSS-specific Time System Correction, which is dependent on the GNSS but independent of the receiver. Term dTRec is the receiver clock offset, which is independent of the GNSS. However we will see later that different receivers measure different TSCX implying receiver biases which are dependent both on the receiver and the GNSS [16]. To monitor the GNSS specific time offset it is convenient to take TSCG as the reference time scale and evaluate the difference (TSCX + dTRec) − (TSCG + dTRec), with X referring to all the GNSS’s different from GPS [17]. In such a way we obtain the sum of the system specific time offset relative to GPS and the receiver hardware inter-system bias (ISB) [17,18,19]. Table 8 lists these specific variables.
p ( t ) = ϱ c · d t ( t ) + c · ( T S C X + d T R e c ) + T Z D sin ( E l )
ϱ ϱ = [ X ( t ) + Y ( t ) · ω e · t o f x ] 2 + [ Y ( t ) X ( t ) · ω e · t o f y ] 2 + [ Z ( t ) z ] 2
d t ( t ) = a 0 + a 1 · ( t T o c L S ) + a 2 · ( t T o c L S ) 2 + d T R e l
d T R e l = 2 · ( X ¯ · v ¯ ) c 2
t o f = ( X x ) 2 + ( Y y ) 2 + ( Z z ) 2 c
H=[ x 1G x 0 ϱ 1G y 1G y 0 ϱ 1G z 1G z 0 ϱ 1G 1000000 1 sine l 1G x 2G x 0 ϱ 2G y 2G y 0 ϱ 2G z 2G z 0 ϱ 2G 1000000 1 sine l 2G x nG x 0 ϱ nG y nG y 0 ϱ nG z nG z 0 ϱ nG 1000000 1 sine l nG x 1R x 0 ϱ 1R y 1R y 0 ϱ 1R z 1R z 0 ϱ 1R 0100000 1 sine l 1R x nR x 0 ϱ nR y nR y 0 ϱ nR z nR z 0 ϱ nR 0100000 1 sine l nR x 1E x 0 ϱ 1E y 1E y 0 ϱ 1E z 1E z 0 ϱ 1E 0010000 1 sine l 1E x nE x 0 ϱ nE y nE y 0 ϱ nE z nE z 0 ϱ nE 0010000 1 sine l nE x 1C x 0 ϱ 1C y 1C y 0 ϱ 1C z 1C z 0 ϱ 1C 0001000 1 sine l 1C x nC x 0 ϱ nC y nC y 0 ϱ nC z nC z 0 ϱ nC 0001000 1 sine l nC x 1J x 0 ϱ 1J y 1J y 0 ϱ 1J z 1J z 0 ϱ 1J 0000100 1 sine l 1J x 1I x 0 ϱ 1I y 1I y 0 ϱ 1I z 1I z 0 ϱ 1I 0000010 1 sine l 1I x nI x 0 ϱ nI y nI y 0 ϱ nI z nI z 0 ϱ nI 0000010 1 sine l nI x 1N x 0 ϱ 1N y 1N y 0 ϱ 1N z 1N z 0 ϱ 1N 0000001 1 sine l 1N x nN x 0 ϱ nN y nN y 0 ϱ nN z nN z 0 ϱ nN 0000001 1 sine l nN ]
( H T H ) x = H T y
x = [ Δ x Δ y Δ z T S C G + d T R e c T S C R + d T R e c T S C E + d T R e c T S C C + d T R e c T S C J + d T R e c T S C I + d T R e c T S C N + d T R e c T Z D ]

4. Results of the Positioning Analyses

Daily analysis has been performed on the 31 stations listed in Table 1 and shown in Figure 1 starting from 1 January 2014 and is currently ongoing. Figure 8 shows the time series of GLGP, GPGA, BDGP and QZGP, distinguishing between the five types of receiver.
In the GLGP time series a very large misalignment of about −400 ns from the beginning of the analyses until mid-August 2014 can be seen. Then a re-aligning procedure started and was completed at the end of 2014. From the beginning of 2015 the GLONASS time scale is generally kept aligned with GPS, but several short-term variations with amplitudes ranging from tens to about one hundred ns are evident. The largest variation observed happened from July to December of 2016, and has a sinusoidal shape with an amplitude of about 100 ns.
BDGP varies continuously, with an oscillating trend and amplitude of about 70 ns. Furthermore the oscillations have a positive mean, which results in an average positive offset of the BeiDou time scale with respect to GPS. Considering a time series of more than three years it is possible to notice a slow trend toward zero, but it is not clear if this long-term variation is effectively a re-alignment procedure of the BeiDou time scale to GPS.
GPGA is aligned with GPS, since the time offset series are almost constant in time and centered to zero. Two sudden variations took place in November 2015 and November–December 2016, measuring about 60 and 30 ns, respectively.
The QZGP system time is aligned with GPS, but unfortunately for this system data from only five of the 31 stations is available. Among these five stations, Leica and Trimble receivers show higher scattered results compared to those of Septentrio and Javad, despite the global average value is very close to zero. It is important to notice that until June of 2017 there was only one satellite belonging to QZSS, so QZGP actually represents the time offset between this single satellite and GPS.

4.1. Differential Time Offset

A receiver-dependent bias is clearly visible in Figure 8, as previously noted by [17,20,21]. In order to better investigate this receiver dependent bias, the time series relative to the mean values of Septentrio stations have been differentiated. The choice of Septentrio is due to the observation that these stations show very similar values: for each day the RMS is generally lower than 3 ns. Figure 9 shows the time series of GLGP, GPGA and BDGP obtained for individual Septentrio stations. The QZGP time series is not shown since there is only one station among the six Septentrio stations which tracks this constellation.
The graph of GPGA in Figure 10 starts from 9 October 2015 due to the high scatter observed before this date. From these graphs the receiver dependent bias can be monitored. It is worth noting that for a given receiver type, some stations show similar time offsets, so their time series are quite superimposed, whereas other stations show different values and this difference seems to be constant in time. For example in Figure 10a it is possible to notice that the Trimble and Javad receivers have very similar time offsets, whereas Leica and Topcon show a relative bias up to tens of nanoseconds.
In Figure 10a a discontinuity of several Leica stations from about 40 ns to about −25 ns in the first half of 2016 is evident. These stations are: CAEN, M0SE, MLVL, PADO, REYK (Table 1). Taking into account the station logsheets it was possible to identify an exact connection between some of the discontinuities in the time offset series and receivers’ firmware updates. For example, considering the five Leica stations mentioned above, the correspondence between the discontinuity in the GLGP time offset and the update of receivers firmware for M0SE, PADO and REYK could be observed.

4.2. Analysis of Other Constellations: NAVIC and GAGAN

The multiGNSS software [4] has the capability to analyze the observations from NAVIC and SBAS, in addition to GPS, GLONASS, Galileo, BeiDou and QZSS. Septentrio has kindly made available RINEX data of days 25–29 May 2017 from their station located in Brussels (not listed in Table 1). This gave the opportunity to analyze the NAVIC time offsets for these five days. This station is equipped with a POLARX5 5.11 receiver, referred to as SEPT hereafter. It is worth noting that the observation data of the NAVIC satellites are available for the L5 carrier only, for which NAVIC has been processed in single frequency.
Figure 11a shows the results. The offset of NAVIC time scale relative to GPS is colored in purple. The NAVIC time offset is characterized by a daily variation which can reach 20 ns. Across the five days, NAGP seems to be quite constant, with a mean value of about −85 ± 9 ns.
Figure 11b shows the time offsets of SEPT differentiated to the other six Septentrio stations currently analyzed. GLGP and BDGP are smaller than those of other stations, whereas GPGA is very close. More in detail, the difference of GLGP varies suddenly from −16.5 to −7.5 ns on 26 May 2017, with a standard deviation of 3 ns. The GPGA of six Septentrio stations show spikes at 12:00 and 24:00 of each day, whereas SEPT does not. Otherwise the alignment is within 1 ns. The difference of BDGP is almost constant, with a mean value of about −12.5 ± 5 ns.
For SBAS data for satellites S27 and S28, both belonging to the Indian overlay system GAGAN in geostationary orbits have been used. These satellites are tracked by seven stations (DLF1, KIRU, REDU, TLSE, WTZ3, WTZZ, ZIMJ). The GAGAN data were analyzed only from 25 September 2016, so as yet not enough results are available to perform a calibration of the GAGAN time offset like those described in the previous paragraph.
Figure 12 shows the results obtained. Trimble stations give higher offsets, Javad stations give lower offsets and Septentrio stations give offsets comprised of those from the previous two receiver types. Septentrio GNGP seems to be quite constant in time, whereas for Trimble and Javad higher variations are observed.

5. Discussion

The observed correspondences between the discontinuities in the time offset series and receiver firmware updates suggest a relationship between the two events. In order to better investigate this relationship, the information about receiver set up and the time offsets relative to Septentrio have been summarized in Table 9. In this table the marker name of a station is followed by a lowercase letter if at least one discontinuity in time offset series is observed. The lowercase letter indicates a continuity period of time offsets, so a station name associated with the same letter has the same time offsets.
For each station every row corresponds to a new receiver set up or new time offsets relative to Septentrio, or both the events: in this case the discontinuity of time offsets corresponds to an update of receiver set up. These correspondences are highlighted by using a bold font.
A total number of 19 discontinuities have been identified. Among these, 11 are connected to receiver updates and six are due to unknown causes. Two of the 11 discontinuities connected to a receiver update involve also the antenna: COMOc and GANPc, as it can be noticed in Table 1. The other two discontinuities are linked to changes in antenna configuration: TLSEb shows a discontinuity on 11 March 2016, when the alignment from Nord was changed from 0 to −140 degrees, WTZZb shows a discontinuity on 13 July 2015, when the ARP (Antenna Reference Point) Up was changed from 0.045 to 0.284 m.
In Table 9 there are 92 receiver firmware updates, only 11 of these are connected with a discontinuity in time offset. So most of the receiver updates do not imply a discontinuity in time offset. Conversely more than half of the discontinuities in time offsets are connected to an update of receiver firmware. For these reasons it is necessary to keep monitoring both the configuration changes of receivers and the time series of time offsets.

6. Conclusions

In the present work a study of the accuracy of broadcast orbits has been presented, taking into account a time span of one week. In this phase, the offset between broadcast reference frames and ITRF has been evaluated, for homogeneous blocks of satellites. The results of an analysis carried out starting from 1 January 2014 and still active were presented, aimed at the evaluation of the misalignment between timescales of the various GNSS’s. In the next sections the main results obtained are summarized and discussed.

6.1. Reference Frames

Reference frames adopted by GPS and Galileo FOC broadcast orbits, in the week taken into account, are aligned with ITRF since the translation of the origin is less than 0.10 m and rotations are less than 2 milliarcsec. For Galileo IOV, GLONASS and BeiDou instead translations at dm-level and rotations higher than 4 milliarcsec have been found.
The Galileo IOV broadcast reference frame is offset to ITRF by at most 0.23 ± 0.04 m in Y.
The GLONASS M broadcast reference frame is offset to ITRF by at most 0.27 ± 0.05 m in Y and the maximum rotation is 4 ± 2 milliarcsec about Y. The GLONASS K broadcast reference frame is offset to ITRF by at most 1.06 ± 0.18 m in Y and the maximum rotation is 19 ± 2 milliarcsec about X.
The BeiDou IGSO broadcast reference frame is offset to ITRF by at most 0.31 ± 0.08 m in Y and the maximum rotation is 3.6 ± 2.0 milliarcsec about Z. BeiDou MEO broadcast reference frame is offset to ITRF by at most 0.38 ± 0.35 m in X and the maximum rotation is 4.3 ± 2.9 milliarcsec about Z.

6.2. Coordinates and Clock Comparison

In general coordinate and clock differences have been demonstrated to be discontinuous and show an oscillating trend with a period of about 12 h (except BeiDou IGSO satellites which have a period of about 24 h). The discontinuities affect mostly the along-track component, in which they are about 1 m for GPS, Galileo and BeiDou IGSO and up to 3 m for GLONASS and BeiDou MEO, and to a lesser extent the radial and cross-track components, in which they are at dm-level.
GPS and Galileo broadcast ephemeris are closer to the precise orbits than those of GLONASS and BeiDou: for GPS and Galileo the average values of RMS are about 0.15 m and 1 ns whereas for GLONASS the average RMSs are 0.48 m and 5.6 ns and for BeiDou 0.43 m and 2.2 ns.

6.3. GNSS’s Time Offsets

GLONASS time scale was misaligned with respect to GPS by about −400 ns until the summer of 2014, when an alignment procedure started, according to [8]. This procedure was completed at the beginning of 2015, so currently the GLONASS timescale is aligned with GPS. Despite this the alignment is not constant, and there may be non-predictable variations with amplitude up to 100 ns, like the one that happened in the second half of 2016.
BeiDou timescale is not aligned with GPS. The time offset vary continuously, with an oscillating trend and amplitude of about 70 ns. Furthermore it is not centered to zero, but it is always positive, although a slow trend of the average value to zero has been detected.
Galileo and QZSS time scales are aligned with GPS, although for Galileo two sudden variations, in November of 2015 and November–December of 2016, of about 60 and 30 ns, respectively, were noticed.
In addition to the previous constellation-specific considerations, for each time offset a receiver-dependent Inter System Bias (ISB) which could reach several tens of nanoseconds was evident. This bias tends to be almost constant in time, and so it could be calibrated. Since ISB is receiver-dependent, an upgrade of receiver firmware can change its amount and a new calibration is required.
The time offsets of 31 IGS/EUREF stations since 1 January 2014 were monitored. For each station, the potential discontinuities in time series of time offsets have been detected, and whenever possible the cause of discontinuity has been identified. Hence, for each continuity interval a relative-to-Septentrio calibration of time offsets has been evaluated.

Author Contributions

Luca Nicolini analyzed the data and wrote the paper; Alessandro Caporali conceived the model and supervised the work.

Conflicts of Interest

The authors declare no conflict of interest.

Appendix A

Figure A1. GPS coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Figure A1. GPS coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Remotesensing 10 00080 g0a1aRemotesensing 10 00080 g0a1b
Figure A2. GLONASS coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Figure A2. GLONASS coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Remotesensing 10 00080 g0a2aRemotesensing 10 00080 g0a2b
Figure A3. BeiDou coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Figure A3. BeiDou coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Remotesensing 10 00080 g0a3aRemotesensing 10 00080 g0a3b
Figure A4. Galileo coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Figure A4. Galileo coordinates and clock differences. “max 5” refers to the maximum threshold of 5 m as a condition for coordinate rejection.
Remotesensing 10 00080 g0a4

References

  1. The Multi-GNSS Experiment and Pilot Project (MGEX). Available online: http://mgex.igs.org (accessed on 29 September 2017).
  2. EUREF Technical Working Group (TWG). Available online: www.euref.eu/euref_twg.html (accessed on 29 September 2017).
  3. Montenbruck, O.; Steigenberger, P.; Hauschild, A. Broadcast versus precise ephemerides: A multi-GNSS perspective. GPS Solut. 2015, 19, 321–333. [Google Scholar] [CrossRef]
  4. Dalla Torre, A.; Caporali, A. An analysis of intersystem biases for multi-GNSS positioning. GPS Solut. 2015, 19, 297–307. [Google Scholar] [CrossRef]
  5. Caporali, A.; Nicolini, L. Interoperability of the GNSS’s for Positioning and Timing. In New Advanced GNSS and 3D Spatial Techniques; Lecture Notes in Geoinformation and Cartography; Cefalo, R., Zielinski, J., Barbarella, M., Eds.; Springer: Cham, Switzerland, 2017; pp. 73–85. ISBN 978-3-319-56218-6. [Google Scholar]
  6. Prange, L.; Orliac, E.; Dach, R.; Arnold, D.; Beutler, G.; Schaer, S.; Jäggi, A. CODE’s five-system orbit and clock solution—The challenges of multi-GNSS data analysis. J. Geod. 2017, 91, 345–360. [Google Scholar] [CrossRef]
  7. Revnivykh, S. GLONASS ground control segment: Orbit, clock, time scale and geodesy definition. In Proceedings of the 25th International Technical Meeting of the Satellite Division of the Institute of Navigation (ION GNSS 2012), Nashville, TN, USA, 17–21 September 2012; pp. 3931–3949. [Google Scholar]
  8. Kosenko, V. Global Navigation Satellite System (GLONASS): Status and Development. In United Nations/Russian Federation Workshop on the Applications of Global Navigation Satellite Systems; Russian Federation: Krasnoyarsk, Russia, 2015. [Google Scholar]
  9. Teunissen, P.J.G.; Montenbruck, O. Springer Handbook of Global Navigation Satellite Systems, 1st ed.; Springer International Publishing: Cham, Switzerland, 2017; ISBN 978-3-319-42926-7. [Google Scholar]
  10. Dach, R.; Lutz, S.; Walser, P.; Fridez, P. Bernese GNSS Software Version 5.2. User Manual; University of Bern, Bern Open Publishing: Bern, Switzerland, 2015; ISBN 978-3-906813-05-9. [Google Scholar]
  11. EU. European GNSS (Galileo) Open Service Signal in Space Interface Control Document. Available online: https://www.gsc-europa.eu/system/files/galileo_documents/Galileo-OS-SIS-ICD.pdf (accessed on 4 January 2018).
  12. Steigenberger, P.; Montenbruck, O. Galileo status: Orbits, clocks, and positioning. GPS Solut. 2017, 21, 319–331. [Google Scholar] [CrossRef]
  13. International GNSS Service (IGS) RINEX Working Group and Radio Technical Commission for Maritime Services Special Committee 104 (RTCM-SC104). RINEX The Receiver Independent Exchange Format; Version 3.03; Werner Gurtner, Astronomical Institute of the University of Bern, Switzerland and Lou Estey, UNAVCO: Boulder, CO, USA, 2015. [Google Scholar]
  14. Nischan, T. GFZRNX–RINEX GNSS Data Conversion and Manipulation Toolbox (Version 1.05). Available online: http://dataservices.gfz-potsdam.de/panmetaworks/showshort.php?id=escidoc:1577894 (accessed on 4 January 2018).
  15. Russian Institute of Space Device Engineering (RISDE). Global Navigation Satellite System GLONASS—Interface Control Document; Version 5.1; Russian Institute of Space Device Engineering: Moscow, Russia, 2008. [Google Scholar]
  16. Håkansson, M.; Jensen, A.B.O.; Horemuz, M.; Hedling, G. Review of code and phase biases in multi-GNSS positioning. GPS Solut. 2017, 21, 849–860. [Google Scholar] [CrossRef]
  17. Zeng, A.; Yang, Y.; Ming, F.; Jing, Y. BDS-GPS inter-system bias of code observation and its preliminary analysis. GPS Solut. 2017, 21, 1417–1425. [Google Scholar] [CrossRef]
  18. Jiang, N.; Xu, Y.; Xu, T.; Xu, G.; Sun, Z.; Schuh, H. GPS/BDS short-term ISB modelling and prediction. GPS Solut. 2017, 21, 163–175. [Google Scholar] [CrossRef]
  19. Odijk, D.; Teunissen, P.J.G. Characterization of between-receiver GPS-Galileo inter-system biases and their effect on mixed ambiguity resolution. GPS Solut. 2013, 17, 521–533. [Google Scholar] [CrossRef]
  20. Gioia, C.; Borio, D. A statistical characterization of the Galileo-to-GPS inter-system bias. J. Geod. 2016, 90, 1279–1291. [Google Scholar] [CrossRef]
  21. Chen, J.; Xiao, P.; Zhang, Y.; Wu, B. GPS/GLONASS System Bias Estimation and Application in GPS/GLONASS Combined Positioning. In China Satellite Navigation Conference (CSNC) 2013 Proceedings. Lecture Notes in Electrical Engineering; Sun, J., Jiao, W., Wu, H., Shi, C., Eds.; Springer: Berlin/Heidelberg, Germany, 2013; pp. 323–333. ISBN 978-3-642-37403-6. [Google Scholar]
Figure 1. Map view of monitored sites.
Figure 1. Map view of monitored sites.
Remotesensing 10 00080 g001
Figure 2. RSW reference system: radial (R), along-track (S) and cross-track (W).
Figure 2. RSW reference system: radial (R), along-track (S) and cross-track (W).
Remotesensing 10 00080 g002
Figure 3. Representation of the offsets between the three GPS blocks (IIR-A, IIR-B/M, IIF) broadcast and precise reference system of CODE SP3.
Figure 3. Representation of the offsets between the three GPS blocks (IIR-A, IIR-B/M, IIF) broadcast and precise reference system of CODE SP3.
Remotesensing 10 00080 g003
Figure 4. Representation of the offsets between the two GLONASS blocks (M, K) broadcast and precise reference system of CODE SP3.
Figure 4. Representation of the offsets between the two GLONASS blocks (M, K) broadcast and precise reference system of CODE SP3.
Remotesensing 10 00080 g004
Figure 5. Representation of the offsets between Galileo (IOV, FOC) broadcast and precise reference system of CODE SP3.
Figure 5. Representation of the offsets between Galileo (IOV, FOC) broadcast and precise reference system of CODE SP3.
Remotesensing 10 00080 g005
Figure 6. Representation of the offsets between BeiDou broadcast (IGSO, MEO) and precise reference system of CODE SP3.
Figure 6. Representation of the offsets between BeiDou broadcast (IGSO, MEO) and precise reference system of CODE SP3.
Remotesensing 10 00080 g006
Figure 7. Availability of Galileo I/NAV-E1-B broadcast ephemeris on day 1 August 2017.
Figure 7. Availability of Galileo I/NAV-E1-B broadcast ephemeris on day 1 August 2017.
Remotesensing 10 00080 g007
Figure 8. Time series since 1 January 2014 of offsets of the GLONASS (a), Galileo (b), BeiDou (c) and QZSS (d) time scales relative to GPS.
Figure 8. Time series since 1 January 2014 of offsets of the GLONASS (a), Galileo (b), BeiDou (c) and QZSS (d) time scales relative to GPS.
Remotesensing 10 00080 g008
Figure 9. Time series since 1 January 2014 of offsets of the GLONASS (a), Galileo (b) and BeiDou (c) time scales of Septentrio stations relative to GPS.
Figure 9. Time series since 1 January 2014 of offsets of the GLONASS (a), Galileo (b) and BeiDou (c) time scales of Septentrio stations relative to GPS.
Remotesensing 10 00080 g009
Figure 10. Time series since 1 January 2014 of offsets of GLGP (a), GPGA (b), BDGP (c) and QZGP (d) differentiated relative to Septentrio.
Figure 10. Time series since 1 January 2014 of offsets of GLGP (a), GPGA (b), BDGP (c) and QZGP (d) differentiated relative to Septentrio.
Remotesensing 10 00080 g010aRemotesensing 10 00080 g010b
Figure 11. Time offsets of Septentrio station. (a) Time offsets of GLONASS, Galileo, BeiDou and NAVIC (purple) relative to GPS; (b) GLGP, GPGA and BDGP relative to the other Septentrio stations.
Figure 11. Time offsets of Septentrio station. (a) Time offsets of GLONASS, Galileo, BeiDou and NAVIC (purple) relative to GPS; (b) GLGP, GPGA and BDGP relative to the other Septentrio stations.
Remotesensing 10 00080 g011
Figure 12. Time series since 25 September 2016 of offset of the GAGAN time scale relative to GPS.
Figure 12. Time series since 25 September 2016 of offset of the GAGAN time scale relative to GPS.
Remotesensing 10 00080 g012
Table 1. List of stations included in the analysis.
Table 1. List of stations included in the analysis.
IDCityCountryDomesReceiverAntennaStart Date
BBYSBanka BystricaSlovak Republic11514M001Trimble NETR9TRM59800.001 January 2014
BOGOBorowa GoraPoland12207M002Topcon EUROCARDASH700936C_M21 June 2015
BRSTBrestFrance10004M004Trimble NETR9TRM57971.001 January 2014
BRUXBrusselsBelgium13101M010Septentrio POLARX4TRJAVRINGANT_DM1 January 2014
CAENCaenFrance19994M001Leica GR25TRM57971.001 January 2014
CEBRCebrerosSpain13408M001Septentrio POLARX4SEPCHOKE_MC1 January 2014
COMOComoItaly12761M001Topcon E_GGDTPSCR3_GGD21 June 2015
COMOComoItaly12761M001Topcon NET-G5TPSCR3_GGD19 October 2016
COMOComoItaly12761M001Topcon NET-G5TPSCR.G37 February 2017
DLF1DelftThe Netherlands13502M009Trimble NETR9LEIAR25.R31 January 2014
DYNGDyonisosGreece12602M006Trimble NETR9TRM59800.002 March 2015
GANPGanovceSlovak Republic11515M001Trimble NETR9TRM55971.001 January 2014
GANPGanovceSlovak Republic11515M001Trimble NETR9TRM59800.006 February 2017
GOP7OndrejovSlovak Republic11502M006Javad TRE_G3TH DELTALEIAR25.R41 January 2014
GOP7OndrejovSlovak Republic11502M006Trimble NETR9LEIAR25.R41 January 2014
HOFNHoefnIceland10204M002Leica GR25LEIAR25.R41 January 2014
IGMIFirenzeItaly12701M003Topcon ODYSSEY_ETPSCR.G321 June 2015
KIRUKirunaSweden10403M002Septentrio POLARX4SEPCHOKE_MC1 January 2014
M0SERomaItaly12772M001Leica GR25LEIAR25.R41 January 2014
MAS1MaspalomasSpain31303M002Septentrio POLARX4LEIAR25.R425 October 2015
MLVLMarne-la-ValleeFrance10092M001Leica GR25TRM57971.001 January 2014
NYA2Ny AlesundNorway10317M008Javad TRE_G3TH DELTAJAV_RINGANT_G3T25 October 2015
OBE4OberpfaffenhofenGermany14208M007Javad TRE_G3TH DELTAJAV_RINGANT_G3T25 October 2015
PADOPadovaItaly12750S001Leica GR10LEIAR25.R41 January 2014
PEN2PencHungary11206M007Leica GRX1200 + GNSSLEIAR25.R42 March 2015
POTSPotsdamGermany14106M003Javad TRE_G3TH DELTAJAV_RINGANT_G3T2 March 2015
REDUReduBelgium13102M001Septentrio POLARX4SEPCHOKE_MC2 March 2015
REYKReykjavikIceland10202M001Leica GR25LEIAR25.R42 March 2015
SULPLvivUkraine12366M001Topcon NET-G3ATPSCR.G521 June 2015
TLSEToulouseFrance10003M009Trimble NETR9TRM59800.002 March 2015
VILLVillafrancaSpain13406M001Septentrio POLARX4SEPCHOKE_MC25 October 2015
WROCWroclawPoland12217M001Leica GR25LEIAR25.R42 March 2015
WTZ3Bad KoetztingGermany14201M015Javad TRE_G3TH DELTALEIAR25.R325 October 2015
WTZZBad KoetztingGermany14201M014Javad TRE_G3TH DELTALEIAR25.R31 January 2014
ZIMJZimmerwaldSwitzerland14001M006Javad TRE_G3TH DELTAJAVRINGANT_DM1 January 2014
Table 2. GPS mean values and standard deviations of coordinates and clock differences.
Table 2. GPS mean values and standard deviations of coordinates and clock differences.
SatelliteRadial (m)Along-Track (m)Cross-Track (m)Clock (ns)BlockClock 1
G010.00 ± 0.12−0.09 ± 0.440.30 ± 0.27−0.9 ± 0.8IIFRb
G020.05 ± 0.13−0.17 ± 0.740.08 ± 0.501.6 ± 0.8IIR-BRb
G030.00 ± 0.15−0.08 ± 0.620.27 ± 0.35−2.4 ± 0.8IIFRb
G050.00 ± 0.100.02 ± 0.660.19 ± 0.251.8 ± 0.6IIR-MRb
G060.01 ± 0.15−0.06 ± 0.790.28 ± 0.34−0.3 ± 0.5IIFRb
G07−0.02 ± 0.11−0.03 ± 0.620.00 ± 0.380.5 ± 1.7IIR-MRb
G08−0.02 ± 0.290.00 ± 0.95−0.03 ± 0.29−0.2 ± 3.6IIFCs
G090.01 ± 0.270.04 ± 0.420.30 ± 0.270.0 ± 0.8IIFRb
G10−0.05 ± 0.120.25 ± 0.670.28 ± 0.36−1.0 ± 0.6IIFRb
G110.04 ± 0.140.36 ± 0.430.00 ± 0.24−3.1 ± 1.3IIR-ARb
G120.03 ± 0.100.32 ± 0.93−0.07 ± 0.280.7 ± 0.8IIR-MRb
G13−0.02 ± 0.13−0.11 ± 0.570.04 ± 0.47−3.4 ± 0.8IIR-ARb
G14−0.04 ± 0.130.80 ± 0.630.04 ± 0.52−2.3 ± 0.5IIR-ARb
G15−0.07 ± 0.080.72 ± 1.060.11 ± 0.190.7 ± 0.7IIR-MRb
G16−0.08 ± 0.08−0.18 ± 0.50−0.04 ± 0.42−1.8 ± 0.6IIR-ARb
G170.03 ± 0.160.74 ± 1.12−0.05 ± 0.310.4 ± 2.0IIR-MRb
G180.05 ± 0.10−0.66 ± 0.880.14 ± 0.32−2.1 ± 1.3IIR-ARb
G19−0.02 ± 0.130.50 ± 0.77−0.06 ± 0.541.3 ± 1.0IIR-BRb
G200.00 ± 0.09−0.46 ± 0.770.13 ± 0.27−2.0 ± 0.9IIR-ARb
G21−0.02 ± 0.120.02 ± 0.820.03 ± 0.38−1.8 ± 0.8IIR-ARb
G22−0.11 ± 0.100.30 ± 0.460.20 ± 0.461.8 ± 0.8IIR-BRb
G230.01 ± 0.08−0.57 ± 0.680.13 ± 0.440.5 ± 0.6IIR-BRb
G24−0.01 ± 0.420.56 ± 1.11−0.07 ± 0.31−2.6 ± 2.6IIFCs
G250.00 ± 0.170.22 ± 0.62−0.17 ± 0.37−1.3 ± 0.8IIFRb
G260.03 ± 0.21−0.47 ± 0.64−0.13 ± 0.26−0.5 ± 0.5IIFRb
G27−0.02 ± 0.300.08 ± 0.68−0.02 ± 0.24−0.9 ± 0.7IIFRb
G280.08 ± 0.13−0.12 ± 0.61−0.02 ± 0.18−2.6 ± 3.9IIR-ARb
G290.06 ± 0.12−0.92 ± 0.74−0.07 ± 0.452.0 ± 1.0IIR-MRb
G300.03 ± 0.22−0.23 ± 0.53−0.09 ± 0.25−0.8 ± 0.8IIFRb
G310.04 ± 0.13−0.25 ± 0.810.00 ± 0.290.8 ± 0.8IIR-MRb
G320.01 ± 0.19−0.21 ± 0.700.29 ± 0.31−0.6 ± 0.6IIFRb
1 Rb: Rubidium, Cs: Cesium.
Table 3. GLONASS mean values and standard deviations of coordinates and clock differences.
Table 3. GLONASS mean values and standard deviations of coordinates and clock differences.
SatelliteRadial (m)Along-Track (m)Cross-Track (m)Clock (ns)BlockClock 1
R010.10 ± 0.41−0.42 ± 0.70−0.19 ± 0.62−2.4 ± 3.0MCs
R020.07 ± 0.44−0.03 ± 1.13−0.14 ± 0.67−6.1 ± 5.8MCs
R030.08 ± 0.400.78 ± 0.87−0.12 ± 0.9720.1 ± 6.0MCs
R040.08 ± 0.41−0.72 ± 1.10−0.16 ± 0.4522.2 ± 6.3MCs
R050.08 ± 0.391.22 ± 1.58−0.18 ± 0.90−1.5 ± 5.8MCs
R060.16 ± 0.470.79 ± 1.72−0.17 ± 0.540.1 ± 5.9MCs
R070.14 ± 0.380.46 ± 1.01−0.12 ± 0.6214.6 ± 4.3MCs
R080.12 ± 0.41−0.41 ± 1.15−0.15 ± 0.9724.3 ± 4.4MCs
R090.00 ± 0.580.00 ± 0.790.00 ± 0.3610.3 ± 3.9KCs
R10−0.29 ± 0.49−0.21 ± 0.730.18 ± 1.06−13.9 ± 7.2MCs
R110.05 ± 0.421.91 ± 0.890.18 ± 0.656.4 ± 5.3MCs
R130.08 ± 0.46−0.31 ± 2.350.15 ± 0.73−3.1 ± 4.7MCs
R14−0.30 ± 0.46−0.23 ± 2.940.14 ± 0.93−20.2 ± 9.7MCs
R15−0.30 ± 0.49−1.13 ± 2.320.09 ± 0.990.6 ± 9.9MCs
R16−0.01 ± 0.441.31 ± 1.120.09 ± 0.693.7 ± 5.2MCs
R170.03 ± 0.622.31 ± 0.88−0.13 ± 0.7411.8 ± 5.0MCs
R18−0.01 ± 0.480.31 ± 0.87−0.15 ± 0.76−4.6 ± 4.3MCs
R190.06 ± 0.661.06 ± 2.00−0.09 ± 0.786.9 ± 5.9MCs
R20−0.35 ± 0.640.01 ± 2.19−0.11 ± 0.715.1 ± 4.8MCs
R210.02 ± 0.530.35 ± 0.82−0.08 ± 0.6613.1 ± 4.7MCs
R220.03 ± 0.46−1.17 ± 1.87−0.07 ± 0.720.0 ± 7.5MCs
R23−0.05 ± 0.521.78 ± 0.97−0.08 ± 0.672.2 ± 4.7MCs
R240.18 ± 0.57−0.96 ± 1.02−0.09 ± 0.796.2 ± 3.5MCs
1 Cs: Cesium.
Table 4. BeiDou mean values and standard deviations of coordinates and clock differences.
Table 4. BeiDou mean values and standard deviations of coordinates and clock differences.
SatelliteRadial (m)Along-Track (m)Cross-Track (m)Clock (ns)OrbitClock 3
C06−1.15 ± 0.310.14 ± 0.51−0.01 ± 0.59104.8 ± 2.2IGSO 1Rb
C070.99 ± 0.35−0.03 ± 0.60−0.21 ± 0.44121.5 ± 2.0IGSO 1Rb
C080.31 ± 0.480.51 ± 0.390.09 ± 0.86113.6 ± 2.4IGSO 1Rb
C09−0.28 ± 0.30−0.32 ± 0.43−0.13 ± 0.7794.8 ± 2.0IGSO 1Rb
C10−0.14 ± 0.320.39 ± 0.70−0.07 ± 0.4695.5 ± 2.3IGSO 1Rb
C11−0.39 ± 0.55−0.20 ± 1.260.04 ± 0.6488.4 ± 27.2MEO 2Rb
C12−0.03 ± 0.490.02 ± 1.330.02 ± 0.5493.1 ± 2.5MEO 2Rb
C130.26 ± 0.63−0.22 ± 0.61−0.03 ± 0.8155.8 ± 1.6IGSO 1Rb
C140.43 ± 0.45−0.53 ± 1.480.50 ± 0.5999.9 ± 3.1MEO 2Rb
1 Inclined Geosynchronous Orbit; 2 Medium Earth Orbit; 3 Rb: Rubidium.
Table 5. Galileo mean values and standard deviations of coordinates and clock differences.
Table 5. Galileo mean values and standard deviations of coordinates and clock differences.
SatelliteRadial (m)Along-Track (m)Cross-Track (m)Clock (ns)GenerationClock 3
E010.01 ± 0.14−0.13 ± 0.28−0.04 ± 0.162.2 ± 1.3FOC 2PHM
E02−0.01 ± 0.15−0.06 ± 0.290.04 ± 0.131.3 ± 1.1FOC 2PHM
E030.01 ± 0.11−0.10 ± 0.250.00 ± 0.172.1 ± 1.2FOC 2PHM
E04−0.01 ± 0.11−0.05 ± 0.360.01 ± 0.161.6 ± 1.2FOC 2PHM
E05−0.03 ± 0.120.00 ± 0.250.01 ± 0.162.1 ± 1.1FOC 2PHM
E070.01 ± 0.12−0.11 ± 0.280.05 ± 0.162.8 ± 1.3FOC 2PHM
E08−0.01 ± 0.110.04 ± 0.240.04 ± 0.141.0 ± 1.2FOC 2PHM
E090.00 ± 0.130.05 ± 0.300.03 ± 0.171.7 ± 1.2FOC 2PHM
E110.01 ± 0.150.00 ± 0.35−0.05 ± 0.180.7 ± 1.2IOV 1PHM
E120.00 ± 0.13−0.04 ± 0.31−0.04 ± 0.171.6 ± 1.4IOV 1PHM
E140.04 ± 0.480.04 ± 2.10−0.14 ± 0.846.7 ± 1.3FOC 2PHM
E180.04 ± 0.37−0.04 ± 2.05−0.02 ± 0.504.1 ± 1.2FOC 2PHM
E19−0.01 ± 0.18−0.08 ± 0.44−0.01 ± 0.231.1 ± 1.5IOV 1PHM
E22−0.01 ± 0.160.03 ± 0.25−0.05 ± 0.131.4 ± 1.5FOC 2PHM
E24−0.02 ± 0.150.01 ± 0.25−0.05 ± 0.177.8 ± 1.1FOC 2PHM
E260.01 ± 0.16−0.09 ± 0.29−0.06 ± 0.152.5 ± 1.3FOC 2PHM
E300.02 ± 0.15−0.02 ± 0.220.02 ± 0.162.0 ± 1.2FOC 2PHM
1 In-Orbit Validation; 2 Full Operational Capability; 3 PHM: Passive Hydrogen Maser.
Table 6. Frequencies and observation codes used.
Table 6. Frequencies and observation codes used.
ConstellationCarrier/Frequency [MHz]Pseudorange Codes
GPSL1 (1575.42)L2 (1227.60)C1CC2W
GLONASSG1 (1602 + k × 9/16)G2 (1246 + k × 7/16)C1CC2P
GalileoE1 (1575.42)E5b 1 (1207.14)C1CC7I/C7Q/C7X
BeiDouB1 (1561.098)B2 (1207.14)C1IC7I
QZSSL1 (1575.42)L2 (1227.60)C1CC2S/C2L/C2X
NAVICL5 (1176.45) C5A
SBASL1 (1575.42)L5 (1176.45)C1CC5I
1 I/NAV.
Table 7. Explanation of symbols and variables used in Equations (2)–(6).
Table 7. Explanation of symbols and variables used in Equations (2)–(6).
SymbolUnitMeaning
cm/sSpeed of light
tsTime of reception in the receiver time scale
t‘sTime of transmission in the specific GNSS time scale: t′ = tp(t)/c
tofsTime of flight
LSsPosition of satellites must be computed at time ttofLS, where LS = full leap seconds for GLONASS; 14 s for BeiDou; 0 s for other GNSS
dTRelsPeriodic part of relativistic correction (which is not considered for GLONASS since it is already included in the polynomial correction [3])
ωerad/sEarth rotation rate appropriate for the GNSS constellation
X, Y, ZmEarth-Centered Earth-Fixed (ECEF) coordinates of satellite
x, y, zmECEF coordinates of receiver
TSCXsTime System Correction of the X 1 GNSS relative to a common time scale
dTRecsReceiver clock offset relative to a common time scale
dtsSatellite Clock offset relative to a specific GNSS time scale
TZDmTropospheric Zenith Delay
El°Elevation
1 G: GPS; R: GLONASS; E: Galileo; C: BeiDou; J: QZSS; I: NAVIC (formerly IRNSS); N: GAGAN.
Table 8. Definition of Time Offsets.
Table 8. Definition of Time Offsets.
Time OffsetDefinition
GLGP(TSCR + dTRec) − (TSCG + dTRec)
GPGA(TSCG + dTRec) − (TSCE + dTRec)
BDGP(TSCC + dTRec) − (TSCG + dTRec)
QZGP(TSCJ + dTRec) − (TSCG + dTRec)
NAGP(TSCI + dTRec) − (TSCG + dTRec)
GNGP(TSCN + dTRec) − (TSCG + dTRec)
Table 9. Calibration of station’s time offsets relative to Septentrio.
Table 9. Calibration of station’s time offsets relative to Septentrio.
STATIONRECEIVERCALIBRATION [ns]
IDFROMTORECEIVERTYPEFIRMWAREdGLGPdGPGAdBDGPdQZGP
BBYSa1 January 201430 May 2014TRIMBLENETR94.81/4.7116.5 ± 2.7 44.4 ± 2.8
BBYSb30 May 2014NOW 1TRIMBLENETR94.85/4.7110.6 ± 0.9−12.4 ± 0.840.1 ± 1.7
BOGO21 June 2015NOW 1TOPCONEUROCARD2.6.1 10 January 2008−118.1 ± 1.1
BRST1 January 201426 March 2014TRIMBLENETR94.8111.1 ± 1.2−12.0 ± 1.138.9 ± 2.4
BRST26 March 2014NOW 1TRIMBLENETR94.8511.1 ± 1.2−12.0 ± 1.138.9 ± 2.4
BRUX1 January 201417 March 2014SEPTENTRIOPOLARX4TR2.3.42.8 ± 2.70.6 ± 0.63.4 ± 3.3
BRUX17 March 20147 September 2015SEPTENTRIOPOLARX4TR2.5.22.8 ± 2.70.6 ± 0.63.4 ± 3.3
BRUX7 September 201524 October 2016SEPTENTRIOPOLARX4TR2.9.02.8 ± 2.70.6 ± 0.63.4 ± 3.3
BRUX24 October 20163 January 2017SEPTENTRIOPOLARX4TR2.9.52.8 ± 2.70.6 ± 0.63.4 ± 3.3
BRUX3 January 2017NOW 1SEPTENTRIOPOLARX4TR2.9.62.8 ± 2.70.6 ± 0.63.4 ± 3.3
CAENa1 January 201420 February 2014LEICAGR253.0141.5 ± 3.2−42.1 ± 1.168.0 ± 3.3
CAENa20 February 201419 September 2014LEICAGR253.0341.5 ± 3.2−42.1 ± 1.168.0 ± 3.3
CAENa19 September 20146 November 2014LEICAGR253.1041.5 ± 3.2−42.1 ± 1.168.0 ± 3.3
CAENa6 November 20145 August 2016LEICAGR253.1141.5 ± 3.2−42.1 ± 1.168.0 ± 3.3
CAENb12 August 20169 November 2016LEICAGR253.11−23.9 ± 0.5−65.3 ± 1.090.3 ± 2.7
CAENb9 November 2016NOW 1LEICAGR254.02−23.9 ± 0.5−65.3 ± 1.090.3 ± 2.7
CEBR1 January 201410 December 2014SEPTENTRIOPOLARX42.5.1p1−0.3 ± 2.80.0 ± 0.9−2.9 ± 3.2
CEBR10 December 201427 August 2015SEPTENTRIOPOLARX42.5.2-esa3−0.3 ± 2.80.0 ± 0.9−2.9 ± 3.2
CEBR27 August 201521 October 2016SEPTENTRIOPOLARX42.9.0−0.3 ± 2.80.0 ± 0.9−2.9 ± 3.2
CEBR21 October 2016NOW 1SEPTENTRIOPOLARX42.9.5-extref1−0.3 ± 2.80.0 ± 0.9−2.9 ± 3.2
COMOa21 June 201519 October 2016TOPCONE_GGD3.4 12 Decembaer 2009 p2−76.2 ± 2.0
COMOb19 October 20167 February 2017TOPCONNET-G55.0 20 November 2015 p2−60.2 ± 0.7
COMOc7 February 2017NOW 1TOPCONNET-G55.1 7 September 2016−56.0 ± 0.8
DLF1a1 January 201417 June 2015TRIMBLENETR94.8123.6 ± 1.8 44.8 ± 1.4
DLF1b17 June 201513 July 2015TRIMBLENETR95.0117.4 ± 0.9−16.2 ± 1.042.2 ± 1.4−102.9 ± 149.4
DLF1b13 July 201520 July 2016TRIMBLENETR95.0317.4 ± 0.9−16.2 ± 1.042.2 ± 1.4−102.9 ± 149.4
DLF1b20 July 201621 December 2016TRIMBLENETR95.1417.4 ± 0.9−16.2 ± 1.042.2 ± 1.4−102.9 ± 149.4
DLF1b21 December 201628 May 2017TRIMBLENETR95.1517.4 ± 0.9−16.2 ± 1.042.2 ± 1.4−102.9 ± 149.4
DLF1b28 May 2017NOW 1TRIMBLENETR95.2217.4 ± 0.9−16.2 ± 1.042.2 ± 1.4−102.9 ± 149.4
DYNGa2 March 201519 June 2015TRIMBLENETR94.8512.3 ± 1.4−13.0 ± 1.338.0 ± 2.1
DYNGa19 June 20155 July 2016TRIMBLENETR95.0112.3 ± 1.4−13.0 ± 1.338.0 ± 2.1
DYNGb05 July 201614 December 2016TRIMBLENETR95.1415.4 ± 1.7−13.6 ± 1.144.1 ± 1.4
DYNGb14 December 2016NOW 1TRIMBLENETR95.1515.4 ± 1.7−13.6 ± 1.144.1 ± 1.4
GANPa1 January 201430 May 2014TRIMBLENETR94.81/4.2913.0 ± 2.6 40.5 ± 1.5
GANPb30 May 201410 February 2015TRIMBLENETR94.85/4.2910.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPb10 February 201518 November 2015TRIMBLENETR94.93/4.9310.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPb18 November 201514 October 2016TRIMBLENETR95.10/5.0210.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPb14 October 20162 January 2017TRIMBLENETR95.14/5.1410.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPb2 January 201711 January 2017TRIMBLENETR95.15/5.1510.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPb11 January 20176 February 2017TRIMBLENETR95.20/5.2010.3 ± 3.6−14.7 ± 2.138.5 ± 3.4−21.8 ± 53.1
GANPc6 February 201718 April 2017TRIMBLENETR95.2017.4 ± 0.9 −11.0 ± 0.944.9 ± 0.8−30.4± 30.6
GANPc18 April 2017NOW 1TRIMBLENETR95.2217.4 ± 0.9 −11.0 ± 0.944.9 ± 0.8−30.4 ± 30.6
GOP7a1 January 201421 August 2015JAVADTRE_G3TH DELTA3.5.1−19.0 ± 1.3
GOP7b21 August 2015NOW 1TRIMBLENETR95.0110.6 ± 3.0−4.9 ± 4.635.1 ± 3.1
HOFN1 January 201418 February 2014LEICAGR253.01/6.21243.8 ± 3.5−44.2 ± 0.8
HOFN18 February 20148 September 2014LEICAGR253.03/6.21443.8 ± 3.5−44.2 ± 0.8
HOFN8 September 201410 September 2014LEICAGR253.10/6.40343.8 ± 3.5−44.2 ± 0.8
HOFN10 September 20143 November 2014LEICAGR253.10.1633/6.40343.8 ± 3.5−44.2 ± 0.8
HOFN3 November 2014NOW 1LEICAGR253.11.1639/6.40343.8 ± 3.5−44.2 ± 0.8
IGMI21 June 201517 June 2016TOPCONODYSSEY_E3.3 10 July 2008 P4−69.3 ± 1.5
IGMI21 July 2016NOW 1TOPCONODYSSEY_E3.4 12 December 2009 P2−69.3 ± 1.5
KIRU1 January 201410 December 2014SEPTENTRIOPOLARX42.5.1p1−3.4 ± 2.1−0.4 ± 1.22.1 ± 3.80.0 ± 0.0
KIRU10 December 201427 August 2015SEPTENTRIOPOLARX42.5.2-esa3−3.4 ± 2.1−0.4 ± 1.22.1 ± 3.80.0 ± 0.0
KIRU27 August 201521 October 2016SEPTENTRIOPOLARX42.9.0−3.4 ± 2.1−0.4 ± 1.22.1 ± 3.80.0 ± 0.0
KIRU21 October 2016NOW 1SEPTENTRIOPOLARX42.9.5-extref1−3.4 ± 2.1−0.4 ± 1.22.1 ± 3.80.0 ± 0.0
M0SEa1 January 201424 February 2014LEICAGR253.00/6.11341.1 ± 4.1
M0SEa24 February 201417 July 2014LEICAGR253.03/6.21441.1 ± 4.1
M0SEa17 July 201411 September 2014LEICAGR253.10/6.40141.1 ± 4.1
M0SEa11 September 201426 November 2014LEICAGR253.10/6.40341.1 ± 4.1
M0SEa26 November 20148 May 2015LEICAGR253.11/6.40341.1 ± 4.1
M0SEa8 May 20152 February 2016LEICAGR253.20/6.40341.1 ± 4.1
M0SEb2 February 201603 April 2017LEICAGR253.22/6.521−24.9 ± 0.6−67.4 ± 0.8
M0SEb3 April 2017NOW 1LEICAGR254.11/6.523−24.9 ± 0.6−67.4 ± 0.8
MAS125 October 201518 October 2016SEPTENTRIOPOLARX42.9.0−1.2 ± 0.80.2 ± 1.2−4.3 ± 2.3
MAS118 October 2016NOW 1SEPTENTRIOPOLARX42.9.5-extref1−1.2 ± 0.80.2 ± 1.2−4.3 ± 2.3
MLVLa1 January 201429 January 2014LEICAGR253.0137.3 ± 2.8−39.8 ± 1.259.4 ± 2.3
MLVLa29 January 201429 August 2014LEICAGR253.0337.3 ± 2.8−39.8 ± 1.259.4 ± 2.3
MLVLa29 August 201420 October 2014LEICAGR253.1037.3 ± 2.8−39.8 ± 1.259.4 ± 2.3
MLVLa20 October 20146 August 2016LEICAGR253.1137.3 ± 2.8−39.8 ± 1.259.4 ± 2.3
MLVLb11 August 20169 November 2016LEICAGR253.11−28.9 ± 0.7−63.0 ± 1.081.9 ± 2.7
MLVLb9 November 2016NOW 1LEICAGR254.02−28.9 ± 0.7−63.0 ± 1.081.9 ± 2.7
NYA225 October 201525 October 2016JAVADTRE_G3TH DELTA3.5.10−29.3 ± 0.818.2 ± 1.6 0.6 ± 8.0
NYA225 October 2016NOW 1JAVADTRE_G3TH DELTA3.6.7−29.3 ± 0.818.2 ± 1.6 0.6 ± 8.0
OBE425 October 201517 October 2016JAVADTRE_G3TH DELTA3.5.10−31.1 ± 0.722.3 ± 1.0
OBE417 October 2016NOW 1JAVADTRE_G3TH DELTA3.6.7−31.1 ± 0.722.3 ± 1.0
PADOa1 January 201425 August 2014LEICAGR103.00/6.11340.7 ± 4.4−41.4 ± 1.353.2 ± 2.2
PADOa25 August 201415 March 2016LEICAGR103.10.1633/6.40340.7 ± 4.4−41.4 ± 1.353.2 ± 2.2
PADOb15 March 201615 June 2016LEICAGR103.22/6.521−25.3 ± 1.4−64.7 ± 0.377.6 ± 1.8
PADOb15 June 201624 August 2016LEICAGR104.00/6.521−25.3 ± 1.4−64.7 ± 0.377.6 ± 1.8
PADOb24 August 2016NOW 1LEICAGR104.00/6.522−25.3 ± 1.4−64.7 ± 0.377.6 ± 1.8
PEN22 March 2015NOW 1LEICAGRX1200 + GNSS8.51/6.11041.6 ± 2.754.9 ± 3.5
POTS2 March 201515 September 2015JAVADTRE_G3TH DELTA3.4.7−21.8 ± 0.816.8 ± 1.1
POTS15 September 201525 October 2016JAVADTRE_G3TH DELTA3.5.10−21.8 ± 0.816.8 ± 1.1
POTS25 October 2016NOW 1JAVADTRE_G3TH DELTA3.6.7−21.8 ± 0.816.8 ± 1.1
REDU2 March 201527 August 2015SEPTENTRIOPOLARX42.5.2-esa30.3 ± 0.40.0 ± 0.9−0.4 ± 1.2
REDU27 August 201518 October 2016SEPTENTRIOPOLARX42.9.00.3 ± 0.40.0 ± 0.9−0.4 ± 1.2
REDU18 October 2016NOW 1SEPTENTRIOPOLARX42.9.5-extref10.3 ± 0.40.0 ± 0.9−0.4 ± 1.2
REYKa2 March 20158 August 2016LEICAGR253.11.1639/6.40342.8 ± 1.2−43.9 ± 0.862.0 ± 2.4
REYKb8 August 2016NOW 1LEICAGR253.11.1639/6.522−24.4 ± 0.7−67.0 ± 0.983.8 ± 3.0
SULP21 June 201511 November 2016TOPCONNET-G3A4.1 31 May 2013−76.5 ± 1.3
SULP16 November 2016NOW 1TOPCONNET-G3A4.7 23 October 2015−76.5 ± 1.3
TLSEa2 March 201519 June 2015TRIMBLENETR94.8515.9 ± 0.9−13.6 ± 1.643.1 ± 2.1
TLSEa19 June 201511 March 2016TRIMBLENETR95.0115.9 ± 0.9−13.6 ± 1.643.1 ± 2.1
TLSEb11 March 201611 August 2016TRIMBLENETR95.0113.6 ± 0.9−14.7 ± 0.644.8 ± 0.9
TLSEb11 August 201612 December 2016TRIMBLENETR95.1413.6 ± 0.9−14.7 ± 0.644.8 ± 0.9
TLSEb12 December 201623 May 2017TRIMBLENETR95.1513.6 ± 0.9−14.7 ± 0.644.8 ± 0.9
TLSEb23 May 201715 June 2017TRIMBLENETR95.2213.6 ± 0.9−14.7 ± 0.644.8 ± 0.9
TLSEb15 June 2017NOW 1TRIMBLENETR95.2213.6 ± 0.9−14.7 ± 0.644.8 ± 0.9
VILL25 October 201521 October 2016SEPTENTRIOPOLARX42.9.02.1 ± 0.5−0.3 ± 0.8−0.7 ± 1.1
VILL21 October 2016NOW 1SEPTENTRIOPOLARX42.9.5-extref12.1 ± 0.5−0.3 ± 0.8−0.7 ± 1.1
WROCa2 March 20154 September 2015LEICAGR253.11.1639/6.40363.2 ± 1.4 84.7 ± 1.8−12.7 ± 18.3
WROCb4 September 201510 March 2016LEICAGR253.21/6.40319.8 ± 1.3−62.8 ± 0.972.8 ± 2.1−13.5 ± 20.1
WROCb10 March 201614 April 2016LEICAGR253.22/6.52119.8 ± 1.3−62.8 ± 0.972.8 ± 2.1−13.5 ± 20.1
WROCc15 April 201623 May 2016LEICAGR253.22/6.52112.1 ± 10.1−62.4 ± 2.072.0 ± 9.2−14.3 ± 27.2
WROCc23 May 2016NOW 1LEICAGR253.22/6.52212.1 ± 10.1−62.4 ± 2.072.0 ± 9.2−14.3 ± 27.2
WTZ3a25 October 201523 April 2016JAVADTRE_G3TH DELTA3.6.1b1-68-7da1−16.2 ± 1.620.4 ± 2.6
WTZ3b28 April 201612 January 2017JAVADTRE_G3TH DELTA3.6.1b1-68-7da1−19.9 ± 0.719.4 ± 5.1
WTZ3b12 January 2017NOW 1JAVADTRE_G3TH DELTA3.6.9−19.9 ± 0.719.4 ± 5.1
WTZZa1 January 201417 April 2014JAVADTRE_G3TH DELTA3.5.3 19 September 2013−14.5 ± 1.7 169.7 ± 9.4
WTZZa17 April 201414 August 2014JAVADTRE_G3TH DELTA3.5.5 3 March 2014−14.5 ± 1.7 169.7 ± 9.4
WTZZa14 August 201427 January 2015JAVADTRE_G3TH DELTA3.6.0 23 June 2014−14.5 ± 1.7 169.7 ± 9.4
WTZZa27 January 201516 June 2015JAVADTRE_G3TH DELTA3.6.1 30 December 2014−14.5 ± 1.7 169.7 ± 9.4
WTZZa16 June 201512 July 2015JAVADTRE_G3TH DELTA3.6.2 8 April 2015−14.5 ± 1.7 169.7 ± 9.4
WTZZb13 July 201520 November 2015JAVADTRE_G3TH DELTA3.6.2 8 April 2015−16.3 ± 0.8−130.2 ± 3.0
WTZZb20 November 201526 November 2015JAVADTRE_G3TH DELTA3.6.3 1 July 2015−16.3 ± 0.8−130.2 ± 3.0
WTZZb26 November 201516 February 2016JAVADTRE_G3TH DELTA3.6.4B1-57-AB7E−16.3 ± 0.8−130.2 ± 3.0
WTZZc16 February 201619 May 2016JAVADTRE_G3TH DELTA3.6.4 12 January 2016−12.2 ± 1.0−133.7 ± 0.8
WTZZd19 May 20161 December 2016JAVADTRE_G3TH DELTA3.6.6 27 April 2016−15.3 ± 0.6−2.6 ± 3.322.2 ± 0.0
WTZZe2 December 201612 January 2017JAVADTRE_G3TH DELTA3.6.6 27 April 2016−12.7 ± 0.8−6.0 ± 1.218.0 ± 1.9
WTZZf12 January 201714 February 2017JAVADTRE_G3TH DELTA3.6.9 28 November 2016−16.2 ± 0.6 −3.1 ± 0.8 17.5 ± 0.0
WTZZg15 February 2017NOW 1JAVADTRE_G3TH DELTA3.6.9 28 November 2016−12.3 ± 0.8 −6.5 ± 1.3 17.4 ± 3.0
ZIMJa1 January 201412 May 2016JAVADTRE_G3TH DELTA3.4.9 18 April 2013−20.6 ± 1.921.9 ± 1.8
ZIMJb12 May 2016NOW 1JAVADTRE_G3TH DELTA3.5.12 12 November 2015−24.8 ± 0.719.3 ± 2.8
1 Calibration table is updated to 10 June 2017.

Share and Cite

MDPI and ACS Style

Nicolini, L.; Caporali, A. Investigation on Reference Frames and Time Systems in Multi-GNSS. Remote Sens. 2018, 10, 80. https://doi.org/10.3390/rs10010080

AMA Style

Nicolini L, Caporali A. Investigation on Reference Frames and Time Systems in Multi-GNSS. Remote Sensing. 2018; 10(1):80. https://doi.org/10.3390/rs10010080

Chicago/Turabian Style

Nicolini, Luca, and Alessandro Caporali. 2018. "Investigation on Reference Frames and Time Systems in Multi-GNSS" Remote Sensing 10, no. 1: 80. https://doi.org/10.3390/rs10010080

APA Style

Nicolini, L., & Caporali, A. (2018). Investigation on Reference Frames and Time Systems in Multi-GNSS. Remote Sensing, 10(1), 80. https://doi.org/10.3390/rs10010080

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop