Post-Processing Differential Correction (PPDC) with CORS Data

What Is Post-Processing Differential Correction?

Every GNSS receiver collects raw range measurements that contain errors from atmospheric delay, satellite clock drift, and multipath reflections. Autonomous positioning—where your receiver works alone—accepts all those errors and typically yields horizontal accuracy in the range of a few meters under open-sky conditions. Post-Processing Differential Correction (PPDC) improves that result dramatically by comparing your rover's raw observations against simultaneous observations recorded at a fixed, precisely known base station. Because both sites see the same satellite signals at the same moment, most error sources cancel out through differencing, leaving a position that can approach centimeter-level accuracy depending on baseline length and observation time.

The CORS Network and NGS OPUS

The Continuously Operating Reference Station (CORS) network, managed by the National Geodetic Survey (NGS), is a nationwide system of permanently installed, survey-grade GNSS receivers that log observations continuously and archive the data in standard RINEX format. Because CORS stations occupy precisely known positions on the National Spatial Reference System (NSRS), they are ideal base stations for PPDC work.

NGS OPUS (Online Positioning User Service) is a free, web-based tool that accepts a RINEX observation file from your rover, automatically selects the three or more nearest CORS stations, computes a differential correction against each, and returns a position solution with accuracy statistics. OPUS removes the need to own or set up your own base station, making high-accuracy positioning accessible even to small survey firms and students.

OPUS offers two processing modes:

• OPUS Static — for observation files typically 15 minutes or longer collected with a stationary receiver; returns latitude, longitude, ellipsoid height, and NAD 83 / NAVD 88 (Geoid model) values.
• OPUS Rapid Static — designed for shorter occupation times, generally supporting dual-frequency receivers and observations of sufficient satellite geometry.

Always check the current NGS OPUS documentation for minimum occupation duration and receiver requirements, as these specifications are updated periodically.

RINEX Format

Receiver Independent Exchange Format (RINEX) is the universally accepted ASCII file format for raw GNSS observations. Most survey-grade and mapping-grade receivers can export RINEX directly; some require proprietary conversion software supplied by the manufacturer. A valid RINEX observation file contains a header section (receiver type, antenna height, approximate position, observation types) followed by time-tagged pseudorange and carrier-phase measurements for each tracked satellite. OPUS will reject files with missing or malformed headers, so verifying the header before submission saves time.

Reading the OPUS Solution Report

OPUS returns a plain-text solution report. Key fields you must record and interpret include:

• Adjusted position — latitude, longitude, and ellipsoid height in NAD 83, plus orthometric height if a geoid model is applied.
• Peak-to-peak errors — the spread between the highest and lowest position values computed from the individual CORS baselines; a quality indicator for how consistent the corrections are.
• RMS (Root Mean Square) errors — a statistical measure of the overall fit; lower RMS indicates a more reliable solution. RMS values are reported separately for north, east, and up components.
• Reference stations used — names and distances to the CORS stations. Longer baselines generally introduce more atmospheric modeling error; baseline lengths under roughly 300 km are recommended for standard OPUS Static work.
• Number of observations used vs. rejected — a high rejection rate may indicate multipath, receiver issues, or an obstructed sky.

Comparing Positioning Methods

This lab compares three positioning methods for the same point:

1. Autonomous GNSS — receiver only, no correction applied.

2. SBAS (Satellite-Based Augmentation System) — real-time broadcast corrections from geostationary satellites (e.g., WAAS in North America), typically improving accuracy to sub-meter levels.

3. OPUS post-processed — differential correction against CORS, typically yielding centimeter-level accuracy for static observations.

The OPUS result is treated as the best available reference for comparison. You calculate the horizontal distance between each other method's reported position and the OPUS position to quantify the improvement.

Selecting the Right Method for the Application

Accuracy requirements drive method selection:

• Autonomous GNSS is appropriate for general navigation, asset inventory with meter-level tolerances, and preliminary reconnaissance.
• SBAS suits many GIS data collection tasks where sub-meter accuracy is acceptable, such as utility mapping or environmental sampling.
• PPDC / OPUS is appropriate for control point establishment, boundary surveys, construction stakeout, and any task requiring horizontal accuracy better than about 0.1 m.

Safety and Professional Responsibilities

Data integrity is this lab's primary safety concern. Submitting corrupted or incorrectly labeled files can produce a false position that later propagates into legal surveys or construction plans. Always verify the antenna height entered in the RINEX header before submission—an incorrect antenna height directly corrupts the height solution. Protect downloaded CORS data and OPUS reports by saving them to a secure, backed-up directory; treat them as legal project records. When collecting field data used in this lab, follow all site-specific PPE requirements (high-visibility vest near roadways, appropriate footwear on uneven terrain) and follow your school's field safety protocol.