Title: Do We Need Ambiguity Resolution in Multi-GNSS PPP for Accuracy or Integrity?
Author(s): G. Seepersad, J. Aggrey and S. Bisnath
Published in: Proceedings of the 30th International Technical Meeting of The Satellite Division of the Institute of Navigation (ION GNSS+ 2017)
September 25 - 29, 2017
Oregon Convention Center
Portland, Oregon
Pages: 2204 - 2218
Cite this article: Seepersad, G., Aggrey, J., Bisnath, S., "Do We Need Ambiguity Resolution in Multi-GNSS PPP for Accuracy or Integrity?," Proceedings of the 30th International Technical Meeting of The Satellite Division of the Institute of Navigation (ION GNSS+ 2017), Portland, Oregon, September 2017, pp. 2204-2218.
Full Paper: ION Members/Non-Members: 1 Download Credit
Sign In
Abstract: With the advent of quad-constellation, triple-frequency and external atmospheric constraints being provided to the PPP user, the novelty and focus of this paper is in the quest to answer the question: Do we really need ambiguity resolution in multi-GNSS PPP for accuracy or for integrity? To address the first component of the question, which is also an area of research that has lacked attention, is an examination of the significance between the float and ambiguity resolved PPP user solution. Is the improvement significant enough for applications such as precision agriculture and autonomous vehicles to justify the additional cost and computational complexity of producing a multi-GNSS PPP-AR solution? Results consist of solution analysis of convergence time (time to a pre-defined performance level), position precision (repeatability), position accuracy (solution error with respect to analysis centre’s weekly Site Independent Exchange (SINEX) solution) and residual analysis. Pre-defined user thresholds were selected based on specifications for lane navigation and machine guidance for agriculture. A novel component within the realm of PPP-AR is the analysis of ambiguity resolution as a metric to examine the integrity of the user solution. The role of ambiguity resolution relies primarily on what are the user specifications. If the user specifications are at the few cm-level, ambiguity resolution is an asset, as it improves convergence and solution stability. Whereas, if the user’s specification is at the few dm-level, ambiguity resolution offers limited improvement over the float solution. If the user has the resources to perform ambiguity resolution, even when the specifications are at the few dm-level, it should be utilized. To have a high probability of correctly resolving the integer ambiguities, the residual measurement error should be less than a quarter of a wavelength. Having a successfully resolved and validated solution can indicate to user the solution strength and reliability.