Compare
UBX vs RINEX: receiver logs and observation exchange
UBX is u-blox-specific binary communication and logging. RINEX is text exchange for observations, navigation and other data.
Which format should you choose?
Keep UBX for receiver-specific records and use RINEX for supported observations across analysis tools; retain originals.
Good fit for UBX
Store and inspect u-blox receiver messages
- Examine recorded positions, status or available raw observations
Good fit for RINEX
Exchanging GNSS receiver observations, navigation messages, and meteorological data between analysis tools · Post-processing ranging and phase observations from multiple satellite systems
- Declaring version, satellite systems, observation codes, and time system in a header
- Sharing GNSS data across receiver manufacturers
Basic information
| Field | UBX | RINEX |
|---|---|---|
| Extension | .ubx | .rnx |
| MIME type | text/plain | |
| Common uses | Store and inspect u-blox receiver messages | Exchanging GNSS receiver observations, navigation messages, and meteorological data between analysis tools · Post-processing ranging and phase observations from multiple satellite systems |
| How to open | Use a compatible decoder to check length, checksum and class/ID. u-center 2 playback requires conversion to .uc2; retain the original .ubx. | Use geodetic or GNSS analysis software that supports the file's version, such as RINEX 4.02. Check RINEX VERSION / TYPE, file type, satellite system, SYS / # / OBS TYPES, start epoch and time system, and station and antenna information. For navigation files, also verify message system and version. Open or decompress compressed files with a compatible tool. |
| Export or convert | RINEX conversion needs supported observation/navigation messages and a decoder. Check for messages such as UBX-RXM-RAWX, observation codes, time and gaps. Position solutions cannot reconstruct original raw observations. | When converting a receiver-specific format to RINEX, verify observation codes, frequency bands, time system, sampling interval, antenna and station details, and whether corrections or cycle-slip records are retained. Producing a GPX track from RINEX requires positioning analysis; it is not a simple file-format conversion. |
Choose by use case
Examine recorded positions, status or available raw observations
Store and inspect u-blox receiver messages
UBXDeclaring version, satellite systems, observation codes, and time system in a header
Exchanging GNSS receiver observations, navigation messages, and meteorological data between analysis tools · Post-processing ranging and phase observations from multiple satellite systems
RINEXSharing GNSS data across receiver manufacturers
Exchanging GNSS receiver observations, navigation messages, and meteorological data between analysis tools · Post-processing ranging and phase observations from multiple satellite systems
RINEXKey point 1
UBX content may include position solutions, status or raw observations, depending on recorded messages.
More on the differencesKey point 2
RINEX uses observation codes or navigation records according to file type and version.
More on the differencesMore on the differences
Check model, firmware, protocol version and output settings; verify needed observations exist before conversion.
- Match supported messages such as UBX-RXM-RAWX, time, satellite/signal IDs and validity flags against converted observations.
- Not all receiver status and settings fit into RINEX. Record exclusions and gaps, plus station/antenna metadata needed separately.
Frequently asked questions
Can position-only UBX produce RINEX observations?
It cannot reconstruct original code and carrier-phase observations. A supported log with the required raw observations is needed.