Tag: PPP

  • Veripos Picked for Offshore Fleet Positioning

    Singapore-based Miclyn Express Offshore (MEO), a provider of offshore support vessels across South East Asia, Australia and the Middle East, has awarded Veripos a five-year contract for provision of high-precision GNSS positioning services in support of its fleet of 27 ships.

    Under the terms of the contract, Veripos will provide MEO’s fleet with Veripos Ultra Precise Point Positioning (PPP) service designed to deliver decimeter-level accuracies globally along with associated integrated mobile receivers. Among the first vessels assigned to utilize the service and equipment are MEO’s new 2,000 dwt platform supply vessels, MEO Ranger and MEO Resolution, both of which have been equipped with LD5-GG2 receivers. Meanwhile, four older MEO vessels have been similarly configured to receive Veripos Ultra service.

    Commenting on the latest contract award, Walter Steedman, Veripos chief executive officer, said it further consolidated the company’s continuing leadership for provision of precise GNSS positioning services for offshore applications throughout the region and beyond.

    Miclyn Express Offshore employs more than 1,400 shore-based personnel and seafarers.

  • NovAtel Launches Correct OEM Positioning Solution

    NovAtel Launches Correct OEM Positioning Solution

    NovAtel Correct.
    NovAtel Correct.

    NovAtel, Inc., OEM provider of high-precision GNSS positioning products, has launched its NovAtel Correct positioning technology. NovAtel Correct optimally combines data from multiple GNSS satellite constellations with corrections from a variety of sources, to deliver the best position solution possible.

    NovAtel Correct provides integrators with the opportunity to choose pricing and subscription options that best match their OEM business objectives. Delivery of correction data is available via satellite or Internet, depending on the requirements of the application. With NovAtel in control of the entire positioning solution, future innovation including seamless integration with all positioning modes and correction types is assured.

    Designed for NovAtel’s OEM6 high-precision receivers, the NovAtel Correct precise point positioning (PPP) solution delivers decimeter-level accuracy worldwide. L-band delivered PPP corrections from TerraStar are supported by NovAtel Correct without users having to add base-station infrastructure. Developers of land, airborne and near shore applications can purchase subscriptions to TerraStar’s correction service directly through NovAtel.

    “For a number of reasons, many of our customers have been eager for an end-to-end NovAtel OEM positioning service,” said Jason Hamilton, VP, Marketing for NovAtel. “NovAtel Correct rounds out our product and service offering and gives customers one-stop shopping for receivers, antennas and correction services.”

    Satellite and NTRIP-based solutions will be available for OEM6 products in Q1 2014 for all applications requiring decimetre-level positioning.

    NovAtel OEM628 triple-frequency +  L-Band GNSS receiver.
    NovAtel OEM628 triple-frequency + L-Band GNSS receiver.
  • Trimble Introduces Ashtech High-Accuracy GNSS Module for System Integrators

    Trimble Introduces Ashtech High-Accuracy GNSS Module for System Integrators

    MB-OneTrimble introduced today the Ashtech MB-One GNSS module. The MB-One delivers highly accurate GNSS-based heading plus pitch or roll in an advanced industry standard form-factor for system integrators.

    The announcement was made today at the AUVSI 2013 Conference and Exhibition.

    Its embedded Z-Blade GNSS technology uses all available GNSS signals equally, without any constellation preference, to deliver fast and stable solutions. The MB-One is designed to add precise positioning and heading in a wide variety of applications such as unmanned, agriculture, marine and military systems.

    “System integrators demand high performance, reliability and support for their positioning solutions,” said Olivier Casabianca, business development manager for the Trimble’s GNSS OEM products. “The MB-One is designed for easy integration and rugged dependability. Users can leverage the module’s Ethernet capability and easy-to-use web browser interface to quickly and cost-effectively develop their products and solutions.”

    The MB-One features an enhanced dual-core GNSS engine with 240 channels capable of tracking a large range of GNSS systems including GPS, GLONASS, Galileo and BeiDou. It uses over-the-air satellite corrections using L-Band hardware to achieve decimeter-level accuracy. The module is capable of receiving and decoding Precise Point Positioning (PPP) to output a highly accurate position solution that removes the need for a local base station.

    The Ashtech MB-One module will be available through the Trimble GNSS OEM international network of representatives and authorized dealers. Evaluation units will be available in the fourth quarter of 2013 and production units are expected to be available in the first quarter of 2014.

     

  • RTKLIB Open Source GNSS Precise Positioning Software Supports NV08C Receiver

    RTKLIB, a developer of open source software for standard and precise GNSS positioning, has released its latest RTKLIB software (version 2.4.2), which fully supports NVS Technologies’ BINR proprietary binary protocol and the NV08C GNSS receiver series.

    The use of RTKLIB, in conjunction with NVS Technologies’ NV08C GNSS receiver series, including the highly integrated NV08C-CSM surface mount module with geodetic grade raw data output, enables GNSS system designers and OEMs to develop highly accurate, low cost and compact precision-grade positioning and navigation equipment.

    RTKLIB features include:

    • Full compatibility with NVS Technologies’ NV08C Series GNSS Receivers.
    • A portable program library and several APs.
    • Standard and precise positioning algorithms using GPS, GLONASS, Galileo, QZSS, BeiDou and SBAS.
    • Supports various GNSS based positioning modes, both for real-time and post-processing, including: Single, DGPS/DGNSS, Kinematic, Static, Moving-Baseline, Fixed, PPP-Kinematic, PPP-Static and PPP-Fixed.
    • Positioning mode for real‐time and post‐processing, including Single, SBAS, DGPS, RTK, Static, Moving‐base and PPP.
    • Supports many standard formats and protocols for GNSS, including RINEX 2 & 3, RTCM 2 & 3, BINEX, NTRIP 1.0, RTCA/DO-229C, NMEA 0183, SP3-c, ANTEX 1.4, IONEX 1.0, NGS PCV and EMS 2.0.
    • External communication via Serial, TCP/IP, NTRIP, local log file (record and playback) and FTP/HTTP (auto download).

    Contact NVS Technologies for specific features compatibility. Visit www.rtklib.com for RTKLIB’s latest (ver. 2.4.2) software package download, release note, information, tutorial, manual and support.

  • GNSS PPP Workshop Early Registration Extended to May 3

    The International Association of Geodesy, Natural Resources Canada, the International GNSS Service, and York University will be hosting GNSS Precise Point Positioning: Reaching Full Potential in Ottawa, Canada, June 12-14, 2013.

    The primary objective of this workshop is to provide a forum for international experts from academia, government and industry to discuss PPP-related matters, including data processing, error modelling, data products, dissemination, applications, and associated policy.

    The preliminary program is now available on the workshop website, along with details about accommodations and registration. Note that early registration has been extended until May 3, 2013.

    Given recent rapid developments in PPP technology, the objectives of this workshop will be to:

    1. Provide a forum for international experts from academia, government and industry to discuss PPP-related matters, including data processing, error modelling, data products, dissemination, applications, and associated policy.
    2. Define the current state of PPP performance and communicate global PPP activities and applications in all sectors.
    3. Identify and investigate the technical and non-technical issues that need to be addressed to improve the technology.
    4. Suggest PPP performance and utility in the next five to ten years.
  • Real-time PPP with Galileo Demonstrated by Fugro

    Real-time PPP with Galileo Demonstrated by Fugro

    Fugro Seastar AS has been looking forward to demonstrating Real-Time Precise Point Positioning (PPP) based solely on Galileo signals since the last two satellites were launched October 12, the company said.

    Those two satellites brought the constellation to a total of four satellites, the minimum required to permit calculation of a Galileo-only position. Fugro achieved this task on March 18, within a week of all four Galileo satellites being activated. Fugro is now generating Galileo orbit and clock corrections, which can be used in conjunction with the Fugro G2 decimeter-level corrections associated with its GPS/GLONASS PPP service.

    The plot below shows performance of the Fugro orbit and clock service using GPS, GLONASS and Galileo satellites between 06:00 and 08:00 UTC,  March 18, 2013, in Oslo, Norway. Between 07:00 and 07:30 UTC, only the four Galileo satellites were used for the solution, which achieved a similar accuracy to Fugro’s existing service, the company said.

    “It is interesting that the noise level of the position is better with Galileo alone than when GPS and GLONASS satellites are also used,” Fugro said in a statement. “This is very encouraging as with only four satellites to choose from, the geometry of the Galileo-based solution is much weaker than the solutions before and after the Galileo-only period. This performance exceeds our expectations and suggests a strong future for Fugro’s Galileo PPP solution.”

    Fugro-chart

  • Innovation: A Better Way

    Innovation: A Better Way

    Monitoring the Ionosphere with Integer-Leveled GPS Measurements

    By Simon Banville, Wei Zhang, and  Richard B. Langley

    GPS World photo
    INNOVATION INSIGHTS by Richard Langley

    IT’S NOT JUST FOR POSITIONING, NAVIGATION, AND TIMING. Many people do not realize that GPS is being used in a variety of ways in addition to those of its primary mandate, which is to provide accurate position, velocity, and time information.

    The radio signals from the GPS satellites must traverse the Earth’s atmosphere on their way to receivers on or near the Earth’s surface. The signals interact with the atoms, molecules, and charged particles that make up the atmosphere, and the process slightly modifies the signals. It is these modified or perturbed signals that a receiver actually processes. And should a signal be reflected or diffracted by some object in the vicinity of the receiver’s antenna, the signal is further perturbed — a phenomenon we call multipath.

    Now, these perturbations are a bit of a nuisance for conventional users of GPS. The atmospheric effects, if uncorrected, reduce the accuracy of the positions, velocities, and time information derived from the signals. However, GPS receivers have correction algorithms in their microprocessor firmware that attempt to correct for the effects. Multipath, on the other hand, is difficult to model although the use of sophisticated antennas and advanced receiver technologies can minimize its effect.

    But there are some GPS users who welcome the multipath or atmospheric effects in the signals. By analyzing the fluctuations in signal-to-noise-ratio due to multipath, the characteristics of the reflector can be deduced. If the reflector is the ground, then the amount of moisture in the soil can be measured. And, in wintery climes, changes in snow depth can be tracked from the multipath in GPS signals.

    The atmospheric effects perturbing GPS signals can be separated into those that are generated in the lower part of the atmosphere, mostly in the troposphere, and those generated in the upper, ionized part of the atmosphere — the ionosphere. Meteorologists are able to extract information on water vapor content in the troposphere and stratosphere from the measurements made by GPS receivers and regularly use the data from networks of ground-based continuously operating receivers and those operating on some Earth-orbiting satellites to improve weather forecasts.

    And, thanks to its dispersive nature, the ionosphere can be studied by suitably combining the measurements made on the two legacy frequencies transmitted by all GPS satellites. Ground-based receiver networks can be used to map the electron content of the ionosphere, while Earth-orbiting receivers can profile electron density. Even small variations in the distribution of ionospheric electrons caused by earthquakes; tsunamis; and volcanic, meteorite, and nuclear explosions can be detected using GPS.

    In this month’s column, I am joined by two of my graduate students, who report on an advance in the signal processing procedure for better monitoring of the ionosphere, potentially allowing scientists to get an even better handle on what’s going on above our heads.


    Representation and forecast of the electron content within the ionosphere is now routinely accomplished using GPS measurements. The global distribution of permanent ground-based GPS tracking stations can effectively monitor the evolution of electron structures within the ionosphere, serving a multitude of purposes including satellite-based communication and navigation.

    It has been recognized early on that GPS measurements could provide an accurate estimate of the total electron content (TEC) along a satellite-receiver path. However, because of their inherent nature, phase observations are biased by an unknown integer number of cycles and do not provide an absolute value of TEC. Code measurements (pseudoranges), although they are not ambiguous, also contain frequency-dependent biases, which again prevent a direct determination of TEC. The main advantage of code over phase is that the biases are satellite- and receiver-dependent, rather than arc-dependent. For this reason, the GPS community initially adopted, as a common practice, fitting the accurate TEC variation provided by phase measurements to the noisy code measurements, therefore removing the arc-dependent biases. Several variations of this process were developed over the years, such as phase leveling, code smoothing, and weighted carrier-phase leveling (see Further Reading for background literature).

    The main challenge at this point is to separate the code inter-frequency biases (IFBs) from the line-of-sight TEC. Since both terms are linearly dependent, a mathematical representation of the TEC is usually required to obtain an estimate of each quantity. Misspecifications in the model and mapping functions were found to contribute significantly to errors in the IFB estimation, suggesting that this process would be better performed during nighttime when few ionospheric gradients are present. IFB estimation has been an ongoing research topic for the past two decades are still remains an issue for accurate TEC determination.

    A particular concern with IFBs is the common assumption regarding their stability. It is often assumed that receiver IFBs are constant during the course of a day and that satellite IFBs are constant for a duration of a month or more. Studies have clearly demonstrated that intra-day variations of receiver instrumental biases exist, which could possibly be related to temperature effects. This assumption was shown to possibly introduce errors exceeding 5 TEC units (TECU) in the leveling process, where 1 TECU corresponds to 0.162 meters of code delay or carrier advance at the GPS L1 frequency (1575.42 MHz).

    To overcome this limitation, one could look into using solely phase measurements in the TEC estimation process, and explicitly deal with the arc-dependent ambiguities. The main advantage of such a strategy is to avoid code-induced errors, but a larger number of parameters needs to be estimated, thereby weakening the strength of the adjustment. A comparison of the phase-only (arc-dependent) and phase-leveled (satellite-dependent) models showed that no model performs consistently better. It was found that the satellite-dependent model performs better at low-latitudes since the additional ambiguity parameters in the arc-dependent model can absorb some ionospheric features (such as gradients). On the other hand, when the mathematical representation of the ionosphere is realistic, the leveling errors may more significantly impact the accuracy of the approach.

    The advent of precise point positioning (PPP) opened the door to new possibilities for slant TEC (STEC) determination. Indeed, PPP can be used to estimate undifferenced carrier-phase ambiguity parameters on L1  and L2, which can then be used to remove the ambiguous characteristics of the carrier-phase observations. To obtain undifferenced ambiguities free from ionospheric effects, researchers have either used the widelane/ionosphere-free (IF) combinations, or the Group and Phase Ionospheric Calibration (GRAPHIC) combinations. One critical problem with such approaches is that code biases propagate into the estimated ambiguity parameters. Therefore, the resulting TEC estimates are still biased by unknown quantities, and might suffer from the unstable datum provided by the IFBs.

    The recent emergence of ambiguity resolution in PPP presented sophisticated means of handling instrumental biases to estimate integer ambiguity parameters. One such technique is the decoupled-clock method, which considers different clock parameters for the carrier-phase and code measurements. In this article, we present an “integer-leveling” method, based on the decoupled-clock model, which uses integer carrier-phase ambiguities obtained through PPP to level the carrier-phase observations.

    Standard Leveling Procedure

    This section briefly reviews the basic GPS functional model, as well as the observables usually used in ionospheric studies. A common leveling procedure is also presented, since it will serve as a basis for assessing the performance of our new method.

    Ionospheric Observables. The standard GPS functional model of dual-frequency carrier-phase and code observations can be expressed as:

    In-E1   (1)

    In-E2    (2)

    In-E3   (3)

    In-E4   (4)

    where Φi j is the carrier-phase measurement to satellite j on the Li link and, similarly, Pi j is the code measurement on Li. The term In-Pj is the biased ionosphere-free range between the satellite and receiver, which can be decomposed as:

    In-E5   (5)

    The instantaneous geometric range between the satellite and receiver antenna phase centers is ρ j. The receiver and satellite clock errors, respectively expressed as dT and dtj, are expressed here in units of meters. The term Tj stands for the tropospheric delay, while the ionospheric delay on L1 is represented by I j and is scaled by the frequency-dependent constant μ for L2, where In-u=. The biased carrier-phase ambiguities are symbolized by  and are scaled by their respective wavelengths i). The ambiguities can be explicitly written as:

    In-E6   (6)

    where Ni j is the integer ambiguity, bi is a receiver-dependent bias, and bi j is a satellite-dependent bias. Similarly, Bi and Bi j are instrumental biases associated with code measurements. Finally, ε contains unmodeled quantities such as noise and multipath, specific to the observable. The overbar symbol indicates biased quantities.

    In ionospheric studies, the geometry-free (GF) signal combinations are formed to virtually eliminate non-dispersive terms and thus provide a better handle on the quantity of interest:

    In-E7   (7)

    In-E8   (8)

    where IFBr and IFB j represent the code inter-frequency biases for the receiver and satellite, respectively. They are also commonly referred to as differential code biases (DCBs). Note that the noise terms (ε) are neglected in these equations for the sake of simplicity.

    Weighted-Leveling Procedure. As pointed out in the introduction, the ionospheric observables of Equations (7) and (8) do not provide an absolute level of ionospheric delay due to instrumental biases contained in the measurements. Assuming that these biases do not vary significantly in time, the difference between the phase and code observations for a particular satellite pass should be a constant value (provided that no cycle slip occurred in the phase measurements). The leveling process consists of removing this constant from each geometry-free phase observation in a satellite-receiver arc:

    In-E9   (9)

    where the summation is performed for all observations forming the arc. An elevation-angle-dependent weight (w) can also be applied to minimize the noise and multipath contribution for measurements made at low elevation angles. The double-bar symbol indicates leveled observations.

    Integer-Leveling Procedure

    The procedure of fitting a carrier-phase arc to code observations might introduce errors caused by code noise, multipath, or intra-day code-bias variations. Hence, developing a leveling approach that relies solely on carrier-phase observations is highly desirable. Such an approach is now possible with the recent developments in PPP, allowing for ambiguity resolution on undifferenced observations. This procedure has gained significant momentum in the past few years, with several organizations generating “integer clocks” or fractional offset corrections for recovering the integer nature of the undifferenced ambiguities. Among those organizations are, in alphabetical order, the Centre National d’Études Spatiale; GeoForschungsZentrum; GPS Solutions, Inc.; Jet Propulsion Laboratory; Natural Resources Canada (NRCan); and Trimble Navigation. With ongoing research to improve convergence time, it would be no surprise if PPP with ambiguity resolution would become the de facto methodology for processing data on a station-by-station basis. The results presented in this article are based on the products generated at NRCan, referred to as “decoupled clocks.”

    The idea behind integer leveling is to introduce integer ambiguity parameters on L1 and L2, obtained through PPP processing, into the geometry-free linear combination of Equation (7). The resulting integer-leveled observations, in units of meters, can then be expressed as:
    In-E10   (10)
    where In-NJ1 and In-NJ2 are the ambiguities obtained from the PPP solution, which should be, preferably, integer values. Since those ambiguities are obtained with respect to a somewhat arbitrary ambiguity datum, they do not allow instant recovery of an unbiased slant ionospheric delay. This fact was highlighted in Equation (10), which indicates that, even though the arc-dependency was removed from the geometry-free combination, there are still receiver- and satellite-dependent biases (br and b j, respectively) remaining in the integer-leveled observations. The latter are thus very similar in nature to the standard-leveled observations, in the sense that the biases br and b j replace the well-known IFBs. As a consequence, integer-leveled observations can be used with any existing software used for the generation of TEC maps. The motivation behind using integer-leveled observations is the mitigation of leveling errors, as explained in the next sections.

    Slant TEC Evaluation

    As a first step towards assessing the performance of integer-leveled observations, STEC values are derived on a station-by-station basis. The slant ionospheric delays are then compared for a pair of co-located receivers, as well as with global ionospheric maps (GIMs) produced by the International GNSS Service (IGS).

    Leveling Error Analysis. Relative leveling errors between two co-located stations can be obtained by computing between-station differences of leveled observations:

    In-E11   (11)

    where subscripts A and B identify the stations involved, and εl is the leveling error. Since the distance between stations is short (within 100 meters, say), the ionospheric delays will cancel, and so will the satellite biases (b j) which are observed at both stations. The remaining quantities will be the (presumably constant) receiver biases and any leveling errors. Since there are no satellite-dependent quantities in Equation (11), the differenced observations obtained should be identical for all satellites observed, provided that there are no leveling errors. The same principles apply to observations leveled using other techniques discussed in the introduction. Hence, Equation (11) allows comparison of the performance of various leveling approaches.

    This methodology has been applied to a baseline of approximately a couple of meters in length between stations WTZJ and WTZZ, in Wettzell, Germany. The observations of both stations from March 2, 2008, were leveled using a standard leveling approach, as well as the method described in this article. Relative leveling errors computed using Equation (11) are displayed in Figure 1, where each color represents a different satellite. It is clear that code noise and multipath do not necessarily average out over the course of an arc, leading to leveling errors sometimes exceeding a couple of TECU for the standard leveling approach (see panel (a)). On the other hand, integer-leveled observations agree fairly well between stations, where leveling errors were mostly eliminated. In one instance, at the beginning of the session, ambiguity resolution failed at both stations for satellite PRN 18, leading to a relative error of 1.5 TECU, more or less. Still, the advantages associated with integer leveling should be obvious since the relative error of the standard approach is in the vicinity of -6 TECU for this satellite.

    FIGURE 1 Relative leveling errors between stations WTZJ and WTZZ on March 2, 2008: (a) standard-leveled observations and (b) integer-leveled observations.
    FIGURE 1. Relative leveling errors between stations WTZJ and WTZZ on March 2, 2008: (a) standard-leveled observations and (b) integer-leveled observations.

    The magnitude of the leveling errors obtained for the standard approach agrees fairly well with previous studies (see Further Reading). In the event that intra-day variations of the receiver IFBs are observed, even more significant biases were found to contaminate standard-leveled observations. Since the decoupled-clock model used for ambiguity resolution explicitly accounts for possible variations of any equipment delays, the estimated ambiguities are not affected by such effects, leading to improved leveled observations.

    STEC Comparisons. Once leveled observations are available, the next step consists of separating STEC from instrumental delays. This task can be accomplished on a station-by-station basis using, for example, the single-layer ionospheric model. Replacing the slant ionospheric delays (I j) in Equation (10) by a bilinear polynomial expansion of VTEC leads to:

    In-E12    (12)

    where M(e) is the single-layer mapping function (or obliquity factor) depending on the elevation angle (e) of the satellite. The time-dependent coefficients a0, a1, and a2 determine the mathematical representation of the VTEC above the station. Gradients are modeled using Δλ, the difference between the longitude of the ionospheric pierce point and the longitude of the mean sun, and Δϕ, the difference between the geomagnetic latitude of the ionospheric pierce point and the geomagnetic latitude of the station. The estimation procedure described by Attila Komjathy (see Further Reading) is followed in all subsequent tests. An elevation angle cutoff of 10 degrees was applied and the shell height used was 450 kilometers. Since it is not possible to obtain absolute values for the satellite and receiver biases, the sum of all satellite biases was constrained to a value of zero. As a consequence, all estimated biases will contain a common (unknown) offset. STEC values, in TECU, can then be computed as:

    In-E13     (13)

    where the hat symbol denotes estimated quantities, and  is equal to zero (that is, it is not estimated) when biases are obtained on a station-by-station basis. The frequency, f1, is expressed in Hz. The numerical constant 40.3, determined from values of fundamental physical constants, is sufficiently precise for our purposes, but is a rounding of the more precise value of 40.308.

    While integer-leveled observations from co-located stations show good agreement, an external TEC source is required to make sure that both stations are not affected by common errors. For this purpose, Figure 2 compares STEC values computed from GIMs produced by the IGS and STEC values derived from station WTZJ using both standard- and integer-leveled observations. The IGS claims root-mean-square errors on the order of 2-8 TECU for vertical TEC, although the ionosphere was quiet on the day selected, meaning that errors at the low-end of that range are expected. Errors associated with the mapping function will further contribute to differences in STEC values. As apparent from Figure 2, no significant bias can be identified in integer-leveled observations. On the other hand, negative STEC values (not displayed in Figure 2) were obtained during nighttimes when using standard-leveled observations, a clear indication that leveling errors contaminated the observations.

    FIGURE 2 Comparison between STEC values obtained from a global ionospheric map and those from station WTZJ using standard- and integer-leveled observations.
    FIGURE 2. Comparison between STEC values obtained from a global ionospheric map and those from station WTZJ using standard- and integer-leveled observations.

    STEC Evaluation in the Positioning Domain. Validation of slant ionospheric delays can also be performed in the positioning domain. For this purpose, a station’s coordinates from processing the observations in static mode (that is, one set of coordinates estimated per session) are estimated using (unsmoothed) single-frequency code observations with precise orbit and clock corrections from the IGS and various ionosphere-correction sources. Figure 3 illustrates the convergence of the 3D position error for station WTZZ, using STEC corrections from the three sources introduced previously, namely: 1) GIMs from the IGS, 2) STEC values from station WTZJ derived from standard leveling, and 3) STEC values from station WTZJ derived from integer leveling. The reference coordinates were obtained from static processing based on dual-frequency carrier-phase and code observations. The benefits of the integer-leveled corrections are obvious, with the solution converging to better than 10 centimeters. Even though the distance between the stations is short, using standard-leveled observations from WTZJ leads to a biased solution as a result of arc-dependent leveling errors. Using a TEC map from the IGS provides a decent solution considering that it is a global model, although the solution is again biased.

    FIGURE 3 Single-frequency code-based positioning results for station WTZZ (in static mode) using different ionosphere-correction sources: GIM and STEC values from station WTZJ using standard- and integer-leveled observations.
    FIGURE 3. Single-frequency code-based positioning results for station WTZZ (in static mode) using different ionosphere-correction sources: GIM and STEC values from station WTZJ using standard- and integer-leveled observations.

    This station-level analysis allowed us to confirm that integer-leveled observations can seemingly eliminate leveling errors, provided that carrier-phase ambiguities are fixed to proper integer values. Furthermore, it is possible to retrieve unbiased STEC values from those observations by using common techniques for isolating instrumental delays. The next step consisted of examining the impacts of reducing leveling errors on VTEC.

    VTEC Evaluation

    When using the single-layer ionospheric model, vertical TEC values can be derived from the STEC values of Equation (13) using:

    In-E14    (14)

    Dividing STEC by the mapping function will also reduce any bias caused by the leveling procedure. Hence, measures of VTEC made from a satellite at a low elevation angle will be less impacted by leveling errors. When the satellite reaches the zenith, then any bias in the observation will fully propagate into the computed VTEC values. On the other hand, the uncertainty of the mapping function is larger at low-elevation angles, which should be kept in mind when analyzing the results.

    Using data from a small regional network allows us to assess the compatibility of the VTEC quantities between stations. For this purpose, GPS data collected as a part of the Western Canada Deformation Array (WCDA) network, still from March 2, 2008, was used. The stations of this network, located on and near Vancouver Island in Canada, are indicated in Figure 4. Following the model of Equation (12), all stations were integrated into a single adjustment to estimate receiver and satellite biases as well as a triplet of time-varying coefficients for each station. STEC values were then computed using Equation (13), and VTEC values were finally derived from Equation (14). This procedure was again implemented for both standard- and integer-leveled observations.

    FIGURE 4. Network of stations used in the VTEC evaluation procedures.
    FIGURE 4. Network of stations used in the VTEC evaluation procedures.

    To facilitate the comparison of VTEC values spanning a whole day and to account for ionospheric gradients, differences with respect to the IGS GIM were computed. The results, plotted by elevation angle, are displayed in Figure 5 for all seven stations processed (all satellite arcs from the same station are plotted using the same color). The overall agreement between the global model and the station-derived VTECs is fairly good, with a bias of about 1 TECU. Still, the top panel demonstrates that, at high elevation angles, discrepancies between VTEC values derived from standard-leveled observations and the ones obtained from the model have a spread of nearly 6 TECU. With integer-leveled observations (see bottom panel), this spread is reduced to approximately 2 TECU. It is important to realize that the dispersion can be explained by several factors, such as remaining leveling errors, the inexact receiver and satellite bias estimates, and inaccuracies of the global model. It is nonetheless expected that leveling errors account for the most significant part of this error for standard-leveled observations.

    For satellites observed at a lower elevation angle, the spread between arcs is similar for both methods (except for station UCLU in panel (a) for which the estimated station IFB parameter looks significantly biased). As stated previously, the reason is that leveling errors are reduced when divided by the mapping function. The latter also introduces further errors in the comparisons, which explains why a wider spread should typically be associated with low-elevation-angle satellites. Nevertheless, it should be clear from Figure 5 that integer-leveled observations offer a better consistency than standard-leveled observations.

    FIGURE 5 VTEC differences, with respect to the IGS GIM, for all satellite arcs as a function of the elevation angle of the satellite, using (a) standard-leveled observations and (b) integer-leveled observations.
    FIGURE 5. VTEC differences, with respect to the IGS GIM, for all satellite arcs as a function of the elevation angle of the satellite, using (a) standard-leveled observations and (b) integer-leveled observations.
    Conclusion

    The technique of integer leveling consists of introducing (preferably) integer ambiguity parameters obtained from PPP into the geometry-free combination of observations. This process removes the arc dependency of the signals, and allows integer-leveled observations to be used with any existing TEC estimation software. While leveling errors of a few TECU exist with current procedures, this type of error can be eliminated through use of our procedure, provided that carrier-phase ambiguities are fixed to the proper integer values. As a consequence, STEC values derived from nearby stations are typically more consistent with each other. Unfortunately, subsequent steps involved in generating VTEC maps, such as transforming STEC to VTEC and interpolating VTEC values between stations, attenuate the benefits of using integer-leveled observations.

    There are still ongoing challenges associated with the GIM-generation process, particularly in terms of latency and three-dimensional modeling. Since ambiguity resolution in PPP can be achieved in real time, we believe that integer-leveled observations could benefit near-real-time ionosphere monitoring. Since ambiguity parameters are constant for a satellite pass (provided that there are no cycle slips), integer ambiguity values (that is, the leveling information) can be carried over from one map generation process to the next. Therefore, this methodology could reduce leveling errors associated with short arcs, for instance.

    Another prospective benefit of integer-leveled observations is the reduction of leveling errors contaminating data from low-Earth-orbit (LEO) satellites, which is of particular importance for three-dimensional TEC modeling. Due to their low orbits, LEO satellites typically track a GPS satellite for a short period of time. As a consequence, those short arcs do not allow code noise and multipath to average out, potentially leading to important leveling errors. On the other hand, undifferenced ambiguity fixing for LEO satellites already has been demonstrated, and could be a viable solution to this problem.

    Evidently, more research needs to be conducted to fully assess the benefits of integer-leveled observations. Still, we think that the results shown herein are encouraging and offer potential solutions to current challenges associated with ionosphere monitoring.

    Acknowledgments

    We would like to acknowledge the help of Paul Collins from NRCan in producing Figure 4 and the financial contribution of the Natural Sciences and Engineering Research Council of Canada in supporting the second and third authors. This article is based on two conference papers: “Defining the Basis of an ‘Integer-Levelling’ Procedure for Estimating Slant Total Electron Content” presented at ION GNSS 2011 and “Ionospheric Monitoring Using ‘Integer-Levelled’ Observations” presented at ION GNSS 2012. ION GNSS 2011 and 2012 were the 24th and 25th International Technical Meetings of the Satellite Division of The Institute of Navigation, respectively. ION GNSS 2011 was held in Portland, Oregon, September 19–23, 2011, while ION GNSS 2012 was held in Nashville, Tennessee, September 17–21, 2012.


    SIMON BANVILLE is a Ph.D. candidate in the Department of Geodesy and Geomatics Engineering at the University of New Brunswick (UNB) under the supervision of Dr. Richard B. Langley. His research topic is the detection and correction of cycle slips in GNSS observations. He also works for Natural Resources Canada on real-time precise point positioning and ambiguity resolution.

    WEI ZHANG received his M.Sc. degree (2009) in space science from the School of Earth and Space Science of Peking University, China. He is currently an M.Sc.E. student in the Department of Geodesy and Geomatics Engineering at UNB under the supervision of Dr. Langley. His research topic is the assessment of three-dimensional regional ionosphere tomographic models using GNSS measurements.

    FURTHER READING

    • Authors’ Conference Papers

    “Defining the Basis of an ‘Integer-Levelling’ Procedure for Estimating Slant Total Electron Content” by S. Banville and R.B. Langley in Proceedings of ION GNSS 2011, the 24th International Technical Meeting of the Satellite Division of The Institute of Navigation, Portland, Oregon, September 19–23, 2011, pp. 2542–2551.

    “Ionospheric Monitoring Using ‘Integer-Levelled’ Observations” by S. Banville, W. Zhang, R. Ghoddousi-Fard, and R.B. Langley in Proceedings of ION GNSS 2012, the 25th International Technical Meeting of the Satellite Division of The Institute of Navigation, Nashville, Tennessee, September 17–21, 2012, pp. 3753–3761.

    • Errors in GPS-Derived Slant Total Electron Content

    “GPS Slant Total Electron Content Accuracy Using the Single Layer Model Under Different Geomagnetic Regions and Ionospheric Conditions” by C. Brunini, and F.J. Azpilicueta in Journal of Geodesy, Vol. 84, No. 5, pp. 293–304, 2010, doi: 10.1007/s00190-010-0367-5.

    “Calibration Errors on Experimental Slant Total Electron Content (TEC) Determined with GPS” by L. Ciraolo, F. Azpilicueta, C. Brunini, A. Meza, and S.M. Radicella in Journal of Geodesy, Vol. 81, No. 2, pp. 111–120, 2007, doi: 10.1007/s00190-006-0093-1.

    • Global Ionospheric Maps

    “The IGS VTEC Maps: A Reliable Source of Ionospheric Information Since 1998” by M. Hernández-Pajares, J.M. Juan, J. Sanz, R. Orus, A. Garcia-Rigo, J. Feltens, A. Komjathy, S.C. Schaer, and A. Krankowski in Journal of Geodesy, Vol. 83, No. 3–4, 2009, pp. 263–275, doi: 10.1007/s00190-008-0266-1.

    • Ionospheric Effects on GNSS

    GNSS and the Ionosphere: What’s in Store for the Next Solar Maximum” by A.B.O. Jensen and C. Mitchell in GPS World, Vol. 22, No. 2, February 2011, pp. 40–48.

    Space Weather: Monitoring the Ionosphere with GPS” by A. Coster, J. Foster, and P. Erickson in GPS World, Vol. 14, No. 5, May 2003, pp. 42–49.

    GPS, the Ionosphere, and the Solar Maximum” by R.B. Langley in GPS World, Vol. 11, No. 7, July 2000, pp. 44–49.

    Global Ionospheric Total Electron Content Mapping Using the Global Positioning System by A. Komjathy, Ph. D. dissertation, Technical Report No. 188, Department of Geodesy and Geomatics Engineering, University of New Brunswick, Fredericton, New Brunswick, Canada, 1997.

    • Decoupled Clock Model

    “Undifferenced GPS Ambiguity Resolution Using the Decoupled Clock Model and Ambiguity Datum Fixing” by P. Collins, S. Bisnath, F. Lahaye, and P. Héroux in  Navigation: Journal of The Institute of Navigation, Vol. 57, No. 2, Summer 2010, pp. 123–135.

     

  • Real-Time Extended GNSS Positioning: A New Generation of Centimeter-Accurate Networks

    A new method brings together advantages of real-time kinematic (RTK) and precise point positioning (PPP) in a technique that does not require local reference stations, while still providing the the high productivity and accuracy of RTK systems with the extended coverage area of solutions based on global satellite corrections. The real-time centimeter-level accuracy without reference-station infrastructure is suitable for many market segments — and is applicable to multi-GNSS constellations.

     

    By Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka

    Real-Time eXtended (RTX) positioning is a technology produced by combining a variety of innovative techniques, which together provide users with centimeter-level real-time position accuracy anywhere on or near the Earth’s surface. This new technique is based on the generation and delivery of precise satellite corrections (that is, orbit, clocks, and others) on a global scale, either through a satellite link or the Internet. The innovative aspects of the new solution can be divided into different categories, which directly relate to the areas that have previously limited the provision of global high-accuracy positioning:

    • Integer-level ambiguities derivation;
    • Real-time, high-accuracy satellite corrections generation;
    • Data transmission optimization;
    • Positioning technology.

    Because of various new aspects of the technique, RTX differs from both differential RTK and precise point positioning as currently understood by the general GNSS community.

    System Overview

    RTX technology is used to provide centimeter-level GNSS positioning through the CenterPoint RTX service. Figure 1 shows the general infrastructure of the system.

     

    Data from monitoring stations distributed around the globe are collected and transmitted via the Internet to operation centers at different locations. The complete operation centers (enclosed by the red dashed square) are redundant in order to assure the very high (~100 percent) availability of the system. In case it is needed, the correction stream source might change between operation centers and/or processing servers within centers. These operational changes are handled in a deterministic way by all parts of the system including the user receiver. Inside the operation centers, redundant communication servers relay the network observation data to the data processing servers, which host the network processors that produce precise orbit, clock, and observation biases valid for any place on the globe.

    After being generated, the precise satellite data are compressed in messages compliant with the CMRx format, specially developed for compact transmission of satellite information. The messages are finally routed to either a satellite uplink station or made available for Internet connection access by the users.

    The CenterPoint RTX tracking network currently consists of around 100 stations, distributed across the globe, as shown in Figure 2. The CenterPoint RTX service is currently offered in North and South America, via satellite link, as indicated in Figure 3. Today the CenterPoint RTX service has been made available globally for all those with Internet access.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 2. CenterPoint RTX tracking network distribution. (Click to enlarge.)
    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 3. CenterPoint RTX L-band satellite service coverage in the Western hemisphere.

    Limiting Factors

    To understand the limiting factors associated with global high-accuracy positioning, it is helpful to consider the simplified basic GNSS observation equations for carrier-phase and code measurements:

    Φi=ρ+c(dT−dt)+T−Ii+λi Ni,
    +Ai−ai+λi(WΦ−wΦ)+BΦ,i−bΦ,i+MΦ,i+nΦ,i
    and
    Pi=ρ+c(dT−dt)+T+Ii,
    +Ai−ai+BP,i−bP,i+MP,i+nP,i

    where:

    Φi    is the carrier-phase measurement for frequency i in meters;
    ρ    is the geometric distance between the antennas of the receiver and satellite in meters;
    c    is the speed of light constant in meters per second;
    dT    is the receiver clock error in seconds;
    dt    is the satellite clock error in meters per second;
    T    is the slant neutral atmosphere delay in meters;
    Ii    is the ionospheric delay for frequency i in meters;
    λi    is the carrier-phase wavelength for frequency i in meters;
    Ni    is the integer carrier-phase ambiguity for frequency i in cycles;
    Ai    is the combined receiver antenna offset and directional variation correction for frequency i in meters;
    ai    is the combined satellite antenna offset and directional variation correction for frequency i in meters;
    WΦ    is the receiver antenna phase wind-up effect, in cycles;
    wΦ    is the satellite antenna phase wind-up effect, in cycles;
    BΦ,i    is the carrier-phase receiver bias for frequency i in meters;
    bΦ,i    is the carrier-phase satellite bias for frequency i in meters;
    MΦ,i    is the carrier-phase multipath for frequency i in meters;
    nΦ,i    is the carrier-phase observation noise and other un-modeled effects for frequency i in meters;
    Pi    is the pseudorange measurement for frequency i in meters;
    BP,i    is the pseudorange receiver bias for frequency i in meters;
    bP,i    is the pseudorange satellite bias for frequency i in meters;
    MP,i    is the pseudorange multipath for frequency i in meters;
    nP,i    is the pseudorange observation noise and other un-modeled effects for frequency i in meters.

    The feasibility of high-accuracy absolute positioning relies on the assumption that phase and code measurements on the different frequencies or on specific observation combinations are modeled quite reliably. This ultimately means that the parameters (or certain combination of them) of the two equations given are known very precisely, that is, with an accuracy of better than a few centimeters.

    Having a global system where every component of the un-differenced GNSS observational model is well known requires advanced understanding and modeling of the involved GNSS-related effects. This is a general achievement of the RTX system.

    (An extensive section here, encompassing satellite orbits and clocks, receiver clock error, antenna phase center odeling, phase wind-up effects, neutral atmosphere delay, and ionospheric delay, appears in the online version of this article, at env-gpsworld-integration.kinsta.cloud/rtx.)

    Real-Time Network Processing

    As previously stated, the RTX system works based on precise satellite information generated at processing centers and broadcast to users. The precise information employed by the systems comprises satellite orbits, satellite clocks, satellite biases, and other auxiliary information.

    The requirements for the satellite orbits to be used in the global RTX system can be summarized as accuracy, continuity, robustness, and reliability. The satellite positions have to be accurate for obvious reasons, including the fact that orbit errors have direct impact on rover-position determination quality. Furthermore, because the RTX network process algorithms use ambiguity resolution, the reliability of the ambiguity determination is highly affected by the satellite orbits quality due to the distances between reference stations in the tracking network. The continuity requirement is put in place to avoid the need of handling observation modeling inconsistency over time for both network and rover processing.

    For the same reason, the overall system employs techniques to properly handle switches between redundant orbit-processing servers without degradation of position quality. As one would expect, network processors have to be, in general, robust against the eventuality of poor data entering the system for various reasons. The RTX network processors employ a variety of quality-control techniques to ensure that only data with the highest expected quality is used for the computation of end products.

    Finally, reliability is a very important factor for real-time orbit processing. At the current stage, the RTX real-time orbit processors are able to run for several months with virtually zero intervention from operators, while handling events such as satellites going through unhealthy periods and satellite maneuvers (during unhealthy period or not).

    There are at least two strong reasons for justifying the need of implementing and running an RTX proprietary orbit processing server. The first one is simply the need of reliably meeting the above-mentioned requirements. The second one is that from an operational perspective, the RTX system is conceived in such a way that it does not rely on any external source of information to run at its full accuracy capability. Figure 4 shows the achieved orbit errors provided by IGS ultra-rapid products during two weeks of March 2011, where IGS rapid orbit products are used as truth. The ultra-rapid orbits are evaluated using the initial portion of the predicted arc, thus making use of the most reliable part of the predicted arcs as the products become available in real-time. In that case, neither accuracy nor continuity requirements for RTX processing are completely met.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 4. IGS ultra-rapid orbit errors, as compared to IGS rapid orbit products.

    Orbit Estimation. The orbit estimation in the CenterPoint RTX system is based on a combination of a UD-factorized Kalman filter estimating satellite position, satellite velocity, troposphere states, integer ambiguities, solar radiation pressure parameters, harmonic coefficients, and Earth-orientation parameters. The prediction step in the filter uses a numerical integration of the equations of motion in connection with a dynamic force modeling. Forces considered in the approach are: the Earth’s gravity field, lunar and solar direct tides, solar radiation pressure, solid earth tides, ocean tides, and general relativity.

    In RTX orbit processing carrier phase integer ambiguities are resolved in real-time. Also, the satellite orbit states are truly estimated in real-time and continuously adapted over time to better represent the current reality. This means that the satellite positions that are evaluated by the user have prediction times of no more than a few minutes since the last orbit processing filtering update, providing negligible loss of accuracy. Figure 5 shows the orbit errors obtained from the RTX orbit processor. Similarly to the previous figure, IGS rapid orbit products are used as reference. The time span is also the same as in the previous figure. The RTX real-time orbit components have a typical overall accuracy of around 2.5 centimeters (cm), and a 3D error accuracy of around 4 cm, considering IGS rapid products as truth.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 5. RTX real-time orbit errors, as compared to IGS rapid orbit products.

    Clock Estimation. Satellite clock estimation forms an essential part of the RTX system. It plays a fundamental role on positioning performance due to a number of reasons. Satellite clocks map directly into line-of-sight observation modeling, yielding into a one-to-one error impact from clocks into GNSS observables modeling. Due to the same strong relationship, it is of fundamental importance that clocks are generated in a way to facilitate ambiguity resolution within the positioning engine. The processing speed of a clock processor is also of critical importance, due to the fact that any delay in computing satellite clocks is directly translated into correction latencies when computing real-time positions on the rover side. For that matter, one should keep in mind that regardless how late satellite corrections get to the GNSS receiver in the field, positions have to be provided to the user as soon as the rover GNSS measurements are available. Therefore latencies typically introduce errors into the final real-time position. In this article, we define real-time positioning as the computation of positions at the time when the rover observables are available, regardless of the latency of the correction stream. This is a necessary concept in order to support dynamic rover GNSS positioning.

    The RTX clock network processor was designed around the requirements discussed earlier. It computes clocks that are compatible with ambiguity resolution on the user receiver. As a matter of fact, the clock network processor itself employs ambiguity resolution for the generation of the RTX clocks. The processor architecture is based on an innovative design that allows processing data of several hundreds of reference stations, including all necessary steps such as data quality control, ambiguity resolution, and the final clock generation, within a fraction of second. The processing time of this kind of real-time network processor has to be minimized as much as possible in order to allow the processor to operate at 1 Hz, and to minimize the final correction latency at the rover end. Note that the final latency of the correction stream is a composition of three basic components: the time for the network data to arrive at the network processing server; the network processing time; and the correction transmission time to reach the final user. Figure 6 shows the typical total correction latency for the RTX system, when corrections are broadcast through a satellite link.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 6. Typical RTX correction stream latency. The dashed green line represents the latency at 50 percent (3.7 s), and the dashed red line represents the latency at 99 percent (5.6 s).

    Unlike satellite orbits, satellite clock solutions are more difficult to compare directly. This is because different clock solutions might have offsets between each other, as well as behave differently due to differences in their GNSS reference time realization process as well as in their observation modeling approaches. That said, one way of verifying the quality of satellite clocks is to quantify how well it can be used to model actual receiver observation data. This can be in general achieved by applying satellite orbit and clock correction onto GNSS data and verifying the remaining residuals. Other quantities such as receiver coordinates have to hold their correct values for the residuals to be meaningful. In this case, the combined satellite orbit and clock error are assessed, and not just the satellite clock alone. For our purposes this is perfectly fine, since this is the way orbits and clocks are employed in rover positioning as well. Figures 7 and 8 show typical combined satellite orbit and clock errors at line-of-sight for different satellites. Figure 7 shows the ionospheric-free phase modeling error for GPS satellites, while Figure 8 is for GLONASS. Note that observations of a reference satellite (highest elevation at the time of observation) were reduced from the others. This was done in order to remove the receiver clock errors from the residuals. For both GPS and GLONASS cases, the observation modeling error after using RTX orbit and clock corrections is on average at the 1 cm level, with values typically less than 2 cm. The GPS satellite with outlying behavior in the plot below was setting at that time, and the increased amplitude of the residuals is mostly due to receiver observation errors such as multipath.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 7. RTX clock quality (GPS) by means of corrected ionospheric-free phase measurements.
    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 8. RTX clock quality (GLONASS) by means of corrected ionospheric-free phase measurements.

     

    Communication and Positioning

    Once all satellite information is available, it must be compressed in a message that can be broadcast to the user in the field. The transmission of global corrections can be done in different ways, such as via Internet, in case the user has access to it, or using a satellite link. In the latter it is customary that corrections sufficient to cover the transmission satellite footprint are broadcast, rather than corrections complete enough to cover the globe. Firstly, because it is expected that users operating inside the satellite footprint will use the corrections only for that region, and secondly because bandwidth restrictions usually play a role in message design for satellite-based communication. The bandwidth restrictions not only enforce maximum bandwidth utilization below a certain limit, but also require that the utilization over time is homogeneous to ensure optimal usage of the satellite channel.

    Furthermore, satellite signals are typically susceptible to frequent message-packet losses depending on the user environment, such as when a receiver is running under canopy. To mitigate packet losses, the message must be built in such a way as to allow the rover to continue operations with minimum loss of availability. In that case not only the message design has to foresee this type of situation, but also the message decoding, usage, and positioning algorithms have to be optimized to most favorably couple with the received messages. All these factors have been taken into account in RTX system communication design. A new message format was created to carry information on satellite orbits, clocks, observation biases, and other auxiliary information. The new RTX CMRx satellite messages deliver 1-millimeter resolution for satellite orbits and clocks.

    The RTX positioning engine inherits several technological aspects from Trimble’s pre-existing RTK engine. This aspect makes the RTX positioning mode, and traditional RTK positioning modes (for example, single base, virtual reference station) easy to co-exist. Among other things, the new engine has been thoroughly tested and optimized for challenging tracking environments. In these scenarios the engine is presented with observation data collected with a high level of multipath and low signal-to-noise ratio, often producing cycle slips and gaps in the data. As previously mentioned, at the same time the correction stream also suffers packet losses and the correction data might not be completely available during certain masking conditions.

    Positioning Performance. The RTX engine delivers typical final accuracies at 1–2 cm level for horizontal positioning, and 2–4 cm for vertical, 1-sigma. The final convergence of the system is achieved in 10 to 45 minutes after receiver startup. The time to converge might depend on several aspects, including satellite geometry and multipath conditions.

    To overcome the increased convergence time as compared to traditional RTK systems, a number of features have been implemented as part of the RTX positioning engine, two of which are worthy of mention here. The Fast Restart feature allows users to power up or place the receiver at a known location and immediately obtain a converged solution. This is also applicable when users have not moved their equipment since the last RTX solution. This feature is quite valuable in agriculture applications, where the user typically does not move the tractor between RTX-steered field work activities, thus avoiding in the majority of cases the need to wait through a new convergence period before starting work, one or more days after the last system usage.

    The second feature is also related to avoiding system re-convergence. The Bridging feature, an outage recovery capability, enables the RTX positioning engine to immediately recover from a complete constellation outage with loss-of-lock during any dynamic activity. This prevents the system from entering a new convergence phase in case the receiver loses track of up to all satellites in view, coupled with outages of up to a couple of minutes, such as when running behind a tree line, or under a bridge.

    Accuracy

    Horizontal position error obtained in real time in a receiver acquiring the RTX correction data through the satellite link in North America is shown in Figure 9. The receiver was running continuously for several days, and was located in Ames, Iowa. As displayed, the horizontal RMS was 1.4 cm, with a 95 percent horizontal error of 2.4 cm. These are typical values for satellite-based RTX horizontal performance.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 9. RTX real-time horizontal positioning performance. Results obtained from a receiver operating in Ames, Iowa.

    Figure 10 shows the vertical performance for the same receiver and time period: the vertical RMS was 2.8 cm, with 95 percent vertical error of 4.4 cm.

    Time to Achieve Convergence. Convergence is directly connected to the level of productivity that can be achieved for actual field applications. In the following example a continuously powered RTX receiver was used to show an assessment of the RTX (re-)convergence capability. The receiver’s tracking of all satellites was disabled every hour by an antenna switch. Each outage lasted three minutes, during which times no GNSS satellites were tracked.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 10. RTX real-time vertical positioning performance.Results obtained from a receiver operating in AMES, Iowa, US.

    This procedure was repeated hourly for several days in order to gather enough performance runs to derive meaningful statistics. Figure 11 shows the resulting performance of this assessment. The standard cold-start re-convergence performance is indicated with blue lines, where the solid lines represent 90-percent performance and the dashed line represents 68-percent performance.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 11. RTX re-convergence performance results.

    As the figure shows, the RTX system converged to better than 5 cm horizontal error after 20 and 25 minutes for 68 percent and 90 percent of the runs, respectively. Convergence time is correlated with a number of aspects, including satellite geometry and multipath environment. Because of these variations, the claimed RTX convergence time is between 10 and 45 minutes for full accuracy achievement.

    The red lines in Figure 11 indicate performance obtained with a second receiver, connected to the same antenna, and thus subject to the exactly same GNSS signal outages. This second receiver had the Bridging functionality enabled, and thus is expected to bridge the outages and phase cycle slips without resetting the positioning solution. The red lines confirm that the desired behavior is achieved. To better visualize what happens over time in this case, Figure 12 shows a few hours of the real-time results obtained with the receiver running with the Bridging functionality activated.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 12. RTX outage recovery real-time performance.

    Figure 13 gives an example of Internet protocol (IP)-based RTX performance. This is a single run where the system converged to better than 5 cm (horizontal) in approximately 15 minutes. Figure 14 shows how the L1 ambiguities of individual satellites in view during that time converged.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 13. RTX IP-based run example.
    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 14. Example of ambiguities convergence during an RTX IP-based run.

    In these two plots, positioning convergence is, as expected, highly correlated with the ambiguities convergence to their final integer values in cycles. Note that satellites that come in after the overall solution is converged (for example, in light blue) achieve their final ambiguity values much quicker than during the position convergence phase, also as expected. The proprietary algorithms used for ambiguity resolution and validation in RTX allow the ambiguities to reliably converge to their integer values. Arbitrary integer number of cycles have been removed from the original ambiguity values to allow better simultaneous visualization of the ambiguities for several satellites.

    Optimizing the RTX system to work under different scenarios was necessary because the multipath and signal availability levels are reasonably different between running an antenna with a reference station setup and the actual user environment, where the data tracking conditions impose additional challenges on making high-accuracy positioning effective on a global basis, in a productive manner. Therefore, an extensive field test campaign was conducted during the pre-release phase of the RTX system. The next example shows RTX in-field performance for an precision agriculture application in Illinois. The setup is typical for agricultural use, with the antenna and receiver mounted on a tractor that ran for about 103 minutes. Figure 15 shows theactual track of the tractor; RTX corrections were received via satellite link.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 15. RTX tractor field test track in Illinois.

    The horizontal positioning performance for that field test can be seen Figure 16. The overall 2D RMS was 2.3 cm and the 95 percent horizontal error was 4.2 cm. Note that this position difference plot is between the RTX solution and a short-range single baseline (SBL) RTK solution providing truth. Therefore the numbers and plot actually show a combination of errors between the global RTX solution and the SBL solution to the local reference station.

    Photo: Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka
    FIGURE 16. Horizontal positioning results for a real-time RTX tractor field test in Illinois.

    Nevertheless the error magnitudes achieved lie within the same range as in the previous assessments shown here.

    Summary

    RTX positioning brings together the advantages of positioning techniques that do not require local reference stations while providing the productivity of RTK positioning. Its deployment introduces innovations in GNSS network processing, as well as advancements in the rover global positioning algorithms.

    RTX employs ambiguity resolution on a global scale for both network and rover processing, including GPS and GLONASS satellites in the solution. The delivery of this new technology is achieved through the CenterPoint RTX positioning service, capable of providing world-wide real-time centimeter-level accuracy without the direct use of a reference station infrastructure.

    A longer version of this article was presented at the 2011 ION-GNSS conference in Portland, Oregon.


    Rodrigo Leandro, Herbert Landau, Markus Nitschke, Markus Glocker, Stephan Seeger, Xiaoming Chen, Alois Deking, Mohamed Ben Tahar, Feipeng Zhang, Kendall Ferguson, Ralf Stolz, Nick Talbot, Gang Lu, Timo Allison, Markus Brandl, Victor Gomez, Wei Cao, and Adrian Kipka are members of the Trimble Engineering Team in Höhenkirchen, German

  • Pulling in All Signals

    Pulling in All Signals

    Adding GLONASS to GPS gives a total of about 50 satellites, for a significant improvement in navigation availability, reliability, robustness, and convergence time through a new multi-GNSS precise point positioning (PPP) service. System performance and field results demonstrate that there is no need to await future constellations — better performance is available now.

    By Tor Melgard, Erik Vigen, Ole Ørpen, Fugro Seastar AS, and Jon Helge Ulstein, Bourbon Offshore Norway AS

    Melgard-Open

    Precise point positioning (PPP) stands out as an optimal approach for providing global augmentation services using current and coming GNSS constellations. PPP requires fewer reference stations globally than classic differential approaches, one set of precise orbit and clock data is valid for all users everywhere, and the solution is largely unaffected by individual reference-station failures. There are always many reference stations observing the same satellite because the precise orbits and clocks are calculated from a global network of reference stations. As a result, PPP gives a highly redundant and robust position solution.

    The results presented here represent a significant step forward in PPP GNSS research and development. Using GLONASS improves the availability and reliability of the solution. The G2 system’s horizontal positioning accuracy is at the decimeter level. These results derive from increasing the number of satellites in the constellation by 60 percent, from about 30 to 50 satellites. The outcome of the development of the G2 real-time combined GPS and GLONASS PPP service represents a next-generation GNSS augmentation. Further, the later GLONASS-M satellites have improved performance and lifetime over previous GLONASS satellites, so that results will continue to improve as that constellation is replenished.

    G2 development has benefited from the close cooperation between Fugro and the European Space Operation Centre (ESOC), an establishment of the European Space Agency (ESA). ESOC has contributed its long experience and expertise on precise orbit and clock processing techniques, while the strength of Fugro is real-time positioning and navigation services.

    Based on this work, Fugro has introduced the first real-time GPS and GLONASS precise orbit and clock service. The service utilizes Fugro’s own network of dual-system GNSS reference stations to calculate precise orbits and clocks on a satellite-by-satellite basis for all 50 satellites of the two global navigation satellite systems. The system comprises about 40 dual-frequency GPS and GLONASS reference stations distributed around the world as shown in Figure 1.

    Raw GNSS measurement data for all satellites are transmitted to processing centers for calculation of the precise orbit and clock of each GPS and GLONASS satellite (Figure 3). The precise data generated is then broadcast to users via geostationary communications satellites with nearly global coverage, as shown in Figure 2.

    FIGURE 1. The G2 reference station network consists currently of 40 GNSS receivers owned and operated by Fugro.
    FIGURE 1. The G2 reference station network consists currently of 40 GNSS receivers owned and operated by Fugro.
    FIGURE 2. The G2 precise orbits and clocks are broadcast over redundant geostationary satellite beams together with the other Fugro services.
    FIGURE 2. The G2 precise orbits and clocks are broadcast over redundant geostationary satellite beams together with the other Fugro services.
    FIGURE 3. Dataflow from the reference stations to the redundant calculation servers producing precise orbits and clocks, then to the satellite uplink stations for broadcast over geostationary satellites to combined G2/GNSS user equipment.
    FIGURE 3. Dataflow from the reference stations to the redundant calculation servers producing precise orbits and clocks, then to the satellite uplink stations for broadcast over geostationary satellites to combined G2/GNSS user equipment.

    Inside the end-user equipment a dual-frequency carrier-phase-based PPP solution gives horizontal positioning accuracy at the decimeter level. The PPP calculation module is provided by Fugro and is embedded in multiple GNSS receiver manufacturers’ products as well as Fugro’s own product line.

    Like any GNSS technique, PPP is affected by satellite line-of-sight obstructions. Even the most precise orbit and clock data is useless if the user cannot track particular satellites. When satellite visibility is partially obstructed, a best possible service can be ensured by using the full range of satellites from both the GPS and GLONASS systems. This can occur during a survey of a dense urban environment, and for urban positioning in general. It can occur under heavy tree cover, when a cruise ship is in a high-sided fjord, when an offshore vessel is close to an oil rig or platform, or during ionospheric disturbances.

    The trend clearly lies towards increasing availability of GNSS satellites on orbit; many studies predict the future benefits of combining the constellations of GPS and Galileo. There is no need, however, to wait for future constellations to reap the immediate benefits of access to additional GNSS satellites. The current GLONASS constellation may not have all the features of future GNSS systems, but it is available here and now. Recently, the Russian government has proven its commitment to enhancing the GLONASS constellation. Many receiver manufacturers have also acknowledged this fact and now provide combined GPS and GLONASS receivers.

    G2 Accuracy and Statistics

    In Figure 4, time-series plots show the 3D accuracy of GPS and GLONASS G2 real-time orbits on August 14, 2009. In the comparison, final orbit data from the International GNSS Service (IGS) is used as reference. PPP positioning is mainly affected by the radial orbit error, which is significantly less than the total 3D error shown here. The 95 percent 3D accuracy for GLONASS (22 centimeters) is more than double that for GPS (10 centimeters). The graph demonstrates how this difference in this case is mainly caused by a few GLONASS satellites being less accurate. Actually, several GLONASS satellites have orbit accuracy very close to the level of GPS for real-time G2 data.

    FIGURE 4. GPS and GLONASS orbits compared to IGS final orbits.
    FIGURE 4. GPS and GLONASS orbits compared to IGS final orbits.

    Figure 5 shows the clock accuracy of the G2 real-time clocks compared to final IGS clocks. A constant bias has been removed to account for the differences in system reference time. Smaller individual clock biases for each satellite can still be observed. Small biases do not affect the final accuracy of the PPP solution, and achievable position accuracy with these clocks are significantly better than the 21-centimeter 95 percent number for GPS may indicate.

    FIGURE 5. GPS clocks compared to IGS final clocks. GLONASS clocks compared to a combined solution based on IGS plus Fugro network to calculate a best possible reference solution.
    FIGURE 5. GPS clocks compared to IGS final clocks. GLONASS clocks compared to a combined solution based on IGS plus Fugro network to calculate a best possible reference solution.

    The lower time series in Figure 5 shows the estimated GLONASS clock accuracy. Currently there is no comparable IGS product with precise GLONASS clocks. A post-processing of all available IGS plus Fugro GNSS stations has been made to establish a reference for the comparison. As shown, the GLONASS clocks are more variable, but still they are stable enough to allow for precise navigation.

    Real-Time Positioning Results

    Real-time position performance is continuously observed at the G2 operation and monitoring center in Oslo, Norway. The graph in Figure 6 shows typical G2 positioning results with the calculation engine running in dynamic mode at a fixed location for a 24-hour period. The blue lines in the north and east time series are at 20 centimeters and the scale is 61 meter. In the height graph the blue lines indicate the 30-centimeter level. The antenna is in a location with clear view of the sky, and in
    dependently calculated reference coordinates are used as reference. 1-sigma accuracy statistics on August 14 are 3, 4, and 8 centimeters in easting, northing and height respectively.

    FIGURE 6. G2 GPS-plus-GLONASS position monitoring results in Oslo on August 14, 2009.
    FIGURE 6. G2 GPS-plus-GLONASS position monitoring results in Oslo on August 14, 2009.

    Figure 7 shows GLONASS-only real-time positioning with clear view of the sky for the same day as in Figure 6 and the same antenna location. The blue line indicates the 50-centimeter level and the scale is 62 meters. For long periods, the GLONASS-only solution works quite nicely. There are, however, shorter periods with fewer than four satellites being tracked, causing the position output to stop, followed by a period of re-convergence.

    FIGURE 7. GLONASS-only real-time PPP solution on August 14, 2009 for a 24-hour period.
    FIGURE 7. GLONASS-only real-time PPP solution on August 14, 2009 for a 24-hour period.

    Figure 8 displays results from May 11, 2009, when there were slightly more satellites available and just enough to have the GLONASS-only solution running for 24 hours without resets. 1-sigma accuracy statistics for this day are 11, 9, and 16 centimeters in easting, northing, and height respectively. Considering the average number of satellites of 6.14 and periods with high DOP values, this is very promising. In early 2010, 20 GLONASS satellites should be available, and by 2011, 24 are expected. In 2010, a performance similar to or better than that of May 11 should generally be expected with the new satellites. By 2011, even better performance is believed to become the norm of GLONASS-only real-time PPP navigation.

    FIGURE 8. GLONASS-only real-time PPP solution on May 11 for a 24-hour period.
    FIGURE 8. GLONASS-only real-time PPP solution on May 11 for a 24-hour period.

    Even in some clear-view-of-sky situations, the addition of GLONASS may improve the navigation compared to GPS-only solutions. Figure 9 presents an example of such situations. Here the GPS-only solution suffers some multipath-like effects showing up, especially in the east component. Figure 10 shows the combined GPS+GLONASS solution for the same dataset. The distortion in position is practically eliminated. This is an example where adding GLONASS also improves redundancy and accuracy for navigation with clear view of the sky.

    FIGURE 9. GPS-only results for a 3-hour period where some multipath-like effects distort the postition, especially the east component.
    FIGURE 9. GPS-only results for a 3-hour period where some multipath-like effects distort the postition, especially the east component.
    FIGURE 10. Adding GLONASS improves redundancy and accuracy for the same time period as presented in Figure 9.
    FIGURE 10. Adding GLONASS improves redundancy and accuracy for the same time period as presented in Figure 9.

    The next test further analyzes the same dataset as in Figures 9 and 10 by simulating a virtual wall to the south, blocking all satellites below 40 degrees elevation. Figure 11 illustrates this virtual wall blocking both GPS and GLONASS satellites.

    FIGURE 11. GPS and GLONASS satellites blocked between the azimuths 90 and 270 degrees and elevation lower than 40 degrees, effectively establishing virtual wall to the south.
    FIGURE 11. GPS and GLONASS satellites blocked between the azimuths 90 and 270 degrees and elevation lower than 40 degrees, effectively establishing virtual wall to the south.

    With such data blockage, the GPS-only solution fails for more than 20 minutes, as seen in Figure 12, simply because the number of satellites goes below four. Then a period with slow convergence follows because of few satellites and high DOP.

    FIGURE 12. GPS-only solution fails when simulating blockage to the south.
    FIGURE 12. GPS-only solution fails when simulating blockage to the south.

    Again, adding GLONASS greatly improves the performance, as shown in Figure 13. Now a sufficient number of satellites are tracked all the time, and there is a continuous solution with the combined GPS+GLONASS throughout the time window when the GPS-only solution failed.

    FIGURE 13. GPS+GLONASS solution continues working with simulated blockage to the south.
    FIGURE 13. GPS+GLONASS solution continues working with simulated blockage to the south.

    Even with more than 30 satellites in the GPS constellation, there are situations when the satellite geometry gets poor. This occurred in northwest Europe on February 2, 2010. One of the GPS satellites (PRN17) was not available due to maintenance, and even with five to six usable GPS satellites left, the horizontal dilution of precision (HDOP) was in the range of 7–11 for about 12 minutes (10-degree elevation mask), as shown in figure 14. Such high HDOP values lie above what most user installations are configured to accept, and Fugro received feedback from clients at sea losing positioning. The G2 solution was not affected by the poor GPS geometry and kept the HDOP below 2 during this period, as shown in Figure 15.

    FIGURE 14. GPS-only performance during a period with poor GPS satellite geometry in Oslo, February 2, 2010.
    FIGURE 14. GPS-only performance during a period with poor GPS satellite geometry in Oslo, February 2, 2010.
    FIGURE 15. GPS+GLONASS performance during the same period as in Figure 14 in Oslo, February 2, 2010.
    FIGURE 15. GPS+GLONASS performance during the same period as in Figure 14 in Oslo, February 2, 2010.

    Convergence-Time Analysis

    As will be shown in the following analysis, adding GLONASS not only improves availability and robustness of the solution, it greatly improves convergence time. Real-time high-accuracy PPP solutions use carrier-phase measurements to achieve high-accuracy positioning. To do so, the carrier-phase ambiguities must be determined. This process takes a certain time depending on the observed satellite geometry and is commonly referred to as cold-start convergence time.

    Figure 16 presents a theoretical study of the expected convergence time for a GPS-only compared to a combined GPS+GLONASS solution. The lower graph shows how the expected convergence time varies significantly for a GPS-only solution throughout the day, with a peak of 75 minutes. The combined solution shows much more consistent performance, with expected 50–60 percent average improvement over GPS-only.

    FIGURE 16. Theoretical study of expected convergence time with actual GPS-and-GLONASS constellation in view of Oslo on June 26, 2009. Adding GLONASS gives a 50–60 percent theoretical convergence time improvement over GPS-only.
    FIGURE 16. Theoretical study of expected convergence time with actual GPS-and-GLONASS constellation in view of Oslo on June 26, 2009. Adding GLONASS gives a 50–60 percent theoretical convergence time improvement over GPS-only.

    We compare this theoretical study to results using G2 data produced in real time in Figure 17. A cold start is performed every 5 minutes throughout the day, for six consecutive days, giving a total of 1,728 convergence tests. The convergence criterion is the time when the 3D position arrives within 40 centimeters of the reference position and remains there for a minimum of 10 minutes. The average convergence time improvement achieved in Figure 17 is 39 percent, with some variations from day to day. On the better days, the average improvement is almost 50 percent, and close to the expected performance based on the theoretical study. On other days, there is room for further improvement. Mainly two factors are expected to contribute: more and newer GLONASS satellites, and further improvements of the G2 precise GPS and GLONASS orbit and clock product.

    FIGURE 17. Convergence results for six consecutive days starting June 24, 2009. Average convergence time of GPS-only is 27 minutes, and GPS+GLONASS is 16.5 minutes, a 39 percent improvement.
    FIGURE 17. Convergence results for six consecutive days starting June 24, 2009. Average convergence time of GPS-only is 27 minutes, and GPS+GLONASS is 16.5 minutes, a 39 percent improvement.

    Dynamic Environment Results

    Since late 2008, the G2 system has been installed on the vessel Bourbon Topaz, making frequent trips into the North Sea and back into port in Norway (see BOX).

    All positioning data from both the G2 system and the GPS-only reference systems are logged in real time on the vessel. Figure 18 gives an example plot of the relative height estimated by the G2 GPS-GLONASS solution. In the beginning of the plot, the vessel is out at sea, clearly seen as a noise in the graph that actually is the vessel’s movement in the waves. Then the vessel comes into port and the slower tidal variations are observed for the next 12 hours until the vessel again goes back out to sea.

    FIGURE 18. Relative G2 height measurements for a 24 hour period. The vessel is in harbor from 04:00 – 16:00 UTC.
    FIGURE 18. Relative G2 height measurements for a 24 hour period. The vessel is in harbor from 04:00 – 16:00 UTC.

    On June 22, 2009, an incident was recorded where the combined GPS-GLONASS G2 solution improves performance. As seen in Figure 19, there is a period starting at 10:00 UTC where the GPS-only reference systems suffer from poorer DOP values, and this is reflected both in horizontal and vertical components of the calculated position. This particular plot shows how the height drifts off by roughly 1 meter while the G2 combined solution remains unaffected for the entire period. Generally, the G2 solution also shows a smoother height than the reference system even when such problems as shown here are not present.

    FIGURE 19. Height graph from the Bourbon Topaz while in harbor on June 22, 2009. The GPS-only reference system has a period with poor DOP values while the GPS-plus-GLONASS solution is not affected.
    FIGURE 19. Height graph from the Bourbon Topaz while in harbor on June 22, 2009. The GPS-only reference system has a period with poor DOP values while the GPS-plus-GLONASS solution is not affected.

    The Bourbon Topaz carries the G2 system on operations in the North Sea, and continuously compares it with the GPS-only reference systems onboard.
    The Bourbon Topaz carries the G2 system on operations in the North Sea, and continuously compares it with the GPS-only reference systems onboard.

    Test of G2 onboard Bourbon Topaz

    The Bourbon Topaz is a modern supply vessel equipped with the latest dynamic positioning (DP) systems, operating in the North Sea. The North Sea can be a harsh environment in which to operate, and we rely on good tools for maneuvering our vessels.

    Early on, we recognized the need for stable, reliable reference systems, and our fleet is equipped with Kongsberg Seatex DPS700 system as standard. When we were asked to test the G2 onboard the Bourbon Topaz, we saw this as an opportunity to follow the development in the industry of such services. The DPS232 receiver was set up in connection with the vessel’s DPS700 system, and all information was logged and sent to Fugro Seastar.

    We often experience that the vessel has to operate close to offshore installations, which could block good reception of signals. In these cases, the G2 offers a much better and more reliable signal reception. Our experience of the quality of the G2 system is overall positive.

    User Equipment

    G2 and the other Fugro services can be received from a variety of different user equipment; both Fugro-branded or manufactured equipment and third-party equipment. In most cases the L-band receiver decoding the data from the geostationary satellites, including Fugro subscription software and position calculation module, is integrated into the same box as the GNSS receiver. Both the GNSS and geostationary satellite signals can be tracked with a single antenna.

    FIGURE 20. Receivers supporting the Fugro services. These are only examples, and not all third-party equipment manufacturers are shown. Fugro L-band data reception receiver and positioning/subscription software reside inside the receiver.
    FIGURE 20. Receivers supporting the Fugro services. These are only examples, and not all third-party equipment manufacturers are shown. Fugro L-band data reception receiver and positioning/subscription software reside inside the receiver.

    Conclusions

    Test results confirm decimeter-level position accuracy in real-time navigation with G2, the first real-time combined GPS and GLONASS PPP service. Several examples show how G2 improves availability, robustness, and convergence time compared to GPS-only positioning.

    More is better. There is no need to wait for future constellations like Galileo to reap the benefits of access to additional GNSS satellites now.

    Manufacturers

    Equipment supporting Fugro services includes receivers from Kongsberg Seatex for marine applications (Seastar), and NovAtel, Trimble, Topcon, Sokkia, Hemisphere GPS, Novariant, and Raven for land applications (Omnistar).


    Tor Melgard is R&D manager at Fugro Seastar in Oslo, Norway. He holds an M.Sc. in electrical engineering from the Norwegian Institute of Technology and wrote his thesis at the Department of Geomatics Engineering, University of Calgary.

    Erik Vigen is a senior developer at Fugro Seastar. He received his M.Sc. in Geodesy from the Norwegian Institute of Technology.

    Ole Ørpen is senior scientist at Fugro Seastar. He received his M.Sc. from the Norwegian Institute of Technology in electrical engineering.

    Jon Helge Ulstein is IT superintendent at Bourbon Offshore Norway AS, a subsidiary of the Bourbon Group, Marseilles, France.