The New Standard: Post-Processing Authenticity in North American Fieldwork

Field teams across North America are facing a quiet shift. The equipment can log positions faster than ever, but the real bottleneck has moved downstream: how do you prove the data you collected is trustworthy after you leave the site? Post-processing used to be a technical footnote — something you ran overnight to clean up noisy GPS logs. Now it's the central conversation in quality assurance meetings, and the standard for what counts as "authentic" fieldwork is tightening.

This guide is for the people who sign off on deliverables — survey managers, GIS coordinators, environmental field leads — and who need a framework to decide which post-processing approach fits their next project. We'll walk through three common options, the criteria that actually separate them in practice, and the failure modes that show up when you treat post-processing as an afterthought.

Who Must Choose, and When

Every field project that relies on GNSS data hits the same fork in the road: do you apply corrections in real time, or do you store raw observations and fix them later? The choice isn't just technical — it affects crew training, equipment budget, and the defensibility of your final dataset. And it has to be made before the first rover goes into the field, because the hardware configuration locks you into one path.

We've seen teams assume that post-processing can always fix whatever the field crew collected. That assumption is expensive. If you didn't log raw carrier-phase data at the rover, you can't reconstruct a PPK solution. If your base station ran out of battery mid-session, you lose the common clock needed for differential correction. The window for choosing the right post-processing method closes the moment you turn off the receiver.

Three groups face this decision most often:

• Survey and mapping firms working on boundary, topographic, or construction staking where positional tolerance is tight (centimeter-level) and liability matters.
• Environmental monitoring teams collecting vegetation plots, stream cross-sections, or soil sample locations — often in canopy or steep terrain where real-time corrections drop out.
• Resource management agencies (forestry, parks, watershed districts) that need defensible records for permitting or compliance, and may not have budget for high-end real-time networks.

For each group, the decision timeline is the same: you must choose before you set up the base station or configure the rover. After that, you're locked in. The rest of this guide lays out the options so you can make that call with confidence.

Why the Timeline Is Shrinking

Several trends are compressing the decision window. First, more field crews are using cellular-based RTK networks, which work well in suburbs but fail in the backcountry. Second, clients are asking for "raw data" alongside final coordinates, which means you need to log everything from the start. Third, post-processing software has become more capable but also more complex — choosing the wrong workflow can cost days of rework. The pressure to decide early has never been higher.

The Option Landscape: Three Approaches

There are more than three ways to post-process GNSS data, but in North American fieldwork the options cluster into three families. Each has a distinct trade-off between convenience, cost, and the kind of authenticity you can prove later.

Option 1: Network RTK Corrections (NRTK)

This is the most common real-time approach, but it still involves post-processing if you want to verify the solution. The rover receives corrections from a network of reference stations (like CORS or a private VRS network) over cellular or radio link. In post-processing, you can compare the rover's logged positions against the network's modeled corrections to detect blunders or multipath.

When it works: Open areas with good cell coverage, fast turnaround needed, and a subscription to a reliable network. Many municipal surveys use this because they can deliver coordinates the same day.

When it fails: In remote valleys, under dense canopy, or anytime the cell signal drops. The rover keeps logging, but without corrections the positions drift. You can't recover those gaps unless you logged raw data — and many NRTK workflows don't log raw phase data by default.

Option 2: PPK with a Local Base Station

Post-processed kinematic (PPK) is the workhorse of high-accuracy fieldwork. You set up a base station on a known point (or a point you'll later tie into a CORS station) and a rover logs raw GPS/GLONASS data. After the field session, you combine the two logs in software to compute a differential solution.

When it works: Anywhere you can set up a base station within about 15–20 km of the rover. Forest canopy, steep terrain, and urban canyons are manageable because the corrections are computed after the fact, not streamed live.

When it fails: If the base station is set up on an unverified point, or if the base and rover lose common satellite lock (e.g., due to a firmware glitch or logging error). The post-processing step also takes time — often 30 minutes to several hours for a full day's data.

Option 3: Precise Point Positioning (PPP) Post-Processing

PPP uses precise satellite orbit and clock corrections (from services like the Canadian CSRS-PPP or NASA's GDGPS) to compute positions from a single receiver's data — no base station needed. You send your rover log to a web service or run desktop software, and it returns a corrected position, often with convergence times of 15–45 minutes.

When it works: Remote areas where you can't set up a base station, or for projects with only a few points that need high accuracy. It's also a great backup if your base station data is corrupted.

When it fails: PPP requires a stable, long observation session — typically 30+ minutes per point — which is impractical for kinematic surveys. It also doesn't handle ionospheric disturbances as well as differential methods, and the accuracy degrades at high latitudes.

Comparison Criteria Readers Should Use

Choosing between these methods isn't about which one is "best" — it's about which one matches your project's constraints. We recommend evaluating on four criteria: reliability in the field environment, cost per point, turnaround time, and auditability. Each matters differently depending on who you're working for.

Reliability in the Field Environment

This is the first filter. If your project area has no cell service, NRTK is off the table. If you're surveying under heavy canopy, PPP won't converge quickly enough for a walking pace. If you're in a remote valley with no suitable base station location, PPK becomes difficult. Map your field site's constraints before you choose the method — not after.

Cost Per Point

NRTK subscriptions cost a few thousand dollars per year per rover. PPK requires a base station receiver (one-time cost $2,000–$10,000) and post-processing software. PPP is often free for limited use (e.g., Natural Resources Canada's CSRS-PPP) or pay-per-point for commercial services. But the hidden cost is crew time: PPK requires someone to set up and monitor the base station, while NRTK and PPP can be one-person operations.

Turnaround Time

If the client needs coordinates before you leave the site, NRTK is the only option that can deliver real-time results (though you may still want to post-process for quality control). PPK typically adds a few hours to a day. PPP adds at least a day for convergence and download. For emergency response or construction staking, speed often overrides other criteria.

Auditability

This is where the authenticity standard comes in. Auditability means you can reconstruct the solution and prove it's correct. PPK with a base station gives you the most audit trail: raw logs from both receivers, a known base point, and a repeatable processing report. NRTK logs are harder to audit because you rely on the network's modeled corrections, which you may not have access to later. PPP logs are auditable if you keep the input RINEX file and the service's output report, but you can't re-run the solution with different parameters.

For regulatory or legal work (boundary surveys, wetland delineation, archaeological site records), auditability should be your top criterion. For internal mapping or reconnaissance, turnaround time may matter more.

Trade-Offs in Practice: A Structured Comparison

The table below summarizes the key trade-offs across the three methods. Use it as a quick reference when you're briefing your team or writing a scope of work.

No single method wins across all criteria. The table should help you identify which trade-offs you can accept and which are deal-breakers for your project.

Composite Scenario: Forest Inventory in British Columbia

A field crew needs to map 200 sample plots in coastal rainforest. Canopy is dense, cell coverage is nonexistent, and the client requires 5 cm horizontal accuracy for compliance with a provincial reporting standard. The team has two survey-grade rovers and one base station. PPK is the obvious choice here. They set up the base station on a benchmark from the provincial control network (verified beforehand), log raw data at both base and rover, and process the data each evening in the office. The bottleneck is battery life: the base station must run for 10 hours without interruption. They bring a spare battery and a solar panel. Post-processing takes about two hours per day, but the audit trail is clean. If they had chosen NRTK, they would have lost most of the day's data when the cell signal failed.

Implementation Path After the Choice

Once you've selected a method, the next step is to build a workflow that ensures consistency across the project. This is where many teams stumble — they choose the right approach but fail to standardize the steps, leading to gaps in the data that undermine authenticity.

Step 1: Define Your Coordinate Reference Frame

Before you go to the field, decide which coordinate system and geoid model you'll use for final deliverables. This sounds basic, but we've seen projects where the base station was set to NAD83(CSRS) while the rover was set to WGS84, and the post-processing software didn't flag the mismatch. Document the reference frame in your metadata and stick to it. If you're working across jurisdictions (e.g., a project spanning the U.S.-Canada border), be explicit about which official transformation you'll apply.

Step 2: Create a Field Log Template

For every base station setup, record the antenna height (measured three times), the point ID, the start and end times, and any obstructions. For rovers, log the observation duration per point and any known issues (e.g., "under tree canopy", "walked past metal shed"). This metadata is as important as the coordinates themselves for post-processing quality control.

Step 3: Establish a Processing Workflow

Write down the exact steps you'll follow in your post-processing software: which settings for elevation mask, which ephemeris (broadcast vs. precise), how you handle cycle slips, and what threshold you use for accepting a fix (e.g., ratio > 3.0). Run the same workflow on every session. If you change settings mid-project, document why. This consistency is what makes your dataset defensible.

Step 4: Build in a Validation Step

Don't trust the post-processed coordinates blindly. Compare a subset of points against independent checks — a known benchmark, a second base station, or a quick PPP solution for a few key points. If the differences exceed your tolerance (e.g., 3 cm horizontal), investigate the source before proceeding. Many teams skip this step to save time, but it's the only way to catch systematic errors like a mis-measured antenna height or a base station coordinate typo.

Step 5: Archive Raw Data

Keep the original receiver files (.T02, .RINEX, .raw) even after you deliver the final coordinates. Clients and regulators are increasingly asking for raw data to verify results. If you delete the raw files after processing, you lose the ability to re-run the solution if a question arises later. Set a retention policy — at least until the project is closed out and any warranty period expires.

Risks If You Choose Wrong or Skip Steps

The consequences of a poor post-processing decision range from wasted field time to legal liability. Here are the most common failure modes we see in North American fieldwork.

Risk 1: Unrecoverable Gaps in the Dataset

If you chose NRTK and the cell signal dropped for an hour, you have positions from that hour but no way to improve them. You can't add corrections retroactively because the rover didn't log raw phase data. The only fix is to revisit the site, which may be impossible if the crew has moved on or the season has changed. This is the most common regret we hear from teams who prioritized speed over robustness.

Risk 2: Base Station Blunders That Propagate to Every Point

If the base station is set up on a point with an incorrect coordinate — even by a few centimeters — every rover point inherits that error. PPK doesn't magically fix a bad base coordinate. The error is systematic and won't show up in internal consistency checks (all points will look good relative to each other). You only catch it when you compare against an independent control point. We've seen projects where hundreds of points had to be re-surveyed because the base station was set up on a mislabeled monument.

Risk 3: Coordinate System Mismatches That Don't Surface Until Delivery

This is especially common in cross-border projects or when using different post-processing software. One team processed their data in UTM zone 10 but delivered it in UTM zone 11 without a proper transformation. The shift was 30 meters. The client didn't notice until they overlaid the data on a map. By then, the field crew was already on another project. Fixing it required reprocessing every point, which took days.

Risk 4: Over-Reliance on Automated Processing

Post-processing software is good at finding a solution, but it doesn't always tell you when the solution is weak. A low ratio value or a high RMS may be flagged, but if the operator doesn't check those flags, bad data gets through. We've seen automated batch processing accept solutions with cycle slips that degraded accuracy by 10 cm. The software didn't reject them because the user had set the acceptance threshold too low. The lesson: always review the quality metrics for each point, not just the final coordinates.

Risk 5: Losing the Audit Trail

If you don't archive raw data and processing reports, you have no way to prove that your coordinates are correct if a question arises months later. This is especially risky for projects that feed into regulatory permits or legal boundaries. Without an audit trail, the data is only as trustworthy as the person who processed it — and that's not a defensible standard.

Common Questions About Post-Processing Authenticity

Q: Can I mix methods within one project — say, use NRTK in open areas and PPK in the woods?

Yes, but you need to document the switch clearly in your metadata and be aware that the two methods have different error profiles. If you combine them in the same dataset, note which points came from which method. For most projects, consistency is preferable; mixing methods can complicate the audit trail.

Q: How long should I log at a base station for PPK?

Log at least 30 minutes of static data at the base station before and after the rover session. This gives you enough data to resolve ambiguities and check for clock drift. If the base station is on a known control point, you can log continuously for the whole day. If it's on a new point, you'll need a longer session (2–4 hours) to compute a reliable position for the base itself.

Q: What's the best way to check base station coordinates?

If possible, set up the base station on a published benchmark from a national or state/provincial control network. If that's not feasible, occupy a temporary point and post-process it against a nearby CORS station using PPP or a static differential solution. Do this check before you start the rover survey, not after.

Q: Is PPP accurate enough for boundary surveys?

In most jurisdictions, boundary surveys require a higher standard of accuracy and traceability than PPP can provide. PPP is useful for reconnaissance or for checking a few points, but for legal boundaries, a differential solution (PPK or static) with a known base station is typically required. Check your local regulations.

Q: How do I handle canopy in post-processing?

Canopy reduces the number of satellites visible and increases multipath. For PPK, use a high-elevation mask (15°) to exclude noisy low-elevation satellites, and log for longer at each point (e.g., 30 seconds instead of 10). Some post-processing software has a "forest" mode that adjusts the solution for canopy. Test it on a known point before relying on it.

Q: What's the most common mistake in post-processing?

Mis-measuring the antenna height. This single error accounts for more accuracy failures than any other. Always measure from the ground mark to the antenna reference point (ARP) using a tape, and record the measurement in the field log. If you use a range pole, verify that the pole height is set correctly. A 2 cm error in antenna height becomes a 2 cm vertical error in every point.

Recommendation Recap Without Hype

After reviewing the options, criteria, and risks, here's a straightforward set of recommendations for common field scenarios. These aren't absolute rules — every project has unique constraints — but they reflect what we've seen work consistently in practice.

1. For legal or regulatory surveys: Use PPK with a base station set up on a verified control point. Log raw data at both ends, process with a documented workflow, and archive everything. This gives you the strongest audit trail.
2. For high-density mapping in open terrain with good cell coverage: NRTK is efficient and fast, but log raw data in the rover as a backup. If the network goes down, you can still process the data using PPK or PPP later.
3. For remote, low-density point collection (e.g., soil samples, wildlife sightings): PPP is a practical choice if you can spend 30+ minutes at each point. It eliminates the need for a base station and works anywhere with a clear sky.
4. For projects with mixed conditions: Default to PPK. It's the most flexible method and gives you the most control over quality. The extra time in the office is worth the confidence you gain.
5. Always include a validation step. Check at least 5% of your points against an independent source — a known benchmark, a second base station, or a quick PPP solution. If the differences are within tolerance, you can deliver with confidence. If not, investigate before you hand over the data.

The new standard for post-processing authenticity isn't about using the fanciest equipment or the latest software. It's about making deliberate choices before you go to the field, documenting every step, and building a dataset that can stand up to scrutiny. That's what separates fieldwork that's merely fast from fieldwork that's truly trustworthy.