Understanding RW5 Format and Raw Data Expectations in GNSS RTK Workflows
A recurring question from users working with SurPad and other GNSS RTK software concerns the RW5 file format. This typically arises when a local authority, client, or legacy workflow requires deliverables in .rw5 format.
To avoid confusion, it is important to understand what RW5 actually represents and how it differs from standard GNSS RTK data outputs.
What is RW5?
RW5 (Trimble Raw Data format) is a proprietary Trimble file format designed to store raw field observations. It is commonly associated with Trimble instruments and software ecosystems such as Trimble Access and Trimble Business Center (TBC).
RW5 files may contain:
In essence, RW5 is not merely a coordinate file — it is a structured measurement journal.
Why RW5 is Rare in GNSS RTK Rover Workflows
Modern GNSS RTK rovers typically operate differently from traditional total station workflows. An RTK rover primarily computes coordinates in real time using satellite observations and correction data (e.g., NTRIP).
As a result:
For this reason, most Android-based GNSS RTK applications — including SurPad — do not natively export RW5 files. RW5 remains tightly coupled to Trimble-oriented measurement architectures.
What Can Be Exported Instead
Although RW5 export is generally not available, SurPad and similar software can provide the data most projects actually require:
In many practical cases, these outputs fully satisfy technical and regulatory requirements, even when RW5 was originally specified.
Raw Data Quality Reports
Requests for “raw data quality per point” are usually achievable. Typical GNSS RTK quality information may include:
These reports are standard in GNSS RTK workflows and are independent of RW5.
Key Takeaway
RW5 is not a universal industry standard but a Trimble-specific format rooted in legacy measurement models. GNSS RTK rover workflows are built around real-time positioning rather than observation journaling.
When compatibility questions arise, it is often more productive to clarify the required deliverables (coordinates, accuracy reports, metadata) instead of focusing strictly on RW5 itself.
Understanding this distinction can prevent unnecessary technical dead ends and simplify project execution.