<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Galileo Open Service Supported by RIGTC/GOP Navigation Performance Monitoring</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jan Douša</string-name>
          <email>jan.dousa@pecny.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pavel Václavovic</string-name>
          <email>pavel.vaclavovic@pecny.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Kala</string-name>
          <email>michael.kala@pecny.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Petr Bezděka</string-name>
          <email>petr.bezdeka@pecny.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lewen Zhao</string-name>
          <email>lewen.zhao@pecny.cz</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Research Institute of Geodesy</institution>
          ,
          <addr-line>Topography and Cartography, Ústecká 98, Zdiby, 25066</addr-line>
          ,
          <country country="CZ">Czech Republic</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Geodetic Observatory Pecný (GOP) of the Research Institute of Geodesy, Topography and Cartography (RIGTC) contributes to the monitoring navigation performance of the Galileo Open Service Signal in Space within the Member States support of the Galileo Reference Centre. GOP contribution consists of the three main tasks: 1) monitoring the quality of multiGNSS data stemming from about 65 reference stations, 2) generating consolidated navigation files and reference GPS and Galileo satellites orbit and clock products with a latency of 6 and 42 hours, and 3) estimating key-parameter indicators for the Galileo OS navigation performance monitoring. The GOP chain of monitoring processes and all mandatory inputs is independent from other contributions in terms of the tools (G-Nut software), reference products rapid precise satellite orbits and clocks), and consolidated broadcast navigation data (BRDC files).</p>
      </abstract>
      <kwd-group>
        <kwd>1 GNSS</kwd>
        <kwd>Galileo</kwd>
        <kwd>satellite orbits and clocks</kwd>
        <kwd>navigation data quality</kwd>
        <kwd>performance monitoring</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>generated on a daily basis in early-rapid and rapid processing mode, i.e. targeting a delivery within 48
hours and 6 hours, respectively. For a maximum independency, in-house developed or extended tools
are mainly exploited for generating reference products (green boxes), monitoring of station data quality
(blue box), estimating station reference coordinates (red box), and monitoring navigation performance
indicators (yellow boxes):
• G-Nut/Anubis tool originally designed for a multi-GNSS data quality control and further
enhanced for estimating site-measured horizontal and vertical positioning indicators using
specific signals and navigation data,
• G-Nut/Aset tool originally designed for the evaluation of satellite orbits and clocks, but
additionally enhanced for merging, filtering and quality control of multi-GNSS navigation
records,
• G-Nut/Geb tool implementing precise coordinate estimates using the Precise Point</p>
      <p>Positioning (PPP) method and precise orbit and clock products,
• G-Nut/Sothis tool for estimating GPS and Galileo precise satellite clock corrections, and
• Bernese GNSS software Version 5.2 driven by an autonomous processing system developed
at GOP for determining precise orbits in the rapid and early-rapid modes.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Consolidated navigation data (BRDC files)</title>
      <p>The GOP consolidated navigation BRDC files [3][1] are generated using the G-Nut/Aset software
and inputs from real-time streams and hourly/daily RINEX files of about 300 global multi-GNSS
stations of the IGS Multi-GNSS Experiment (MGEX) [4], [5] and the GRC-MS networks. The GOP
BRDC product contains navigation data for all the GNSS constellations and regional augmentations.
The RINEX 2 and 3 files are provided repetitively over past three days with a delay of 2-72 hours.</p>
      <p>The GOP consolidation procedure consists of merging, filtering, and data quality control of
navigation records collected from an extensive number of global multi-GNSS stations. In support of
the ultra-fast delivery, it requires neither reference products nor external a priori information. In order
to guarantee a high reliability of the consolidated files, it relays on autonomous methods: a) time-series
analysis for selected parameters (values, differences), b) range check (record pre-filtering), c) statistical
analysis, d) majority vote, e) penalty system, f) identification and correction of issues from specific
receivers.</p>
      <p>The parameter range check is applied for filtering out obviously incorrect navigation records. An
analysis of selected navigation parameter time-series monitors absolute values and their changes in
time. This procedure is completed with a penalty system using adaptable thresholds for identifying and
rejecting outliers. Signal group delays and satellite health status are evaluated statistically along with
autonomously detecting (and eliminating) problematic receiver types. Header data are selected
according to a majority vote. All the methods applied within the concatenation and the quality-control
processes are performed at several levels when selecting a group of navigation files from available
global stations.</p>
      <p>From the four types of navigation messages provided by the Galileo system [6] the two are currently
supported: 2) F/NAV navigation message transmitted on channel E5a-I at a rate of 25 bps and 2) I/NAV
navigation message transmitted on both E1B and E5b-I channels at a rate of 125 bps. Figure 2 and
Figure 3 display total numbers of satellites per individual GNSS (top) and mean numbers of navigation
messages per satellite for each GNSS (bottom) as available in the GOP BRDC files in the years
20172021. The top plot shows new satellites included in the Galileo system and reaching 22 (+2 eccentric)
satellites in February 2018. The bottom plot indicates several periods with a low number of navigation
data (per satellite) in a day. Two from all recognizable events occurred in 2018 (November 7-8) and in
2019 (July 11-17), i.e. during the GRC-MS monitoring period, and these were also reported as outages
in the Notice Advisory to Galileo Users (NAGU) 2018027-031 and 2019025-028, respectively.</p>
      <p>Figure 4 then displays daily percentages of healthy navigation records per day for all individual
satellites (the y-axis) using Galileo F/NAV data. The I/NAV data performs usually in a similar way.
The value 100% and 0% represents healthy and unhealthy satellites, respectively. Some days/satellites
show mixed healthy and unhealthy signal status records. Note that Galileo health status is combined
from the Signal Health Status (SHS), the Data Validity Status (DVS) and the Signal-in-Space Accuracy
(SISA) flags defined in the Galileo OS Service Definition Document [7]. The plot also shows the two
Galileo eccentric satellites (E14 and E18) becoming active on November 30, 2020 (NAGU
2020019020) and eventually providing 24 Galileo active (+2 permanently inactive) satellites. Another event
occurred on December 14, 2020, when the Galileo F/NAV and I/NAV OS SIS was not healthy during
4 and 6 hours (NAGU 2020021), respectively. This was due to the SISA providing the status ‘No
Accuracy Prediction Available’ (NAPA) as visible in dark blue color in Figure 5. The SISA=NAPA
(negative value) is the most frequent reason observed behind short-term unhealthy statuses of Galileo
satellites.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Reference satellite orbit and clock products</title>
      <p>The GOP uses the Bernese GNSS Software V5.2 software [8] for generating precise orbits when
exploiting double-difference observations from a network of more than 120 global stations. The
processing strategy was derived from the GOP ultra-rapid orbits procedure contributing to IGS [9] [10],
however, now including the Galileo besides the GPS system. Two solutions are provided according to
IGS standard delivery timeliness: 1) rapid one with a latency of 2 days, and 2) early-rapid one with a
latency of 6 hours. The latter is a trade-off between the standard IGS ultra-rapid production (6 hour
latency, 4 times/day), supporting mainly (near) real-time data processing, and the rapid production –
the early-rapid is generated once a day (as rapids), but has low latency and includes a 1-day orbit
prediction (as ultra-rapids).</p>
      <p>The orbit product results from combining normal equations of two consecutive days, thus generating
a 2-day arc solution. The orbit model includes 6 Kepler orbital parameters, 9 solar radiation pressure
parameters of the Extended Center for Orbit Determination in Europe Model (ECOM) Version 2 [11],
and 3 stochastic pulses introduced every 12 hours. The orbit determination is initialized exploiting the
GOP BRDC files. The procedure consists of two main iterations while additional ones may be triggered
anytime when handling specific problems due to individual satellites, stations, or baselines.
Satellitespecific orbit accuracy codes provided within the header of the extended Standard Product version 3
format (SP3) are estimated when exploiting a variety of information such as parameter formal errors,
day-to-day orbit comparisons, short-/long-arc combinations, and other internal control procedures.</p>
      <p>Station coordinates and Earth rotation parameters (X-/Y-Pole, X-/Y-Pole rates, length of a day) are
estimated along with satellite orbits on a daily basis too. Other parameters, such as tropospheric delays,
ionospheric corrections, and initial phase ambiguities, are handled within individual processing steps
with an effective time resolution. The models used in the processing are compliant with the International
Earth Rotation and Reference System Service (IERS) 2010 conventions [12]. The absolute antenna type
calibrations for phase center offsets and variations follows the IGS14 model updates.</p>
      <p>The GOP precise satellite clock corrections are estimated on a daily basis using the G-Nut/Sothis
software and introducing the GOP early-rapid (or rapid) satellite orbits and station coordinates. The
processing strategy exploits the ionosphere-free linear combination, however, mixing zero- and
epochdifference observations. Epoch clock variations are estimated by using epoch-differenced carrier-phase
observations. Initial clock biases (ICBs) for each individual satellite are then estimated by using
zerodifferenced code observations [13]. The method is both efficient and robust thanks to the elimination
of initial phase ambiguities and reducing a possible negative impact of cycle slips. Satellite and receiver
clock corrections are estimated epoch-by-epoch in a stochastic process (the Kalman filter) as a sum of
epoch-differenced clock corrections and corresponding initial clock bias. For accurate ICB estimates,
the procedure is supported with differential code biases from DLR MGEX quarterly files [14]. The
clock datum is defined using the common clock satellite datum and the strategy developed at GOP
focusing on real-time applications [15]. The clock corrections are estimated at a 5-min sampling rate
for all healthy GPS and Galileo satellites and provided consistently in SP3 and clock RINEX files.</p>
      <p>The GOP orbits and clocks are regularly compared to the IGS MGEX products, in particular CODE
[16], [17] and CNES solutions [18].The comparison is performed on a daily basis using the G-Nut/Aset
software and a 15-min time resolution. Such an orbit comparison includes the calculation of 7 Helmert
parameters between both solutions in a global scale, and on a daily basis, when removing problematic
satellites, if any. The satellite clock comparison is performed on a double-difference basis, the first
eliminating the clock datum definition within individual products (accessible as a common clock error
in a single epoch) and, the second eliminating initial satellite clock biases corresponding to
satellitespecific code biases at the initial epoch. The clock differences are also reduced by the radial position
error – for this case transformed into time domain by applying the speed of light – for the corresponding
satellite, because the actual clocks also include the compensation of errors in the radial component.
Figure 5 and Figure 7 show results of GOP rapid Galileo satellite orbits and clock corrections,
respectively, compared to the final products of the Center of Orbit Determination in Europe (CODE).
The plots correspond to the year 2020 when the two Galileo elliptic satellites were estimated by GOP
immediately after becoming active on November 30, 2020. A slightly worse performance of the GOP
orbit comparison to CODE (but not so for CNES) revealed for the satellites with a low beta angle (the
angle between the Sun and the corresponding orbital planes), compare Figure 8. The reason is related
to a recent update of the orbit model at CODE considering the effect of thermal radiators [19]. Some
isolated issues at individual days (a vertical view) or satellites (a horizontal view) are usually associated
with the lack of optimal coverage of Galileo data in a global scope within a short latency of the analysis.
A temporal or spatial lack of data then affects even more significantly satellite clock estimates. Figure
9 shows a general agreement of GOP rapid orbits to the final products of CODE and CNES (French
Space Agency) with a RMS of 3 cm and 6 cm for GPS and Galileo, respectively.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Service volume availability</title>
      <p>A monitoring of the Galileo Open Service volume, e.g. such as the availability of at least one
dualfrequency OS SIS and 3D DOP &lt; 6, is performed globally using navigation data only. The service
volume approach does not consider any errors stemming from environmental effects or user equipment.
We estimate service volume Key Parameter Indicators (KPIs) using a regular grid of ‘user’ points with
a horizontal resolution of 10×10 degrees, and a 900 seconds sampling interval. For each grid point and
time epoch, the availability of the dual-frequency OS SIS is checked and the Position DOP (PDOP) is
calculated using healthy satellites above the elevation angle cut-off 5 degrees. The healthy satellites are
considered according to SHS, DVS, SISA flags and the ephemeris validity period [13].</p>
      <p>The service volume availability KPIs are estimated using the G-Nut/Aset software and GOP BRDC
files on a monthly basis. Monthly percentages of at least one dual-frequency OS SIS is obtained from
the Worst User Location (WUL) on the globe. Figure 10 shows the evolution of the KPI during October
2018 and May 2021 for I/NAV data. An event of July 11-17, 2019 can be clearly observed with the KPI
decreasing down to 81.08%. Two other smaller events can also be observed: November 7-8, 2018 and
December 14, 2020, discussed at other places in the paper.</p>
      <p>Monthly percentages of available PDOP &lt; 6 is then represented as a weighted mean (with respect to
the latitude) over all grid points. Figure 11 shows the monthly KPI for mean availability of PDOP &lt; 6
during the period. On February 11, 2019, a total number of 22 satellites became active for Galileo and,
obviously, the Initial Service achieved low PDOP values at any time of a day enabling a continuous
positioning at any place on the Earth. Hence, monthly KPIs increased to values higher than 99%, with
a single exception of 87% occurring during the event in July 2019. The Minimum Performance Levels
(MPL) defined in the Galileo OS-SIS SDD [7] is 77% which has been satisfied continuously.
Figure 12 displays samples of global maps with monthly PDOP KPIs for December 2020 using
F/NAV (left) and I/NAV (right) broadcast navigation data types. This month includes the event from
December 14, 2020 and shows a small difference in KPIs between F/NAV and I/NAV data when these
were not available for all the satellites during 4h and 6h hours, respectively. However, the performance
still achieved values above 98% in both cases, and was a single such an event in 2020.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Site measured positioning performance</title>
      <p>A site-measured positioning performance exploits real data of selected stations, and thus includes
implicitly atmospheric, user equipment, and site environment errors. At GOP, the Galileo horizontal
and vertical positioning performance is thus monitored using 14 selected sites distributed globally, and
those providing Galileo E1, E5a and E5b signals. Reference coordinates are estimated in the first step
with the Precise Point Positioning (PPP) [20] method on a daily basis, using the G-Nut/Geb software
[21], [22], and GOP rapid products. A Single Point Positioning (SPP) method is then performed on a
daily basis using the G-Nut/Anubis software [23], exploiting code observations only from the selected
stations, and GOP consolidated navigation files. Two independent positioning solutions uses the
ionosphere-free linear combinations of E1+E5a and E1+E5b. The Galileo F/NAV and I/NAV broadcast
navigation type is used for the former and the latter linear combination. The SHS, DVS, SISA, and the
ephemeris validity period are considered prior using any satellite contributing to the performance
monitoring. All healthy satellites above the 5-degree elevation angle cut-off are then used. Station
coordinates, tropospheric path delays, and receiver clock offsets are estimated simultaneously epoch by
epoch at a 30-sec sampling interval provided the PDOP is below 6.</p>
      <p>Figure 13 displays several example time-series of horizontal and vertical positioning errors using
E1+E5a supported with F/NAV navigation data. The horizontal error, absolute vertical error and PDOP
are displayed in blue, green and yellow colors. A very good results can be observed at the AREG station
(top-left plot) during November 2020. An impact of a reduced number of Galileo satellites before
February 11, 2018 can be observed at the JFNG station (top-right plot) which resulted in regular periods
of a global unavailability of Galileo OS positioning during a day. The incident of unplanned
discontinuity of navigation data for all the satellites over 27 hours November 7-8, 2018 (reported with
NAGU 2018027-028), and including an impact of degrading OS SIS prior the outage on horizontal and
vertical positioning, are displayed for the AREQ station (bottom-left plot). The data quality may also
affect the positioning in the site-measured performance monitoring as it is visible in a period of frequent
degradations at the URUM station during August 2019.
Finally, Table 1 shows a typical monthly performance of Galileo horizontal and vertical positioning
errors at the 95th percentiles during 4th quarter of 2020. The best three global stations (AREG, METG,
and YEL2) achieved 0.6-1.0m and 1.3-1.8m horizontal and vertical errors respectively, and the worst
three stations (ASCG, JFNG, and MAYG) achieved 1.3-1.8m and 2.5-3.5m, respectively. This results
is typical for solutions using either F/NAV or I/NAV data during 2019 and 2020 with more or less
stable constellation and, currently, it is the best performance from all other GNSS systems.</p>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>The Galileo OS SIS performance monitoring at GOP comprises of a fully independent chain of
processes including the exploited software as well as input reference products. The GOP solution is
also performed in a rapid mode (or shorter), i.e. providing all results within 1-2 days after the last
observation. It is based on the GOP fast consolidation of global navigation files, early generation of
GPS and Galileo reference products and key-parameter indicators estimated using the G-Nut software
tools. The solution can be easily extended to additional indicators, other GNSS or to a real-time mode.</p>
      <p>During the period (2018/Q4 – 2020/Q4), the Galileo OS SIS performed very well in terms of all the
positioning aspects monitored at GOP and satisfied the MPL defined in the OS SIS SDD. However,
few events have been observed, those related to the positioning performance analysed at GOP, reported
to the GRC and GSA on a quarterly basis, and some of them briefly discussed in this paper:
• 2018, Nov 7-8 – unplanned discontinuity of navigation data for all the satellites over 27 hours
(reported with NAGU 2018027-028).
• 2019, Feb 11 – activated new Galileo satellites (E13, E15, E33 and E36), and firstly achieving
24-hour continuous Galileo PDOP &lt; 6 in a global scope.
• 2019, July 11-17 – unplanned unavailability of OS SIS over 6 days for all the satellites (reported
with NAGU 2019025-027).
• 2019, Sept 2-3 – satellite on-board navigation data provision only (i.e. without ground update)
for all satellites over 12 hours.
• 2019, Oct 29 – short-term E11 satellite clock degradation (followed by the satellite
deactivation) with a 30-min impact on positioning around the South-East Africa.
• 2020, Dec 14 – 4h and 6h provision of on-board navigation data for all satellites and F/NAV
and I/NAV, respectively.</p>
      <p>• 2020, Oct 30 – activating the two eccentric Galileo satellites (E14 and E18).</p>
    </sec>
    <sec id="sec-7">
      <title>7. Acknowledgements</title>
      <p>We acknowledge the European Union and the European GNSS Agency (GSA) for co-financing a
cooperation of the Galileo Reference Center (GRC) and the Member States within the GRC-MS project
since November 2019 (Grant agreement nr. GSA/GRANT/04/2016), and supporting independent
monitoring of the Galileo system performance.</p>
    </sec>
    <sec id="sec-8">
      <title>8. References</title>
      <p>[1] P. Buist, A. Mozo, H. Tork (2017) Overview of the Galileo Reference Centre: Mission,
Architecture and Operational Concept, Proceedings of the 30th International Technical Meeting of
The Satellite Division of the Institute of Navigation (ION GNSS+ 2017), Portland, Oregon,
September 2017, pp. 1485-1495.
[2] P. Buist, M. Porretta, A. Mozo, H. Tork (2018) The Galileo Reference Centre and Its Role in the
Galileo Service Provision, 69th International Astronautical Congress (IAC), Bremen, Germany,
15 October 2018.
[3] J. Douša (2018) GOP’s consolidated multi-GNSS navigation data archive,
https://doi.org/10.24414/c4ba-kf16
[4] J.M. Dow, R.E. Neilan, C. Rizos (2009) The International GNSS Service in a changing landscape
of Global Navigation Satellite Systems, J. Geod. 83:191–198, doi:10.1007/s00190-008-0300-3
[5] O. Montenbruck, P. Steigenberger, L. Prange, Z. Deng, Q. Zhao, F. Perosanz, I. Romero, C. Noll,
A. Stürze, G. Weber, R. Schmid, K. MacLeod, S. Schaer (2017) Multi-GNSS Experiment (MGEX)
of the International GNSS Service (IGS) – Achievements, Prospects and Challenges, Adv. Space
Res. 59(7):1671-1697, doi:10.1016/j.asr.2017.01.011
[6] Galileo Open Service - Signal In Space Interface Control Document (SIS ICD v2, January 2021),
https://www.gsc-europa.eu/sites/default/files/sites/all/files/Galileo_OS_SIS_ICD_v2.0.pdf.
[7] Galileo Open Service - Service Definition Document (Galileo OS SDD v1.1, May 2019,
https://www.gsc-europa.eu/sites/default/files/sites/all/files/Galileo-OS-SDD_v1.1.pdf.
[8] R. Dach, S. Lutz, P. Walser, P. Fridez (Eds) (2015) Bernese GNSS Software Version 5.2. User
manual, Astronomical Institute, University of Bern, Bern Open Publishing.
doi:10.7892/boris.72297
[9] J. Douša (2004) Precise Orbits for Ground-Based GPS Meteorology: Processing Strategy and
Quality Assessment of the Orbits Determined at Geodetic Observatory Pecný, J. Meteor. Soc. Jap.,
82:371-380
[10] J. Douša (2012) Development of the GLONASS ultra-rapid orbit determination at Geodetic
Observatory Pecný, In: Geodesy for Planet Earth, Proceedings of the IAG Symposium, S.Kenyon,
M.C.Pacino, U.Marti (eds.), Buenos Aires, Aug 31-Sep 4, IAG Symposia, Springer,
136:10291036
[11] D. Arnold, M. Meindl, G. Beutler, R. Dach, S. Schaer, S. Lutz, L. Prange, K. Sośnica, M. Mervart,
A. Jäggi (2015). CODE’s new solar radiation pressure model for GNSS orbit determination. J.</p>
      <p>Geod. 89, 775–791, doi:10.1007/s00190-015-0814-4
[12] IERS Conventions (2010), IERS Technical Note 36, G. Petit and B. Luzum (eds.) Frankfurt am</p>
      <p>Main: Verlag des Bundesamts für Kartographie und Geodäsie, 179 pp.
[13] M. Ge, J. Chen, J. Douša, G. Gendt, J. Wickert (2012) A computationally efficient approach for
estimating high-rate satellite clocks corrections in real-time, GPS Solut., Springer
Berlin/Heidelberg, 16(1):9-17, doi:10.1007/s10291-011-0206-z
[14] O. Montenbruck, A. Hauschiled, P. Steigenberger (2014) Differential Code Bias Estimation using
Multi‐GNSS Observations and Global Ionosphere Maps, Navig. J. ION, 61(3):191-201,
doi:10.1002/navi.64
[15] L. Zhao, J. Douša, S. Ye, P. Václavovic (2020), A flexible strategy for handling the datum and
initial bias in real-time GNSS satellite clock estimation, J Geodesy, 94:1,
doi:10.1007/s00190-01901328-9
[16] L. Prange, R. Dach, S. Lutz, S. Schaer, A. Jäggi (2015) The CODE MGEX Orbit and Clock</p>
      <p>Solution. In: C. Rizos, P. Willis (eds) IAG 150 Years. IAG Symposia, Springer, Vol 143
[17] L. Prange, E. Orliac, R. Dach, et al. (2017) CODE’s five-system orbit and clock solution—the
challenges of multi-GNSS data analysis, J. Geod., 91:345
[18] S. Loyer, F. Perosanz, F. Mercier, H. Capdeville, J.C. Marty (2012) Zero-difference GPS
ambiguity resolution at CNES–CLS IGS Analysis Center. J. Geod. 86:991–1003.
doi:10.1007/s00190-012-0559-2
[19] Sidorov D.,Rolf D, Polleb, Larse P, Jäggia A (2020) Adopting the empirical CODE orbit model to</p>
      <p>Galileo satellites, Adv Space Res, (in press) DOI: 10.1016/j.asr.2020.05.028
[20] J.F. Zumberge, M.B. Heflin, D.C. Jefferson, M.M. Watkins, F.H. Webb (1997) Precise point
positioning for the efficient and robust analysis of GPS data from large networks J. Geoph. Res.
(SE) 102:5005-5017
[21] P. Václavovic, O. Nesvadba (2020) Comparison and assessment of float, fixed, and smoothed
Precise Point Positioning, Acta Geodyn. Geomater., Vol. 17, No. 3 (199), 329–340, 2020,
doi:10.13168/AGG.2020.0024
[22] P. Václavovic, J. Douša, G. Gyori (2013) G-Nut software library - state of development and first
results, Acta Geodyn Geomater, Vol. 10, No. 4 (172), pp 431-436, doi:10.13168/AGG.2013.0042.
[23] P. Václavovic, J. Douša (2016) G-Nut/Anubis – open-source tool for multi-GNSS data monitoring,
In: Rizos Ch and Willis P (eds.), IAG Symposia Series, IAG 150 Years. Springer, 143:775-782,
doi:10.1007/1345_2015_157</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>