Setting Up Repeatable Base Stations: OPUS, NTRIP, and QGIS Cross-Checks

Why Base Station Accuracy Matters

A base station provides real-time corrections to your drone's GNSS receiver during flight. If the base station's coordinates are wrong, the drone's position data shifts by the same amount — and that error propagates through every orthophoto, digital surface model, and contour line you produce.

For projects that require repeat visits — such as construction progress monitoring, stockpile volume calculations, or annual site surveys — consistent base station positioning is even more critical. A shift of a few centimeters between visits can make it appear that earth has moved when it hasn't, or worse, mask actual movement that needs attention.

Method 1: OPUS Solution for Primary Positioning

The National Oceanic and Atmospheric Administration's Online Positioning User Service (OPUS) provides free access to high-accuracy coordinates tied to the National Spatial Reference System (NSRS). It uses the same software that computes coordinates for the nation's geodetic control marks and the NOAA CORS Network.

The workflow:

1. Set up your GNSS receiver (such as an Emlid RS3 or RS2+) over your chosen base station location
2. Log raw GNSS data for 4–5 hours — longer sessions produce more reliable solutions
3. Upload the log file to OPUS via the NOAA website
4. OPUS processes your data against nearby CORS stations and returns a precise coordinate solution

A 4–5 hour OPUS session typically yields centimeter-level accuracy in the horizontal and a few centimeters in the vertical. This becomes your reference position for the base station.

Method 2: RTK Observation and PPK Cross-Check

While OPUS provides the most reliable position, it requires several hours of data collection and internet access to submit. For field verification, a faster cross-check method is useful.

Short observation method: Take a 2-minute RTK observation at the same point using your rover receiver connected to a network RTK service. This gives you a quick position check that, while less accurate than a full OPUS solution, can reveal gross errors before you start flying.

Post-processed kinematic (PPK) correction: If a surveyor's GNSS data becomes available after your initial setup — for example, if a surveyor visits the site later with their own equipment — you can PPK-correct your base station log against a nearby CORS station using software like Emlid Studio. This provides an independent check on your base station position.

The DMA group has observed that a surveyor's GNSS receiver may show 3–4 cm vertical difference from an initial RTK reading. When surveyor data becomes available, PPK correction can resolve this discrepancy and improve overall accuracy.

Method 3: QGIS Cross-Check with Ground Control Points

Once you have your base station position established, the next step is to validate that your mapping software is using it correctly. This is where QGIS comes in.

The cross-check workflow:

1. Process your flight data in your photogrammetry software (Pix4Dmatic, Pix4Dsurvey, etc.)
2. Export the ground control point (GCP) coordinates from your processing report
3. Import the GCP coordinates into QGIS alongside a reference layer — such as a known-good orthophoto or survey-grade point data
4. Compare the positions visually and measure any discrepancies

Minor discrepancies between your GCPs and the reference layer confirm that your coordinate system alignment is correct. If you see larger offsets, it may indicate a base station position error, a coordinate system mismatch, or a GCP marking issue.

Best practice for GCP placement: Limit manual GCP marks to 10–12 points per project. Adding more points beyond this threshold tends to increase error rather than improve accuracy, as the additional points introduce more opportunities for marking inconsistencies.

Establishing Permanent Base Station Locations

For sites that require recurring scans — such as annual construction progress monitoring or environmental change detection — consider establishing permanent, secure base station locations. A D60 nail driven at a secluded location on the site, marked with a whisker or flag, provides a repeatable point that can be reoccupied on every visit.

This approach ensures long-term data repeatability. When you return to the same site months or years later, you set up over the same physical point, use the same OPUS-derived coordinates, and eliminate the variable of base station repositioning from your data comparison.

Putting It All Together

A reliable base station workflow combines all three methods:

1. Cook your base station point with a 4–5 hour OPUS session for the most reliable position
2. Cross-check in the field with a 2-minute RTK observation and, when available, PPK correction against a CORS station
3. Validate in QGIS by importing GCP coordinates and comparing against a reference layer
4. Document and secure your base station location for repeat visits

This three-method approach catches errors at each stage — from the initial OPUS solution through field verification to final software validation. It takes more time upfront than simply accepting a single RTK fix, but it prevents the kind of systematic errors that can waste hours of processing time and erode client confidence.

References

NOAA OPUS — Online Positioning User Service

Emlid Reach RS3 — OPUS Workflow Documentation

Post-processing Emlid GNSS Data with OPUS Corrections — UI Drone Lab

Local Base Station vs Network RTK — Heliguy

RTK Base Station in 2026: Is It Still Worth the Investment? — RTK Data