Gnss
GNSS field work: precision budgets, OPUS sessions, and antenna heights.
GNSS field work: the precision a receiver's millimeters-plus-ppm specification promises over your baseline, planning an NGS OPUS session and naming its RINEX file, reducing a slant antenna height to the antenna reference point, and site localization that fits local coordinates to the grid. It is for surveyors running RTK, PPK, and static sessions. Start with the RTK and PPK precision budget. A slant height measured to the edge of the antenna is not the vertical height to the reference point, so reduce it before processing.
I want to estimate RTK or PPK precision from a receiver's spec
- RTK and PPK precision budget
The precision a receiver's a mm + b ppm specification promises over your baseline, horizontal and vertical, scaled to a confidence level and compared with your target.
I want to plan an OPUS session and name the RINEX file
- OPUS session planning
Which NGS OPUS processing a planned GNSS session gets (rapid-static or static), whether its length qualifies, and the RINEX file name for the day.
I want to turn a slant antenna height into the vertical to the ARP
- Antenna height from a slant measurement
The vertical height to the antenna reference point from a slant height measured to the edge of the antenna, its radius, and the mark-to-ARP offset.
I want to fit local site coordinates to the grid through control points
- Site localization (calibration)
Fits local site coordinates to grid coordinates through control points seen in both, by a similarity (scale, rotation, shift) or affine transform, with residuals, their root mean square, and a check for a feet-and-meters mix-up.