Editor's Points: Positioning with Confidence
In this issue, William Henning, PLS, senior geodesist for NGS, tackles the first of seven best practices for RTK positioning, which NGS has dubbed “The Seven C’s:” checking, communication, conditions, constraints, coordinates, collection and confidence. Although his column will focus primarily on single-base RTK, Henning is also hard at work leading a group that is developing guidelines for using real-time networks. Chief among the recommendations:
- Know the networks. Users should be familiar with the different GNSS manufacturers’ RTN solutions, including non-physical (virtual) reference stations, master-auxiliary types and reverse processing concepts.
- Record the metadata. These include details such as the RTN coordinate basis (datum, adjustment, epoch), any calibrations performed, hardware, firmware and software versions, data collection criteria (number of epochs of data, intervals used, DOP settings, minimum satellites present during collection), conditions such as local weather and space weather, possible multipath conditions, and obstructions.
- Understand the concepts of precision (a measure of alignment to the RTN or to the constrained passive marks as a local projection) and accuracy (the alignment to the national datums) in differential GNSS positioning. NGS encourages all RTNs to align to the national datums at certain levels horizontally and vertically using the national CORS network as truth and to produce positions that are consistent at high accuracy from overlapping or abutting RTNs. NGS also encourages all RTNs to provide their data in formats that all users can use regardless of their GNSS hardware.
- Follow the NGS best practices for GNSS field locations--i.e., “The Seven C’s”--which are the same for networks as they are for single-base RTK.
By following the guidelines, users should be able to achieve GNSS RTN positioning with high accuracy at a 95 percent confidence level. It still won’t be fool-proof--but it’s getting closer.
Share your thoughts on this column here or www.rpls.com. To contact the editor, send an e-mail to email@example.com.