Legacy GNSS software may require GNSS measurements in old RINEX2 format while modern CORS networks usually provide data in RINEX3 or even RINEX4 format. KernelSAT RTOOLS service may help to accurately convert RINEX3 or RINEX4 into legacy RINEX2 both raw measurements and navigation data (ephemeris).

TOPAZ PPK long baseline processing (182 km) in static mode. Estimation of TOPAZ positions accuracy vs reference coordinates computed by Bernese GNSS Software.

Example of CORS reference station processing in PPP positioning mode by PENTAP. Comparison of resulted positions to reference coordinates computed by CODE (Center for Orbit Determination in Europe) i.e. Bernese GNSS Software.

BIN2TXT service may help to convert binary UBLOX UBX messages (like [UBX-NAV-PVT] or [UBX-RXM-RAWX]) into ASCII text form for deep messages and fields analysis.

Precise Point Positioning (PPP) Post-Processing of GNSS raw data with precise SP3 orbits and clocks by PENTAP service.

Example of kinematic GNSS raw data post-processing. Rover file is of UBLOX UBX format, base - RTCM3 corrections.

Ste-by-step illustrated example of static GNSS raw data PPK post-processing with help of TOPAZ service.

Few practical examples of how to be ensure UBLOX UBX log can be converted to RINEX.

RTools servicve may help to convert UBLOX UBX file to RINEX observables (OBS) file.

RTools online service may be used for converting Hatanaka Compressed RINEX (CRX) to standard RINEX of required version. The article describes in details how to do it.

Example of how to convert RTCM3 corrections into RINEX format.

Sometimes, one may have in hands set of RINEX observables files (say 1h files) while one single "composite" file is needed. The article describes in details how to do it w/ help of RINEX Tools service.

Network RTK (VRS, MAC or FKP) may provide better RTK performance (accuracy, reliability, TTFF) being compared to single physical station. Sometimes it is needed to check that coming corrections are actually from Network RTK engine, get idea where the nearest physical station is.

Why RTK rover can't get FIX or it is too long and unstable? RTCM3 corrections coming from base is one of the key factors to be checked. WAY service can decode and analyze RTCM3 corrections. Besides standard statistic information about detected messages, tracked GNSS / SVs / Signals on base, WAY may warn you about obvious issues w/ corrections. Like absent of base position or base ID change or to low SNR on base.

Quite often one may need to get quick statistic of GNSS data file - what format / protocol is it? What messages are inside? How many w/ bad / good CRC? What is the average position (just to be aware where the file was collected) etc.