RTKLIB ver. 2.4.

1 Manual

2011‐06‐10

Contents

1 Overview .............................................................................................................................................................. 1

2 System Requirement ........................................................................................................................................... 3

3 Instructions .......................................................................................................................................................... 4

3.1 Installation/Uninstallation.......................................................................................................................... 4

3.2 Real‐time Positioning with RTKNAVI ...................................................................................................... 6

3.3 Configure Input, Output and Log Streams for RTKNAVI ................................................................... 19

3.4 Post‐Processing Analysis with RTKPOST .............................................................................................. 25

3.5 Configure Positioning Options for RTKNAVI and RTKPOST ............................................................ 29

3.6 Convert Receiver Raw Data to RINEX with RTKCONV ..................................................................... 42

3.7 View and Plot Solutions and Observation Data with RTKPLOT ........................................................ 46

3.8 NTRIP Source Table Browser ................................................................................................................... 58

3.9 Use Console APs of RTKLIB .................................................................................................................... 60

4 Develop and Link user AP with RTKLIB ....................................................................................................... 61

Appendix A Console AP Commands .................................................................................................................... 62

A.1 RTKRCV ..................................................................................................................................................... 62

A.2 RNX2RTKP................................................................................................................................................. 65

A.3 POS2KML ................................................................................................................................................... 67

A.4 CONVBIN .................................................................................................................................................. 68

A.5 STR2STR ..................................................................................................................................................... 71

Appendix B File Formats......................................................................................................................................... 72

B.1 Positioning Solution File........................................................................................................................... 72

B.2 SBAS Log File ............................................................................................................................................. 75

B.3 Solution Status File .................................................................................................................................... 76

B.4 Configuration File ..................................................................................................................................... 78

Appendix C Library APIs (Application Program Interfaces) ............................................................................. 81

Copyright (C) 2007‐2011 by T. Takasu. All rights reserved.

i
 RTKLIB ver. 2.4.1 Manual

1 Overview

RTKLIB is an open source program package for standard and precise positioning with GNSS. RTKLIB

consists of a portable program library and several application programs (APs) utilizing the library. The

features of RTKLIB are:

(1) Supports standard and precise positioning algorithms with:

GPS, GLONASS, Galileo, QZSS and SBAS

(2) Supports various positioning modes with GNSS for both real‐time and post‐processing:

Single‐point, DGPS/DGNSS, Kinematic, Static, Moving‐baseline, Fixed, PPP‐Kinematic and PPP‐Static

(3) Supports many standard formats and protocols for GNSS:

RINEX 2.10, 2.11, 2.12 OBS/NAV/GNAV/HNAV, RINEX 3.00 OBS/NAV, RINEX 3.00 CLK, RTCM v.2.3,

RTCM v.3.1, NTRIP 1.0, NMEA 0183, SP3‐c, ANTEX 1.3, IONEX 1.0, NGS PCV and EMS 2.0 (see

Release Notes for supported RINEX files and RTCM messages)

(4) Supports several GNSS receiversʹ proprietary messages:

NovAtel: OEM4/V, OEM3, OEMStar, Superstar II, Hemisphere: Eclipse, Crescent, u‐blox: LEA‐4T,

LEA‐5T, LEA‐6T, SkyTraq: S1315F, JAVAD GRIL/GREIS, Furuno GW‐10‐II/III (see Release Notes for

supported messages)

(5) Supports external communication via:

Serial, TCP/IP, NTRIP, local log file (record and playback) and FTP/HTTP (automatic download)

(6) Provides many library functions and APIs:

Satellite and navigation system functions, matrix and vector functions, time and string functions,

coordinates transformation, input and output functions, debug trace functions, platform dependent

functions, positioning models, atmosphere models, antenna models, earth tides models, geoid models,

datum transformation, RINEX functions, ephemeris and clock functions, precise ephemeris and clock

functions, receiver raw data functions, RTCM functions, solution functions, Google Earth KML

converter, SBAS functions, options functions, stream data input and output functions, integer

ambiguity resolution, standard positioning, precise positioning, post‐processing positioning, stream

server functions, RTK server functions

(7) Provides GUI and console (command line) APs:

‐ RTKNAVI, RTKRCV : real‐time positioning

‐ RTKPOST, RNX2RTKP : post‐processing analysis

‐ RTKPLOT : visualization of solutions and observation data

‐ RTKCONV, CONVBIN : RINEX translator for RTCM and receiver raw data log

‐ STRSVR, STR2STR : communication utility

1
 RTKLIB ver. 2.4.1 Manual

‐ NTRIPSRCBROWS : NTRIP source table browser

‐ Other positioning utilities

All of the executable binary APs for Windows are included in the package as well as whole source

programs of the library and the APs.

2
 RTKLIB ver. 2.4.1 Manual

2 System Requirement

All of the library functions and APIs are written in ANSI C (C89). The library internally uses standard

socket and pthread (POSIX thread) for Linux/UNIX or winsock and WIN32 thread for Windows. By setting

compiler option ‐DLAPACK or ‐DMKL, the library uses LAPACK/BLAS or Intel MKL for fast matrix

computation. The console APs are also written in standard C. The library and console APs can be built on

many environments like gcc on Linux. The GUI APs are written in C++ and utilize Borland VCL for the GUI

toolkit. All of the executable binary APs in the package were built by free edition Borland Turbo C++ 2006

([Link] * on Windows. The binary APs were tested on Windows XP SP3 32bit and

Windows 7 64bit. The console APs are also built and tested on Ubuntu 9.04 Linux.

* Free edition Turbo C++ 2006 is no longer available. We plan to change the GUI toolkit for RTKLIB GUI

APs to open source one in future versions.

3
 RTKLIB ver. 2.4.1 Manual

3 Instructions

3.1 Installation/Uninstallation

(1) Extract the program package rtklib_<ver>.zip or rtklib_<ver>_bin.zip to appropriate

directory (<ver> indicates the version number). The RTKLIB directory structure is as follows.

rtklib_<ver>
\src : Source programs of RTKLIB libraries *
\rcv : Source programs depending on GPS/GNSS receivers *
\bin : Executable binary APs and DLLs for Windows
\data : Sample data for APs
\app : Build environment for APs *
\rtknavi : RTKNAVI (GUI) *
\rtknavi_mkl : RTKNAVI_MKL (GUI) *
\strsvr : STRSVR (GUI) *
\rtkpost : RTKPOST (GUI) *
\rtkpost_mkl : RTKPOST_MKL (GUI ) *
\rtkplot : RTKPLOT (GUI) *
\rtkconv : RTKCONV (GUI) *
\srctblbrows : NTRIP source table browser (GUI) *
\rtkrcv : RTKRCV (console) *
\rnx2rtkp : RNX2RTKP (console) *
\pos2kml : POS2KML (console) *
\convbin : CONVBIN (console) *
\str2str : STR2STR (console) *
\appcmn : Common routines for GUI APs *
\icon : Icon data for GUI APs *
\lib : Libraries generation environment*
\test : Test program and data *
\util : Utilities *
\doc : Document files

* Not included in the package rtklib_<ver>_bin.zip

(2) Create the shot‐cuts of the GUI AP executable binaries in rtklib_<ver>\bin. To execute console

APs, add <install dir>\rtklib_<ver>\bin to the command path.

4
 RTKLIB ver. 2.4.1 Manual

(3) The GUI and command line APs in RTKLIB never utilize Windows registry. To uninstall the RTKLIB

package, simply delete the whole files and directories in the installed directory.

(4) The optional settings for the GUI APs are saved in INI files (*.ini) usually placed in directory

C:\Windows. To uninstall the RTKLIB package completely, please delete these INI files too.

(5) Some GUI APs (RTKCONV, RTKPOST, RTKNAVI and STRSVR) in RTKLIB can be executed with the

command line option -i <inifile>.ini to select the alternative INI file for the other optional

settings. Users can switch the options for such APs by using the command line option as well as the

option -t <title> to change the window title. So you can configure multiple short‐cuts for the same

GUI AP with different options by setting the properties of the short‐cuts.

(6) To use RTKPOST_MKL or RTKNAVI_MKL, which is the Intel‐MLK‐library‐linked version RTKPOST

or RTKNAVI for faster matrix computation, on multiple‐core CPU or multiple‐processor computers,

please set the Windows environment variable OMP_NUM_THREADS to 2, 4 or 8 according to the number

of the CPU cores. That enables multi‐threading matrix computation in order to shorten the processing

time.

5
 RTKLIB ver. 2.4.1 Manual

3.2 Real-time Positioning with RTKNAVI

Real‐time positioning AP RTKNAVI inputs raw observation data of GPS/GNSS receivers and execute

navigation processing in real‐time. By setting the positioning mode to Kinematic and configuring the rover

and the base station receiver data inputs, RTK‐GPS/GNSS positioning is enabled with OTF (On‐the‐fly)

integer ambiguity resolution.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. (Double‐click the icon or full in the

path in the command console) You can see the main window of RTKNAVI.

Display Switch

Input/Output/Log
Time Display Stream
Status/Settings

Signal Level/
Solution Satellite Visibility
Display Display

RTK Monitor
Button Operation
Buttons

Message Area Save Log Button

(2) The following figure shows the data flow of RTKNAVI. You have to set Input Streams, Output Streams

(optional) and Log Streams (optional) for real‐time positioning.

GPS/GNSS Input Streams (I) Output Streams (O)

Receivers
(1) Input Rover (4) Output Solution 1

(2) Input Base Station RTKNAVI (5) Output Solution 2

(3) Input Correction

Correction (6) Log Rover
Provider

(7) Log Base Station

(8) Log Correction

Log Streams (L)

6
 RTKLIB ver. 2.4.1 Manual

(3) For real‐time positioning with RTKNAVI, you have to input the raw observation data and satellite

ephemerides from the GPS/GNSS receivers. To set the input stream, push the button I upper center

in the main window. You can see ʺInput Streamsʺ dialog.

(4) Check and set the stream type of Rover, Base‐station or Correction in the dialog. If you set the

positioning mode option ʺSingleʺ, the input stream for Base‐station and Correction are not required.

The stream types can be selected from the following options.

(a) Serial : Input data from a serial port (RS232C or USB)

(b) TCP Client : Connect to a TCP server and input data via the TCP connection

(c) TCP Server : Accept a TCP client connection and input data via the TCP connection

(d) NTRIP Client : Connect to a NTRIP server (caster) and input data via the NTRIP.

NRTK (network RTK) server supporting NTRIP and RTCM 2/3 can also

be used for the base‐station via Internet.

(e) File : Input data from a log file.

(f) FTP : Input data after downloading a file by FTP (Only for Correction)

(g) HTTP : Input data after downloading a file by HTTP (Only for Correction)

You have to select the stream data format from the following options with the pull down menu under

ʺFormatʺ. Refer Release Notes for the detailed supported messages.

(a) RTCM2 : RTCM 2.3

(b) RTCM3 : RTCM 3.1

(c) NovAtel OEM4/V : NovAtel OEM4/V, OEMStar binary format

(d) NovAtel OEM3 : NovAtel OEM3 (Millennium) binary format

(e) u‐blox : u‐blox LEA‐4T, 5T and 6T binary format

7
 RTKLIB ver. 2.4.1 Manual

(f) Superstar II : NovAtel Superstar II binary format

(g) Hemisphere : Hemisphere Crescent/Eclipse binary format

(h) SkyTraq : SkyTraq S1315F binary format

(i) GW10 : Furuno GW‐10‐II/III binary format

(j) Javad : JAVAD GRIL/GREIS binary format

(k) SP3 : SP3 precise ephemeris (Only for Correction)

(5) If you select Serial as the stream type, push ... button under ʺOptʺ label to set the options of port

selection, bit‐rate, byte size, parity, number of stop bits and flow control with ʺSerial Optionsʺ dialog.

(6) In case of selecting Serial as the stream type, you can configure the startup and shutdown commands

to be sent to the GPS/GNSS receiver. Push ... button under ʺCmdʺ label. Fill in the commands in the

text fields in ʺSerial Commandsʺ dialog. If you do not check ʺCommands at startupʺ or ʺCommands at

shutdownʺ, the startup or shutdown command is not sent to the receiver. You can also load the

commands from a command file by pushing Load... button or save the commands to a command file

with Save... button. The command file is just a text file including startup commands and shutdown

commands separated by a line starting with ʺ@ʺ. The sample command files for some typical receivers

are found in the directory rtklib_<ver>/data.

8
 RTKLIB ver. 2.4.1 Manual

(7) The line starting with ʺ!ʺ is treated as a receiver binary command. The following commands can be

used for u‐blox and SkyTraq receivers. Refer receiversʹ manuals for details.

!UBX ... : u‐blox LEA‐4T/5T command

!UBX CFG‐PRT portid res0 res1 mode baudrate inmask outmask flags

!UBX CFG‐USB vendid prodid res1 res2 power flags vstr pstr serino

!UBX CFG‐MSG msgid rate0 rate1 rate2 rate3

!UBX CFG‐NMEA filter version numsv flags

!UBX CFG‐RATE meas nav time

!UBX CFG‐CFG clear_mask save_mask load_mask

!UBX CFG‐TP interval length status time_ref res adelay rdelay udelay

!UBX CFG‐NAV2 ...

!UBX CFG‐DAT maja flat dx dy dz rotx roty rotz scale

!UBX CFG‐INF protocolid res0 res1 mask0 mask1 mask2 mask3

!UBX CFG‐RST navbbr reset res

!UBX CFG‐RXM gpsmode lpmode

!UBX CFG‐ANT flags pins

!UBX CFG‐FXN flags treacq tacq treacqoff tacqoff ton toff res basetow

!UBX CFG‐SBAS mode usage maxsbas res scanmode

!UBX CFG‐LIC key0 key1 key2 key3 key4 key5

!UBX CFG‐TM intid rate flags

!UBX CFG‐TM2 ch res0 res1 rate flags

!UBX CFG‐TMODE tmode posx posy posz posvar svinmindur svinvarlimit

!UBX CFG‐EKF ...

!STQ ... : SkyTraq S1315F binary command

!STQ RESTART [arg...] system restart

!STQ CFG‐SERI [arg...] configure serial port property

!STQ CFG‐FMT [arg...] configure output message format

!STQ CFG‐RATE [arg...] configure binary measurement output rates

!WAIT time : wait for time (ms)

(8) If you select TCP Client or TCP Server as the stream type, you can set the options of TCP server address

(for TCP Client only) and port number with ʺTCP Client Optionsʺ or ʺTCP Server Optionsʺ dialog. If

you select ʺTCP Serverʺ, multiple TCP client connections are allowed.

9
 RTKLIB ver. 2.4.1 Manual

(9) If you select NTRIP Client as the stream type, you can set the NTRIP client options of NTRIP caster host

address, port number, mount‐point of NTRIP caster, user‐ID and password with ʺNTRIP Client

Optionsʺ dialog. If the Port field blank, NTRIP default port number (2101) is used.

(10) If you select File as the stream type, input the file path to the text field Input File Paths. Fill in the path

directly or select a file with the file selection dialog by pushing ... button. The input file should be a

receiver raw data log. You can set the replay speed and the start time offset of the log file in Time field

(To use the feature, you have to record the log with the time‐tag file.)

10
 RTKLIB ver. 2.4.1 Manual

(11) By pushing the ʺOptʺ button right‐side of the input stream settings like ʺ‐EPHALLʺ, you can set the

receiver‐dependent options with the Receiver Option dialog. For the receiver‐dependent options,

please read the comment lines in the source program in rtklib_<ver>\src\rcv/<receiver>.c

(12) In case of using NRTK (network RTK) service, which requires NMEA GPGGA messages to select

reference station or to get virtual reference station position, select the message content with the pull

down menu at Transmit NMEA GPGGA to Base/NRTK. If you select Latitude/Longitude to send fixed

position, fill in the latitude and longitude for NMEA GPGGA message in degree (minus means south

or west).

(13) For correction, you can select FTP or HTTP for the stream type. After pushing Opt button, you have to

configure FTP or HTTP options with FTP Option or HTTP Option dialog. At first fill in the server

address and the file path in Download Address field as the format <server address>/<file path>.

Usually you might include day or time keywords in <file path>. For example, if downloading IGS

Ultra‐rapid ephemeris from NASA GSFC CDDIS data server , you can input the download address:
[Link]/gps/products/%W/igu%W%D_%hb.sp3.Z

In this case, the keywords %W, %D and %hb are replaced by GPS week number, day of week and 6 hour

of the day according to the download time in GPS Time, respectively. For other keywords which can be

used in the file path, push ? button and see the dialog. You can also set Download Interval,

Download Offset (for example, Interval = 6H and Offset = 2 H means the download will be tried at 2:00,

8:00, 14:00 and 20:00 in GPS Time), Time Offset in Path for replacing the keywords in the file path,

11
 RTKLIB ver. 2.4.1 Manual

Retry Interval, User (for FTP only) and Password (for FTP only) for the server. For User and Password,

ʺanonymousʺ and your mail address are usually used for the anonymous FTP server.

To use download files, you also have to set the file format in Input Dialog. Current version only

supports SP3 precise ephemeris for this purpose. Downloaded files are saved in a local directory. The

local directory path can be set with Options dialog ‐ Files ‐ FTP/HTTP Local Directory.

(14) To output of the positioning solution of RTKNAVI, set the output streams. To set the output streams,

push the button O upper right in the main window. You can see ʺOutput Streamsʺ dialog.

Check and set the stream type of solution in the dialog. You can configure two independent output

streams. You can select the stream type out of Serial, TCP Client, TCP Server, NTRIP Server and File.

The options are similar to the input streams. You also have to select the following output format

options. The time and latitude/longitude formats in output messages can be configured by the

positioning options.

(a) Lat/Lon/Height : Latitude, longitude and height

(b) X/Y/Z‐ECEF : X/Y/Z components in ECEF frame

(c) E/N/U‐Baseline : E/N/U components of the baseline

(d) NMEA‐183 : NMEA GPRMC, GPGGA, GPGSV

(15) If you select ʺFileʺ as the output stream type, you can include some keywords in the file path to be

replaced by date or time. Push ? button to show the keyword replacement in file paths. If you set

12
 RTKLIB ver. 2.4.1 Manual

Swap Intv option, the output file is swapped periodically in the specified cycle. To use the file swap

function, the file path must contain the keywords to be replaced by the swap time.

(16) If you select ʺNTRIP Serverʺ as the output stream type, you have to set NTRIP server options with

ʺNTRIP Server Optionʺ dialog. The options include the address of NTRIP Caster Host, the port number

to connect NTRIP caster, Mountpoint, Password and String showing the source‐table parameters to

NTRIP Caster. If the Port field is blank, the default port number (80) is used.

(17) To output an input stream as a path‐through log, set the log streams. To configure the log streams,

push the button L upper right in the main window. You can see ʺLog Streamsʺ dialog. The settings

are similar to the output streams. If you want to replay the log file as an input stream later, you have to

check ʺTime‐Tagʺ option and output the time tag file simultaneously. The output path of the time tag

file is output file path + .tag. The keyword replacements in the file paths and swap interval are the

same as ʺOutput Streamsʺ dialog.

13
 RTKLIB ver. 2.4.1 Manual

(18) To configure the positioning options, push Options... button and set the options in ʺOptionsʺ dialog.

For details of the positioning options, refer 3.5 Configure Positioning Options for RTKNAVI and

RTKPOST.

(19) Push Start button. The status of each streams are shown on the upper right indicators. From the left,

they show the stream/processing status of Input Rover, Input Base Station, Input Correction, the

positioning process, Output Solution 1, Output Solution 2, Log Rover, Log Base Station and Log

Correction. Gray represents not used, Orange means waiting for the connection, Deep‐green means

connected or running, Light‐green means data active (input, output or processing) and Red means a

communication error occurs. Some status messages are also shown in the lower center message area in

the main window. To stop the positioning process in RTKNAVI push Stop button.

(20) After the input observation data and ephemerides are completed and valid, RTKNAVI computes the

positioning solution and display it in the solution display left in the main window with the solution

status (FIX, FLOAT, DGPS, SBAS, SINGLE or PPP), E/N/U or X/Y/Z components of the standard

deviation, Age (age of differential), Ratio (ratio factor of ambiguity validation) and # of Sat (number of

14
 RTKLIB ver. 2.4.1 Manual

valid satellites). To switch the format in the solution display, push button upper right corner. You
can switch the solution to Lat/Lon/Height (degree/minute/second), Lat/Lon/Height (degree),

X/Y/Z‐ECEF (m), E/N/U‐Baseline (m), Pitch/Yaw/Length‐Baseline (deg, m), alternatively.

(21) To switch the format in the time display, push GPST button upper center in the main window. You

can switch the time system to GPST, UTC, JST and GPST (GPS week/TOW), alternatively.

(22) In the status display right in the main window, observation SNR status or visible satellites in skyplot

are shown. By pushing button upper right corner of the status display, you can switch the contents
to Rover : Base SNR, Rover SNR, Rover Skyplot, Base Skyplot and Baseline plot, Wide Rover : Base

SNR, Wide‐mode Rover SNR, alternatively. You can switch the frequency show in the plot by pushing

the second button near the upper right corner.

(23) By pushing Plot... button, you can execute RTKPLOT to plot the current position of the rover receiver

as the graph. For the usage of RTKPLOT, please refer 3.7 View and Plot Solutions and Observation

Data with RTKPLOT.

15
 RTKLIB ver. 2.4.1 Manual

(24) The positioning solutions are recorded in the internal buffer simultaneously. You can save the internal

solution buffer to the file by pushing ... below the solution display. The size of the solution buffer and

the saved solution log can be configured with ʺOptionsʺ dialog.

(25) By pushing the button lower left in the main window, you can see ʺRTK Monitorʺ window. With the
window, you can monitor the internal status of RTKNAVI. You can select the following contents with

the upper left pull down menu. Multiple ʺRTK Monitorʺ windows are allowed. To close the window,

push Close button.

16
 RTKLIB ver. 2.4.1 Manual

(a) RTK : General status of the internal positioning process

(b) Satellites : Status of each satellites

(c) States : State vector values of the estimation filter

(d) Covariance : Covariance matrix of the estimation filter

(e) Obs Data : Input observation data. RCV=1 means rover and 2 means base‐station

(f) Nav GPS/GAL/QZS : GPS, Galileo or QZSS navigation messages

(g) Nav GLONASS : GLONASS navigation messages

(h) Nav GEO : SBAS satellites navigation messages

(i) Time/Iono : Time and Ionosphere parameters

(j) Streams : Status of input, output and log streams

(k) SBAS Msgs : HEX dump of input SBAS messages

(l) SBAS Long : SBAS long term satellite corrections

(m) SBAS Iono : SBAS ionospheric delay corrections

(n) SBAS Fast : SBAS fast corrections

(o) RTCM Msgs : Status of RTCM 2 or 3 messages

(p) RTCM DGPS : RTCM DGPS corrections

(q) RTCM SSR : RTCM SSR corrections

(r) LEX Msgs : (reserved)

(s) LEX Eph/Clock : (reserved)

(t) LEX Iono : (reserved)

(u) Iono Correction : Ionosphere corrections

(v) (1) Rover : Dump of Input Rover stream

(w) (2) Base/NRTK : Dump of Input Base Station stream

(x) (3) Correction : Dump of Input Correction stream

17
 RTKLIB ver. 2.4.1 Manual

(y) (4)(5)Solution 1/2 : Dump of Output Solution 1/2 stream

(z) Error/Warning : Error or warning messages

(26) By pushing button lower right in the main window, you can minimize the main window as an icon
in the task‐tray of Windows desktop. To restore the main window, double‐click the task‐tray‐icon or

click right‐button on the task‐tray‐icon and select menu ʺMain Window...ʺ.

18
 RTKLIB ver. 2.4.1 Manual

3.3 Configure Input, Output and Log Streams for RTKNAVI

For relative positioning like RTK‐GPS/GNSS, the rover receiver and the base station receiver are usually

placed on the separated sites. In other cases, user might use the positioning result at the remote site far from

these receivers. To interconnect these sites, user has to establish data communication links. To facilitate easy

setup of these communication links, RTKLIB provides the communication utility STRSVR, with which user

can configure input and output data stream via these communication links. STRSVR also has the function

of relay or split the data stream for real‐time positioning with RTKNAVI.

For example, to receive observation data of a remote base station at a rover receiver site and to get RTK‐GPS

solution, user can place a remote PC installing STRSVR connecting to the base station receiver and can

configure STRSVR to send data to the rover site. The following examples show the typical applications of

RTKNAVI and SVRSVR.

(1) Single‐point positioning and output solutions to a file

PC

GPS/GNSS Serial
RTKNAVI File
Receiver

(1) Input Rover=Serial

(3) Output Solution 1=File

(2) Single point positioning, output solutions to a serial device, log data to a file

PC

GPS/GNSS Serial Serial

RTKNAVI
Receiver

(1) Input Rover=Serial

(3) Output Solution 1=Serial Log
(5) Log Rover=File

19
 RTKLIB ver. 2.4.1 Manual

(3) RTK‐GPS/GNSS, input the rover and base‐station data from two serial devices

PC
Rover Serial
Receiver
File
RTKNAVI
Base Station
Receiver Serial
(1) Input Rover=Serial
(2) Input Base Station=Serial
(3) Output Solution 1=File

(4) RTK‐GPS/GNSS, input rover data from a serial port and input base‐station data from a remote receiver

via WiFi network.

Base Station Rover

Receiver Receiver

PC Serial PC Serial

File
STRSVR RTKNAVI
TCP TCP
Server Client
(0) Input =Serial (1) Input Rover=Serial
(1) Output 1=TCP Server (2) Input Base Station=TCP Client
(3) Output Solution 1=File

(5) RTK‐GPS/GNSS, input rover data from a serial port and input base station data via mobile phone

Internet connection

Mobile
Phone
Base Station Rover
N/W
Receiver Receiver

PC Serial PC Serial

Internet File
STRSVR RTKNAVI
Mobile
Phone
(0) Input =Serial Terminal (1) Input Rover=Serial
(1) Output 1=TCP Server (2) Input Base Station=TCP Client
(3) Output Solution 1=File

20
 RTKLIB ver. 2.4.1 Manual

(6) RTK‐GPS/GNSS, input data from a serial port and input base station data via a NTRIP caster on

Internet. Current version does not support NTRIP caster feature. Please employ some alternative

NTRIP caster implementation.

Ntrip
Base Station Rover
Caster
GPS Receiver GPS Receiver

PC Serial PC Serial

Internet File
STRSVR RTKNAVI

(0) Input =Serial (1) Input Rover=Serial

(1) Output 1=NTRIP Server (2) Input Base Station=NTRIP Client
(3) Output Solution 1=File

(7) RTK‐GPS/GNSS with NRTK (Network RTK) service via Internet

Reference
Reference Rover
Reference
Station
Reference
Station GPS Receiver
Station
Station
PC Serial

Internet File
NTRIP Caster RTKNAVI

NRTK provider (1) Input Rover=Serial

(2) Input Base Station=NTRIP Client
(3) Output Solution 1=File

21
 RTKLIB ver. 2.4.1 Manual

(8) Multiple RTK‐GPS/GNSS with single NRTK service

Reference
Reference
Reference
Station
Reference
Station
Station
Station (1) Input =NTRIP Client
(2) Output=TCP Server
PC

NTRIP Caster Internet STRSVR

NRTK provider
LAN

PC PC PC PC

RTKNAVI RTKNAVI RTKNAVI RTKNAVI

Rover Rover Rover Rover

Receiver 1 Receiver 2 Receiver 3 Receiver 4

(1) Input Rover=Serial

(2) Input Base Station=TCP Client

(9) Real‐time PPP with real‐time satellite orbit and clock provided as a NTRIP stream.

Real‐time Orbit GPS Receiver

and clock
Provider
PC Serial

Internet File
NTRIP Caster RTKNAVI

NRTK provider (1) Input Rover=Serial

(2) Input Correction=NTRIP Client
(3) Output Solution 1=File

22
 RTKLIB ver. 2.4.1 Manual

(10) Long‐baseline RTK with FTP download of precise ephemeris

Base Station Rover

GPS Receiver GPS Receiver

PC Serial PC Serial

Internet File
STRSVR RTKNAVI

(0) Input =Serial (1) Input Rover=Serial

(1) Output 1=NTRIP Server (2) Input Base Station=NTRIP Client
(3) Input Correction=FTP
(3) Output Solution 1=File
IGS Data Server
Ultra‐rapid Ephemeris (SP3)

The following instructions are for the operation of STRSVR.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. You can see the main window of

STRSVR.

(2) To configure the input stream, select the stream type with pull down menu at ʺ(0) Inputʺ. Selectable

stream types are Serial, TCP Client, TCP Server, NTRIP Client, File, FTP or HTTP. The stream options

or the startup/shutdown command can be set as well as Input Streams for RTKNAVI.

(3) To configure the output streams, select the stream type with pull down menu at (1) Output, (2) Output

or (3) Output. The setting for the output streams are same as Output Streams or Log Streams for

RTKNAVI.

23
 RTKLIB ver. 2.4.1 Manual

(4) Push Start button in the main window. The communication status is shown in the message area lower

center of the main window. Status indicators left side of the main window also shows the

communication status. The indicator colors means: Orange: waiting connection, Dark‐Green:

connected, Light‐Green: data active, Red: error. Total data amount (bytes) and data rate (bps) of the

input and output streams are also shown in right side. To stop the communication, push Stop button.

(5) By pushing Options... button, you can set the communication options with ʺOptionsʺ dialog. To send

NMEA GPGGA message to the server connected the input stream, check ʺNMEA Request Cycleʺ and

set the request cycle (ms) and latitude/longitude in the messages. To connect an external NTRIP Caster

from the inside of the firewall via a HTTP‐proxy server, you can input the address and the port number

as the form <address>:<port> in HTTP/NTRIP Proxy field.

24
 RTKLIB ver. 2.4.1 Manual

3.4 Post-Processing Analysis with RTKPOST

RTKLIB contains a post processing analysis AP RTKPOST. RTKPOST inputs the standard RINEX 2.10 or

2.11 observation data and navigation message files (GPS, GLONASS, Galileo, QZSS and SBAS) and can

computes the positioning solutions by carrier‐based relative positioning.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. You can see the main window of

RTKPOST. You can execute the binary AP file rtklib_<ver>\bin\rtkpost_mkl.exe instead.

RTKPOST_MKL is a faster version of RTKPOST, which link Intel MKL library for fast matrix

computation.

(2) Input the RINEX observation data file path of the rover receiver in the text field RINEX OBS(: Rover).

Fill in the file path or select a file using the file selection dialog shown by pushing ... button. You can

use the compressed file by GZIP (.gz), COMPRESS (.z) or Hatanaka‐Compression (.yyd) for the

RINEX observation data. If a wild‐card (*) is included in the file path, the wild‐card expanded

multiple files are used.

(3) If you process RINEX data in the positioning mode of DGPS/DGNSS, Kinematic, Static, Moving‐Base

or Fixed, input the file path of the base‐station receiver in RINEX OBS: Base Station field as well as

rover observation data.

(4) You also have to input the path of RINEX navigation message files of GPS, GLONASS, SBAS and QZSS

25
 RTKLIB ver. 2.4.1 Manual

in RINEX *NAV/CLK, SP3, IONEX or SBS/ EMS field. If you leave first and second field blank, the

observation data file path with the extension replaced by .*nav (.obs)

or .yyN,.yyG,.yyH,.yyQ,.yyP (.yyO) is used for the navigation message files of GPS, GLONASS,

SBAS and QZSS. If a wild‐card (*) is included in the file path, the wild‐card expanded multiple files

are used. To use precise ephemeris and clock for PPP‐kinemaric or PPP‐static mode, you can input

SP3‐c (for precise satellite ephemeris and clock) or RINEX CLK (for precise satellite clock) file path in

the field. You can input IONEX 1.0 file for ionospheric VTEC grid corrections. For SBAS correction, you

can input SBAS message log as RTKLIB format or EMS (EGNOS message server) 2.0 format file. You

can also include wild‐cards (*) in these file paths. The wild‐cards are expanded and multiple files are

used.

(5) Input the output file path in the text field Solution. The field is automatically set as the first input file

path with the extension replaced by .pos or .nmea. If you check Dir and fill in the field, the output

directory is set to the specified directory. You can modify the output file path manually.

(6) Push Options... button to set the processing options. For detailed options, refer 3.5 Configure

Positioning Options for RTKNAVI and RTKPOST. You can set the start time or end time by checking

and setting Time Start (GPST) or Time End (GPST) field in the main window. You also set the time

interval by checking and setting Interval field. With the ? button, the input time in GPS time can be

converted to UTC, GPS Week/TOW, Day of Year, Day of Week, Time of Day and Leap Seconds.

(7) If you check both of Time Start and Time End, you can check Unit for multiple session analysis. If Unit

checked and set the Unit, the analysis session is separated to multiple sessions for the Unit (hr). To

avoid overwriting the output to the same file, the output file path has to contain the keyword replaced

according to the session time. For details of the keyword replacement in the input or output file paths,

refer 3.5 Configure Positioning Options for RTKNAVI and RTKPOST.

(8) Push Execute button to start the analysis. The processing status is shown in the status message field

lower center in the main window. When you see ʺdoneʺ message here, the analysis is completed. If you

26
 RTKLIB ver. 2.4.1 Manual

want to stop the processing on the way, push Abort button.

(9) After completing the analysis, by pushing View... button, you can display the content of the output

file by Text Viewer. You can reload the output file by pushing button in Text Viewer window. To
close the window, push Close button.

(10) By pushing View... button, you can also plot the result with RTKPLOT. Refer 3.7 View and Plot

Solutions and Observation Data with RTKPLOT for details.

27
 RTKLIB ver. 2.4.1 Manual

(11) By pushing To KML... button, the output file can be converted to Google Earth KML file with ʺGoogle

Earth Converterʺ dialog. Set or select the options and push Convert button in the dialog. You can

launch Google Earth with the generated KML/KMZ file by pushing Google Earth button. To specify

the Google Earth execution file, configure Options ‐ Files ‐ Google Earth Exe File.

(12) With button in the main window, you can view and plot the input observation data RTKPLOT. You

can also display the contents of the input files with Text Viewer by pushing button.

28
 RTKLIB ver. 2.4.1 Manual

3.5 Configure Positioning Options for RTKNAVI and RTKPOST

By pushing Options... button in the main windows of RTKNAVI or RTKPOST, you can set the positioning

options. Selectable or changeable positioning options are as follows. These options can be saved to the

configuration file by pushing Save button on the dialog and select the file path. The options can be

loaded from a configuration file by pushing Load button and selecting a configuration file. For the

configuration file, refer B.4.

(1) Setting 1

Item Descriptions Notes

Set positioning mode
‐ Single : Single point positioning or SBAS DGPS
‐ DGPS/DGNSS : Code‐based differential GPS
‐ Static : Carrier‐based Static positioning
‐ Kinematic: Carrier‐based Kinematic positioning
‐ Moving‐Base: Moving baseline
Positioning Mode
‐ Fixed: Rover receiver position is fixed
‐ PPP Kinematic: Precise Point Positioning with kinematic
mode
‐ PPP Static: Precise Point Positioning with static mode
‐ PPP Fixed: Rover receiver position is fixed with PPP
mode

29
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set used carrier frequencies
‐ L1 : L1 only
Frequencies ‐ L1+L2 : L1 and L2
‐ L1+L2+L5: L1, L2 and L5
‐ L1+L2+L5+L6: L1, L2, L5 and L6 (reserved)
Set solution type
‐ Forward: Forward filter solution
Solution Type ‐ Backward: Backward filter solution * * RTKPOST only
‐ Combined: Smoother combined solution with forward
and backward filter solutions *
Elevation Mask Set elevation mask angle (deg)
SNR Mask Set SNR mask (dBHz)
Set the dynamics model of the rover receiver.
‐ OFF: Dynamics is not used Only effective in
Rec Dynamics ‐ ON: Receiver velocity and acceleration are estimated. DGPS/DGNSS or
The receiver position is predicted with the estimated Kinematic mode
velocity and acceleration.
Only available in
Set whether earth tides correction is applied or not
Earth Tides DGPS/DGNSS,
‐ OFF: Not apply earth tides correction
Correction Kinematic or PPP
‐ ON: Apply earth tides correction
Mode
Set ionospheric correction options. If you set the
parameter Estimated. Vertical ionospheric delay for each
satellite) are estimated. For long baseline analysis,
ionosphere estimation is effective to suppress
ionosphere delay effects.
‐ OFF : Not apply ionospheric correction
‐ Broadcast: Apply broadcast ionospheric model Estimated STEC is
‐ SBAS: Apply SBAS ionospheric model effective for only
Ionosphere
‐ Dual‐Frequency: Ionosphere‐free linear combination DGPS/DGNSS or
Correction
with dual frequency measurements is used for Kinematic, Static
ionospheric correction mode.
‐ Estimate STEC : Estimate ionospheric parameter STEC
(slant total electron content)
‐ IONEX TEC: Use IONEX TEC model
‐ QZSS Broadcast: Apply broadcast ionosphere model
provided by QZSS
‐ QZSS LEX: (reserved)
Set whether tropospheric parameters (zenith total
delay at rover and base‐station positions) are estimated or
not.
‐ OFF : Not apply troposphere correction
Troposphere ‐ Saastamoinen: Saastamoinen model
Correction ‐ SBAS: SBAS tropospheric model
‐ Estimate ZTD: Estimate ZTD (zenith total delay)
parameters
‐ Estimate ZTD+Grad: Estimate ZTD and horizontal
gradient parmeters

30
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set the type of satellite ephemeris.
‐ Broadcast : Use broadcast ephemeris
‐ Precise : Use precise ephemeris
‐Broadcast+SBAS: Broadcast ephemeris with SBAS
SSR corrections
long‐term and fast correction
Satellite Ephemeris can be applied
‐Broadcast+SSR APC: Broadcast ephemeris with SSR
only for RTKNAVI
correction (antenna phase center value)
‐ Broadcast+SSR CoM: Broadcast ephemeris with SSR
correction (satellite center of mass value)
‐ QZSS LEX: (reserved)
Set the excluded satellites for positioning. Fill in the PRN
numbers of the satellites separated by spaces. For
Excluded Satellites GLONASS, Galileo, QZSS and SBAS, use Rnn, Enn, Jnn
(+PRN: Included) and Snn, respectively (nn: satellite number).
If ʺ+ʺ is added to the head of the satellite ID, the satellite is
included for positioning even if the satellite is unhealthy.
Check used navigation satellite systems. If not checked,
satellites of the system are not used for positioning.
‐ GPS
‐ GLONASS
Navi System * Not supported yet
‐ Galileo *
‐ QZSS
‐ SBAS
‐ Compass *

(2) Setting 2

31
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set the strategy of integer ambiguity resolution
‐ OFF : No ambiguity resolution
‐ Continuous : Continuously static integer ambiguities are
estimated and resolved
Integer Ambiguity
‐ Instantaneous : Integer ambiguity is estimated and Default: Continuous
Resolution
resolved by epoch‐by‐epoch basis
‐ Fix and Hold : Continuously static integer ambiguities
are estimated and resolved. If the validation OK, the
ambiguities are tightly constrained to the resolved values.
Set the strategy of GLONASS integer ambiguity resolution
‐ OFF: Ambiguities are not fixed.
‐ ON: Ambiguities are fixed. Usually the ambiguity of only
GLONASS
the same types receiver pair for the rover and the base
Ambiguity Default: ON
station can be fixed. The different receiver types have
Resolution
inter‐channel bias which can not be canceled by DD.
‐ Auto calibration: Receiver inter‐channel bias terms are
estimated as a linear equation by the frequencies.
Validation Set the integer ambiguity validation threshold for
Threshold to Fix ratio‐test, which uses the ratio of squared residuals of the Default value: 3.0
Ambiguity best integer vector to the second‐best vector.
Set the minimum lock count and the minimum elevation
Min Lock /
angle (deg) to fix integer ambiguity. If the lock count or the
Elevation to Default value: 0, 0
elevation angle is less than the value, the ambiguity is
Fix Ambiguity
excluded from the fixed integer vector.
If you select ʺFix and Holdʺ mode for Integer Ambiguity
Min Fix / Elevation
Resolution, set the minimum fix count and the minimum Default value: 10, 0
to Hold Ambiguity
elevation angle (deg) to hold ambiguity.
Set the outage count to reset ambiguity. If the data outage
Outage to count is over the value, the estimated ambiguity is reset to
Default value: 5,
Reset Ambiguity/ the initial value. And set the cycle‐slip threshold (m) of
0.05
Slip Thres geometry‐free LC carrier‐phase difference between
epochs.
Max Age of Set the maximum value of age of differential (s) between
Default value: 30
Differential the rover and the base station.
Set the reject threshold of GDOP and innovation (pre‐fit
Reject Threshold
residual) (m). If the GDOP or the innovation is over the
of GDOP/ Default value: 30, 30
value, the observable is excluded for the estimation
Innovation
process as an outlier.
Set the number of iteration in the measurement update
Number of of the estimation filter. If the baseline length is very short
Default value: 1
Iteration like 1 m, the iteration may be effective to handle the
nonlinearity of measurement equation.
If Moving‐Base mode, check and set the constraint of the
Baseline Length
baseline length. Fill in the length in m and the standard
Constraint
deviation (m) of the constraint.

32
 RTKLIB ver. 2.4.1 Manual

(3) Output

Item Descriptions Notes

Set the output solution format.
For RTKNAVI,
‐ Lat/Lon/Height : Latitude, longitude and height
specify options as
Solution Format ‐ X/Y/Z‐ECEF : X/Y/Z components of ECEF coordinates
Output Streams
‐ E/N/U‐Baseline: E/N/U components of baseline vector
setting.
‐ NMEA0183 : NMEA GPRMC, GPGGA, GPGSV
Not applicable to
Output Header Set whether the header is output or not.
NMEA
RTKPOST only
Output Processing
Set whether the processing options are output or not. Not applicable to
Options
NMEA
Set the format of time
‐ [Link] GPST : GPS week and TOW (time of week)
Not applicable to
Time Format ‐ hh:mm:ss GPST : yyyy/mm/dd hh:mm:ss GPST
NMEA
‐ hh:mm:ss UTC : yyyy/mm/dd hh:mm:ss UTC
‐ hh:mm:ss JST : yyyy/mm/dd hh:mm:ss JST
Not applicable to
# of Decimals Set number of decimals in the time format
NMEA
Set the formats of latitude and longitude if the solution
Latitude/Longitude format is set to Lat/Lon/Height. Not applicable to
Format ‐ [Link] : Degree NMEA
‐ ddd mm [Link] : Degree minute second
Not applicable to
Field Separator Set the separator for fields.
NMEA
Set the datum if the solution format option is set to
Lat/Lon/Height.
Datum ‐ WGS84 : WGS84 datum
‐ Tokyo : Tokyo datum
(current version supports only WGS84)
Set the type of height.
Height ‐ Ellipsoidal : Ellipsoidal height
‐ Geodetic : Geodetic height

33
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set the geoid model if the Height option is set to Geodetic.
‐ Internal: Internal geoid model
‐ EGM96‐BE (15ʺ) : EGM96 (15ʺ x 15ʺ grid) *1
‐ EGM2008‐SE (2.5ʺ) : EGM2008 (2.5 x 2.5ʺ grid) *2
Geoid Model
‐ EGM2008‐SE (1ʺ): EGM2008 (1 x 1ʺ grid) *2
‐ GSI2000 (1x1.5ʺ): GSI2000 (1x1.5ʺ grid) *3
If using external geoid model, specify the geoid file path in
ʺFilesʺ tab.
Set the solution type for Static or PPP‐Static mode
‐ All: all solutions for the processing period are outputted
Solution for Static
‐ Single: Only one solution for the processing period is RTKPOST only
Mode
outputted. The time of solution is first epoch in the
processing period.
NMEA Interval (s) Set the output interval of NMEA GPRMC, GPGGA
RTKNAVI only
RMC/GGA messages
NMEA Interval (s) Set the output interval of NMEA GPGSA, GPGSV
RTKNAVI only
GSA/GSV messages
Set the output level of the solution status file. The solution
Output Solution status file contains estimated states and residuals. The
Status solution status file is created in the current directory
(RTKNAVI) or in the output file directory (RTKPOST).
Set the output level of debug trace file. If setting OFF, any
debug trace file is not output. The debug trace file is
Output Debug Trace
created in the current directory (RTKNAVI) or in the
output file directory (RTKPOST).

*1 [Link] ([Link] )
*2 Und_min1x1_egm2008_isw=82_WGS84_TideFree_SE,
Und_min2.5x2.5_egm2008_isw=82_WGS84_TideFree_SE
([Link] )
*3 gsigeome.ver4 ([Link]

(4) Statistics

34
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Measurement
Errors (1‐sigma)
Code/Carrier‐Phase Set the ratio of standard deviations of pseudorange Default value: 100,
Error Rate L1/L2 errors to carrier‐phase errors for L1 and L2/L5/L6. 100
Set the base term of carrier‐phase error standard
Carrier‐Phase Error Default value: 0.003
deviation (m).
Carrier‐Phase Set the elevation dependent term of carrier‐phase error
Default value: 0.003
Error/sinEl standard deviation (m/sin(el)).
Carrier‐Phase Set the baseline‐length dependent term of carrier‐phase
Default value: 0
Error/Baseline error standard deviation (m/10km).
Set the standard deviation of Doppler errors (Hz)
Doppler Frequency Default value: 1
(Current version does not use the value)
Process Noises
(1‐sigma/sqrt(s))
Set the process noise standard deviation of the receiver
Receiver Accel acceleration as the horizontal or vertical component. Default value:
Horiz/Vertical (m/s2/sqrt(s)). If Receiver Dynamics is set to OFF, they are 1 and 0.1
not used.
Set the process noise standard deviation of carrier‐phase Default value:
Carrier‐Phase Bias
bias (ambiguity) (cycle/sqrt(s)). 1E‐4
Vertical Ionospheric Set the process noise standard deviation of vertical Default value:
Delay ionospheric delay per 10 km baseline (m/sqrt(s)). 1E‐3
Zenith Tropospheric Set the process noise standard deviation of zenith Default value:
Delay tropospheric delay (m/sqrt(s)). 1E‐4
Satellite Clock Set the satellite clock stability(s/s). The value is used for Default value:
Stability interpolation of base‐station observables. 5E‐12

(5) Positions

35
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Rover
Lat/Lon/Height Set the position of the rover antenna if the rover antenna is
(deg/m) fixed.
Select the type of the rover antenna.
To select the antenna type, set the Receiver Antenna PCV
File path in Files. If ʺ*ʺ is used, antenna type and antenna
Antenna Type
delta are recognized by the antenna information of RINEX
OBS header (RTKPOST) or RTCM antenna information
(RTKNAVI).
Set the delta position of the rover antenna as the E/N/U
Delta‐E/N/U offsets of ARP (antenna reference point) position with
refer to the marker (m).
Base Station
Set the position of the base‐station antenna.
‐ Lat/Lon/Height (deg/m): Latitude/longitude/height in
degree and m
‐ Lat/Lon/Height (dms/m): Latitude/longitude/height in
degree/minute/second and m
‐ X/Y/Z‐ECEF (m): X/Y/Z components in ECEF frame.
Height is specified
‐ RTCM Station Position: Use the antenna position
Lat/Lon/Height as ellipsoidal height
included in RTCM messages *
(deg/m) * RTKNAVI only
‐ Average of Single‐Pos: Use the average of single point
** RTKPOST only
solutions **
‐ Get from Position File: Use the position in the position
file. The station is searched by using the head
4‐character ID of the rover observation data file path. **
‐ RINEX Header Position: Use the approximate position in
RINEX OBS header. **
Select the type of the base‐station antenna.
To select the antenna type, set Receiver Antenna PCV
File in Files. If ʺ*ʺ is used, antenna type and antenna delta
Antenna Type
are recognized by the antenna information of RINEX OBS
header (RTKPOST) or RTCM antenna information
(RTKNAVI).
Set the delta position of the base‐station antenna as E/N/U
Delta‐E/N/U
offsets of ARP position with refer to the marker (m).

36
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Input the station position file path to retrieve the position
from the station list. The station position file is a text file
which contains the multiple lines. Each line represents
a record for a station. A record contains:
‐ Latitude (deg)
‐ Longitude (deg)
‐ Ellipsoidal height (m)
‐ Station ID
Station Position File ‐ Station name
separated by spaces. The line starting ʺ%ʺ is treated as the
comment line. An example station position file is found at
rtklib_<ver>\data\[Link].

SINEX station positions can be used as well. An sample

SINEX file is found at
rtklib_<ver>\data\igs10P1565_wocov.snx

If you set Station Position File in ʺFilesʺ tab, you can select the potion of the rover or the base‐station

antenna from the station list in ʺStationsʺ dialog by pushing ... button. You can load Lat/Lon/Hgt format or

SINEX format file. The file type is automatically recognized. You can search a station Id or Name with Find

button with a specified word in the Find field.

37
 RTKLIB ver. 2.4.1 Manual

(6) Files

Item Descriptions Notes

If you use the precise ephemeris or SSR correction, input
the ANTEX antenna parameters file path for the satellite
Satellite Antenna antenna PCV (phase center variation) correction. Usually
PCV File ANTEX use latest [Link] file provided by IGS.
An example of the ANTEX file is found at
rtklib_<ver>\data\[Link].
If you apply the receiver antenna phase center offset and
PCV correction, input ANTEX or NGS type antenna
Receiver Antenna parameters file path.
PCV File ANTEX or An example of the antenna parameter file is found at
NGS rtklib_<ver>\data\[Link].
or
rtklib_<ver>\data\ngs_abs.pcv.
Input the file path of the geoid data file if selecting the
Geoid Data File
external model as Geoid Model.
Ionosphere Data
(reserved)
File
Input the file path of DCB correction for PPP in CODE
format.
DCB Data File An example of the antenna parameter file is found at
rtklib_<ver>\data\P1C1_ALL.DCB
rtklib_<ver>\data\[Link]
rtklib_<ver>\data\P1P2_ALL.DCB
Ocean Loading BLQ (current version does not support ocean loading
Format correction)
Google Earth Exe
Input the execution file path of Google Earth. RTKPOST only
File
FTP/HTTP Local Input the local directory for FTP/HTTP download. The
RTKNAVI only
Directory downloaded files are save in the directory.

38
 RTKLIB ver. 2.4.1 Manual

(6) Misc (RTKNAVI)

Item Descriptions Notes

Set the processing cycle time of in ms. Usually set 100 ms
Processing Cycle
or less value.
Set the timeout and re‐connect interval for TCP client and
Timeout/ NTRIP client connections in ms. If the timeout time
Re‐Connect Interval expired without sever response, RTKNAVI retries to
connect to server after waiting for the re‐connect interval.
If output or log file swap enabled, set the overlapped
periods between the previous and the new output files in
File Swap Margin second. If you set it to 0, the periods of these files are not
overlapped. This feature is to avoid the missing of
transient data by the output file swapping.
NMEA Set the NMEA GPGGA transmission cycle to NRTK server
Transmission Cycle in ms.
Set the internal input message buffer size in bytes. Usually
Input Buffer Size
set it to 32768 or more.
Set the internal solution buffer size and log size in epochs.
Solution Buffer/Log
To increase the length of the receiver trajectory on ʺRTK
Size
Mapʺ, increase the solution buffer size.
Select navigation messages to be used.
‐ (1) All: In any of the input streams
Navigation Message
‐ (2) Rover: In the rover receiver stream
Selection
‐ (3) Base Station: In the base station receiver stream
‐ (4) Correction: In the correction stream
If SBAS DGPS correction enabled, input SBAS satellite
SBAS Satellite
PRN number to be used. If you input 0, all available SBAS
Selection
satellites are used.
Set monitor port number. The monitor port is TCP server
port to connect from outside or by RTKPLOT for real‐time
Monitor Port
solution monitor. If multiple instances of RTKNAVI are Default: 52001
Number
generated, the following numbers are used automatically.
If 0 is set, the monitor port is not used.

39
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set HTTP/NTRIP proxy server address and port number
HTTP/NTRIP Proxy as <address>:<port> form to connect the NTRIP
Caster via a HTTP‐Proxy server.
Solution Font Select the font of the solution display in the main window.

(7) Misc (RTKPOST)

Item Descriptions Notes

Select ON to enable time interpolation of base station data.
Time Interpolation If selecting ON, the base station data are linearly
of Base Station interpolated to the rover epoch and DD
Observation Data (double‐difference) is made with them. If not checked,
nearest epoch of base station data is used for DD.
If SBAS DGPS correction enabled, input SBAS satellite
SBAS Satellite
PRN number to be used. If you input 0, all available SBAS
Selection
satellites are used.
For batch processing with multiple input files or multiple
sessions, you can set input file paths or output file path
containing the following keywords.

%Y, %y, %m, %d, %n, %W, %D, %h, %H, %r, %b

Station ID List
The keywords are replaced by the proper values or
expanded for multiple session analysis.
To enable time keywords, set Time Start, Time End and
Unit (optional) in the main window. For keywords %r, %b ,
input Rover List or Base Station List below.
For online reference, push ʺ?ʺ button.
Input the rover ID list to replace keyword %r in input and
Rovers output file paths. The line starting with ʺ#ʺ is treated as a
comment.

40
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Input the base station ID list to replace keyword %b in
Base Stations input and output file paths. The line starting with ʺ#ʺ is
treated as a comment.

41
 RTKLIB ver. 2.4.1 Manual

3.6 Convert Receiver Raw Data to RINEX with RTKCONV

RINEX (Receiver Independent Exchange Format) is a standard GPS/GNSS data format supported by many

receivers or GPS/GNSS post‐processing analysis software. RTKLIB post‐processing analysis AP RTKPOST

can also handle RINEX data files as inputs. For preparing RINEX files, RTKLIB provides the converter AP

RTKCONV, which translates receiver raw data to RINEX OBS (observation data), RINEX NAV (GPS

navigation messages) and RINEX GNAV (GLONASS navigation messages). RTKCONV can also extract

SBAS messages from the receiver raw data and output the SBAS log file.

The supported RINEX version is 2.10 or 2.11. RINEX 3.0 will be supported by the future version. Refer

the Appendix B.2 SBAS Log File for the SBAS log file format.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. You can see the main window of

RTKCONV.

(2) Input the receiver raw data file path to the text field RTCM, RCV RAW or RINEX OBS. Fill in the file

path directly or select the file with the file selection dialog by pushing ... button. You can also drag

and drop the icon of the raw data file to the main window of RTKCONV. Supported receiver raw data

formats are as follows. Refer Release Notes for detailed supported messages.

(a) RTCM2 : RTCM 2.3

(b) RTCM3 : RTCM 3.0 or 3.1

(c) NovAtel OEM4/V : NovAtel OEM4/V binary format

(d) NovAtel OEM3 : NovAtel OEM3 (Millennium) binary format

42
 RTKLIB ver. 2.4.1 Manual

(e) u‐blox : u‐blox LEA‐4T, 5T, 6T binary format

(f) Superstar II : NovAtel Superstar II binary format

(g) Hemisphere : Hemisphere Crescent/Eclipse binary format

(h) SkyTraq : SkyTraq S1315F binary format

(i) GW10 : Furuno GW‐10‐II/III binary format

(j) Javad : JAVAD GRIL/GREIS binary format

(k) RINEX : RINEX OBS format.

If the wild‐card (*) is used in the file path, wild‐card expanded multiple files will be read. By setting

RINEX as the input file format and setting output RINEX version, you can convert RINEX version 2 to

version 3 or RINEX version 3 to version 2.

(3) Select the format with the pull down menu Format. If you select ʺAutoʺ, RTKCONV recognizes the file

format according to the following file extensions.

(a) RTCM2 : .rtcm2

(b) RTCM3 : .rtcm3

(c) NovAtel OEM4/V : .gps

(d) u‐blox : .ubx

(e) Superstar II : .log

(f) Hemisphere : .bin

(g) SkyTraq : .stq

(h) Javad : .jps

(i) RINEX : .obs,.*o, .*O

(4) Input the output paths of RINEX OBS (observation data), RINEX NAV (GPS navigation messages),

RINEX GNAV (GLONASS navigation messages), RINEX HNAV (GEO satellite navigation messages),

RINEX QNAV (QZSS navigation messages) and SBAS Log files. Fill in the file path directly or select the

file with the file selection dialog by pushing ... button. If you do not check the checkbox left, the file is

not output. RINEX GNAV, HNAV and QNAV are supported only in RINEX version 2. If selecting

version 3 as output RINEX, all navigation data are output to a combined NAV type RINEX file. The

output files can include keywords. The keywords are replaced by time, date or station ID. Push ʺ?ʺ

button, to refer the keyword replacements in output files.

(5) If you want to output the files to a directory, check Output Directory and input the output directory.

The directory can be selected by pushing ... button. If the Output Directory is not checked, the files are

43
 RTKLIB ver. 2.4.1 Manual

output to the same directory of the input file. If the output directory is not exist, the directory is

automatically created. However, the parent directory always has to be exist for the directory creation.

(6) You can set the start time or end time optionally by checking and setting Time Start (GPST) or Time

End (GPST) field upper in the main window. You can also set the time interval option by checking and

setting the field Interval. If you input Time Start and Time End, check Unit and input Time Unit, you

can initiate multiple‐session conversion. In this case, please include keywords to be replaced by date

and time in the input file path and the output file paths. Note that RTKCONV does not confirm the

overwrite if the output file exists in such multi‐session conversion.

(7) You can push Options... button to configure RINEX options. Set the options for RINEX headers,

navigation systems, observation types or frequencies with ʺOptionsʺ dialog . If you check RINEX Name,

the output file paths are compliant to the RINEX file name convention. Please input Station ID to

complete the output file names for RINEX file name convention. The Option field is

receiver‐dependent options. Specify the option like ʺ‐EPHALLʺ. For details, refer the comment in the

source codes in rtklib_<ver>\src\rcv\<receiver>.c.

(8) Push Convert button to start converting the receiver raw data to RINEX and SBAS log files. If you

want to stop the conversion on the way, push Abort button. The status is displayed in the message

area lower center in the main window. The message O=nnn means the number of converted

observation data (epochs). The message N=nn, G=nn, H=nn, S=nnn, Q=nnn and E=nnn means the

number of navigation messages (NAV, GNAV, HNAV and QNAV), SBAS messages and errors,

respectively.

44
 RTKLIB ver. 2.4.1 Manual

(13) After finishing the conversion, you can see the observation data plot by pushing Plot... button with

RTKPLOT. Refer 3.7 Plot and View Solutions and Observation Data for details. You can also view the

output file with Text Viewer by pushing button.

(14) By pushing Process... button, you can execute RTKPOST_MKL AP to process the converted RINEX

OBS/NAV files. Refer 3.4 Post‐processing Analysis with RTKPOST for details.

45
 RTKLIB ver. 2.4.1 Manual

3.7 View and Plot Solutions and Observation Data with RTKPLOT

RTKLIB contains the AP RTKPLOT to view and plot the positionig solutions by RTKLIB or RINEX

observation data with graphical user interface.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. You can see the main window of

RTKPLOT. By pushing Plot... button or some buttons of RTKPOST and RTKCONV, RTKPLOT is also

executed.

Plot Type Tool Time Reload/

Selection Buttons Scroll‐bar Clear
Button

Tool Bar

Plot Area

Status Bar

(2) Execute the menu ʺFileʺ ‐ ʺ Open Solution 1ʺ and select the solution file with the file selection dialog.

The input solution file can be RTKLIB solution format or NMEA‐0183. If the file format is NMEA, the

file has to contain at least GPRMC and GPSGGA sentences. If the solution file is valid, the receiver

ground track is plot in the window on the map. The color of the marks, lines and grid in the plot can be

changed with menu ʺEditʺ ‐ ʺOptionsʺ. The status bar at the bottom of the main window also shows the

time range, the number of solution epochs (N=nnnn), the baseline length (B=[Link]), the number

and percentage of each quality solutions (Q=1:nnn(pp%), 2:nnn(pp%),...). The quality flag Q

and the marker color means: 1: Fixed, 2: Float, 4: DGPS, 5: Single (the colors are changeable with the

plot options). To screen the marks by the quality flag Q, select the second pull down menu in the Tool

Bar. By drag and drop of the solution file icon to the main window of RTKPLOT, you can also read and

plot the solution file.

46
 RTKLIB ver. 2.4.1 Manual

(3) By dragging the mouse with the left button down on the plot, you can drag the map up, down, left and

right . You also change the scale of the map by dragging the mouse up or down with the right button

or by rotating the scroll wheel of the mouse.

(4) By selecting the pull down menu right in Tool Bar, you can switch the plot to E/N/U components of

receiver position (Position), E/N/U components of receiver velocity (Velocity) or E/N/U components of

receiver acceleration (Accel). You can drag the X/Y‐axis with the left‐button dragging and change the

scale with the right‐button dragging at the X/Y‐axis area.

47
 RTKLIB ver. 2.4.1 Manual

(5) By selecting the pull down menu right in Tool Bar, you can switch the plot to NSat/Age/Ratio (number

of valid satellites, age of differential, ratio factor of ambiguity validation). If you set Output Solution

Status option to Residuals, you can show the residuals plot by selecting L1 Residuals, L2 Residuals or

L5 Residuals. In residuals plot mode, you can select a satellite with right pull down menu as well as all

satellites. In the residuals plot of carrier‐phase, the red lines indicate cycle slips and gray lines indicate

parity unknown flags (That mean the half‐cycle ambiguities in carrier‐phase are not resolved).

48
 RTKLIB ver. 2.4.1 Manual

(6) By opetating tool buttons in Tool Bar, you can center the current position with , adjust the scale of

X‐axis with , adjust the scale of Y‐axis with , display the current position as a large mark with ,

fix the current position at the horizontal center with , fix the current position at the vertical center

with , start animation with and stop animation with . You can also slide Time Scroll Bar to
change the epoch of the current position. To clear read data, execute the menu ʺFileʺ ‐ ʺClearʺ or push

button in Tool Bar. To reload the solution file, execute the menu ʺFileʺ ‐ ʺReloadʺ or push button
in Tool Bar.

(7) By executing the menu ʺFileʺ ‐ ʺOpen Map Imageʺ, you can read a JPEG image and draw the map

image on the background of ʺGnd Trkʺ plot. The image can be enabled or disabled by pushing
button in Tool Bar.

(8) To adjust the position in the map image, execute the menu ʺEditʺ ‐ ʺMap Imageʺ and input latitude and

longitude of the image‐center, image‐scale along X or Y‐axis in ʺMap Imageʺ dialog. If you finish it,

push Save Tag button to save the adjustment information to an image‐tag‐file. The path of the

image‐tag‐file is the original map image file path + .tag. If the image‐tag‐file already exists, it is

automatically read with the map image itself. The current version does not support rotation of the map

image. Please select the map image in which the north direction is properly aligned to the upper

direction. For example, you can get a JPEG image by the menu ʺFileʺ ‐ ʺSaveʺ of Google Earth. To fix

north to upper, push ʺNʺ button in Google Earth. To avoid the distortion of the map image, set the

49
 RTKLIB ver. 2.4.1 Manual

coordinates origin inside of or near the map image.

(9) By executing the menu ʺEditʺ ‐ ʺWaypoints...ʺ, you can see the ʺWaypointsʺ dialog. With the dialog,

you can load, save, add and delete the way‐points as the list form. By pushing Add button and editing

the point name, the current receiver position can be added to the way‐point list. The positions of the

waypoints are shown on the ʺGnd Trkʺ plot when button down.

(10) To plot multiple solution file, execute the menu ʺFileʺ ‐ ʺOpen Solutions‐2ʺ and select file with the file

selection dialog. You can switch the plot on/off of the solution 1 and 2 with 1 2 buttons in Tool Bar.

To Plot the difference of the solution 1 and the solution 2, push 1‐2 button in Tool Bar.

(11) To set the time range and time interval of the solutions, execute the menu ʺEditʺ ‐ ʺTime Span/Intervalʺ

and check and set the Time Start, Time End and Interval field in ʺTime Span/Intervalʺ dialog.

50
 RTKLIB ver. 2.4.1 Manual

(12) By Executing the menu ʺEditʺ ‐ ʺSolution Sourceʺ, you can view the source of solutions as the text form.

(13) To plot solutions in real‐time, execute the menu ʺFileʺ‐ʺConnection Settingsʺ and set solution

parameters in ʺConnection Settingʺ dialog. You can select Stream Type, Stream Option (Opt), Stream

Commands (Cmd), Solution Format, Time Format, Lat/Lon Format and Field Sep for both of solution‐1

and solution‐2. After setting the connection parameters, execute the menu ʺFileʺ‐ʺConnectʺ or push
button in Tool Bar. To disconnect the external device, execute menu ʺFileʺ‐ʺDisconnectʺ or push connect

button again. For example, if selecting serial as Stream Type and NMEA0183 as Solution Format, you

can monitor external receiverʹs NMEA output in the RTKPLOT window.

51
 RTKLIB ver. 2.4.1 Manual

(14) By pushing Plot... button of RTKNAVI, RTKPLOT automatically runs and connects to the monitor

port of RTKNAVI. If you want to connect to RTKNAVI executed on the remote PC, input the

connection setting like TCP Client as Stream Type, IP address of the remote PC and port number of

monitor port of RTKNAVI and connect to the remote RTKNAVI. In this case, multiple client

connections are allowed.

(15) To plot the RINEX observation data, execute menu ʺFileʺ ‐‐ ʺOpen Obs Dataʺ and select the RINEX

observation and navigation message files. You can select multiple RINEX files. If you do not select the

RINEX navigation message file, RTKPOST reads the observation data file paths with the extension

replaced by .*nav (.obs) or .yyN,.yyG,.yyH,.yyQ (.yyO) as the GPS, GLONASS, SBAS and

QZSS navigation data. If you want read the RINEX navigation message file separately, execute the

menu ʺFileʺ ‐ ʺOpen Nav Messagesʺ. If the input files can be read properly, you can see the satellite

visibility or the observation data availability plot. You can use left‐button or right‐button drag to

change the time span. You can also use some tool buttons in Tool Bar as well as for the solution plot.

52
 RTKLIB ver. 2.4.1 Manual

(16) By selecting the pull down menu in Tool Bar, you can switch the plot to satellite visibility in skyplot

(SkyPlot) or plot of number of visible satellites and DOP (Sats/DOP). You can apply the elevation mask

by reading the elevation mask data by the menu ʺFileʺ ‐ ʺOpen Elev Maskʺ and by set the option ʺ Elev

Mask Patternʺ ON. For the format of the elevation mask data, refer the example file found in

rtklib_<ver>\data\elmask_sample.txt.

53
 RTKLIB ver. 2.4.1 Manual

(17) By Executing the menu ʺEditʺ ‐ ʺObs Data Sourceʺ or ʺObs Data QCʺ, you can view the source of

solutions or the QC result as the text form.

54
 RTKLIB ver. 2.4.1 Manual

(18) To configure the plotting options, execute the menu ʺEditʺ ‐ ʺOptions...ʺ and set the options with the

following ʺOptionsʺ dialog.

Item Descriptions Notes

Time Format Select time format.
Show Statistics Set whether statistics are shown or not.
Set whether cycle‐slip position is shown or not in observation
Cycle‐Slip data display. Cycle‐slips are shown as red vertical lines in the
observation data plot.

55
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Set whether parity unknown status is shown or not in
Parity Unknown observation data display. Parity unknown epochs are shown as
gray vertical lines in the observation data plot.
Set whether ephemeris status is shown or not in observation
data display. Ephemerides are shown as the grey line under the
Ephemeris
observation data plot. Gray dots means the Toe. Red ephemeris
plot means the satellite is unhealthy.
Set the elevation mask angle (deg) for observation data display.
Elevation Mask
The elevation mask is also used for DOP computation.
Set whether low elevation satellites under the elevation mask is
Hide Low Satellite
shown or not.
Maximum DOP Set the y‐axis limit of DOP plot.
Satellite System Select the navigation systems to be plotted.
Set excluded satellites. Fill in the satellite number or ID
Excluded Sats
separated by spaces.
Set whether error bar or error circle is shown or not in solution
Error Bar/Circle
display. You can select Bar/Circle of Dots as the format.
Set whether direction arrow and velocity arrow is shown or not
Direction Arrow
in solution ground track display.
Graph Label Set whether graph labels are shown or not in solution display.
Set whether grid and grid labels are shown or not in solution
Grid/Grid Label
display.
Set whether compass is shown or not in solution ground track
Compass
display.
Set whether scale is shown or not in solution ground track
Scale
display.
Auto Fit Set whether scale is adjusted automatically or not.
Y‐Range (+/‐) Set the range of Y‐axis in solution display.
Set the real‐time plot buffer size in epochs. The older solutions
RT Buffer Size
over the buffer size is deleted in real‐time plot.
Select the origin position of solution display as follows.
‐ Start Pos, End Pos, Average Pos, Linear Fit Pos
‐ Base Station, Lat/Lon/Hgt, Auto Input, Waypoint 1‐10.
If you select Lat/Lon/Height, you have to input latitude,
longitude and ellipsoidal height in the text fields below for the
Coordinate Origin
origin. If selecting Auto Input, receiver ID is assumed as the
4‐charactors of the solution file name head and the position is
read from the position file. The position file can be selected by
pushing ... button and pushing Load button in the position list
dialog.
Set the mark colors for solution No. 1 or observation data in
Mark Color 1 plots. Click color panel right and select color with color
selection dialog.
Mark Color 2 Set the mark colors for solution No. 2 in plots.
Line Color Set the line color in plots.
Text Color Set the text color in plots.
Grid Color Set the grid color in plots.
Background Color Set the background color in plots.
Plot Style Select the plot style in plots.
Mark Size Set the mark size in plots.

56
 RTKLIB ver. 2.4.1 Manual

Item Descriptions Notes

Select the font in plots. Push ... button and select the font with
Font
font selection dialog.
Set the animation interval for solution or observation data
Anim. Interval
display.
Update Cycle (ms) Set the plot update cycle time in ms for real‐time plotting
Set latitude, longitude and height for the origin. Fill in the
Lat/Lon/Hgt
values directly or push ... button and select the station position.
Set QC command and its options for observation data.
As default, TEQC QC mode options are set. The command is
QC Command used for executing the menu ʺEditʺ ‐ ʺObs Data QC...ʺ. The
command must be in the command search path or in the
directory for the RTKLIB executable files.

57
 RTKLIB ver. 2.4.1 Manual

3.8 NTRIP Source Table Browser

NTRIP (Networked Transport of RTCM via Internet Protocol) is a communication protocol to interchange

GPS/GNSS related data such as receiver raw observation data, ephemerides and corrections for DGPS or

RTK‐GPS. NTRIP specifies the table format of so‐called Source Table, which represents contents list of

provided data by NTRIP servers. RTKLIB includes a simple browser for NTRIP Source Tables.

(1) Execute the binary AP file rtklib_<ver>\bin\[Link]. You can see the main window

of NTRIP Source Table Browser.

(2) Push button upper left in the main window, leaving right pull down menu of NTRIP caster list
blank. If the bottom status bar shows ʺconnecting...ʺ and then ʺupdate caster listʺ, the NTRIP caster list

is updated. If the pull down menu is blank, the browser acquires the NTRIP caster list from the default

NTRIP info caster [Link] and update the list. To change the source of the list, fill the

NTRIP caster address as the form of <address>:<port> in the pull down menu and push button.
If you omit port number, the browser uses the default port number 2101.

(3) Select the caster in the pull down menu and push button. If the status bar shows ʺsource table
receivedʺ, the browser properly received a NTRIP Source Table from the selected NTRIP caster and

shows it in the window. The status bar also indicate the error message if a problem arises.

58
 RTKLIB ver. 2.4.1 Manual

(4) By pushing field title, you can sort the list. You also can push STR , CAS , NET , SRC to switch the

contents of the Source Table to Stream List, Caster List, Network List and Original Source Table.

59
 RTKLIB ver. 2.4.1 Manual

3.9 Use Console APs of RTKLIB

RTKLIB includes the following console APs. To execute the APs,

These APs only use standard C functions. So you can rebuild the APs on the non‐Windows environment

like LINUX, UNIX, MAC OS X and so on. RTKLIB also contains standard make environment for gcc. Refer

Appendix A RTKLIB Console AP Commands for detailed the command line options for these APs.

(1) RTKRCV

Real‐time Positioning. The console AP version of RTKNAVI.

(2) RNX2RTKP

Post‐Processing Analysis. The console AP version of RTKPOST.

(3) POS2KML

Google Earth KML converter for solution files.

(4) CONVBIN

RINEX Converter of receiver raw data. The console AP version of RTKCONV.

(5) STR2STR

Stream Server. Console AP version of STRSVR.

60
 RTKLIB ver. 2.4.1 Manual

4 Develop and Link user AP with RTKLIB

RTKLIB provide the following general purpose C‐functions callable from user application program (AP).

User can use these function to develop user original positioning APs.

(1) Matrix and vector functions

(2) Time and string functions

(3) Coordinates transformation and geoid model

(4) Navigation processing

(5) Positioning models (troposphere, ionosphere, antenna PCV)

(6) SBAS DGPS/DGNSS correction

(7) Single point positioning

(8) Carrier‐based and code‐based relative positioning

(9) OTF integer ambiguity resolution

(10) Receiver raw binary data input

(11) Positioning solution/NMEA input/output

(12) RINEX observation data/navigation message input/output

(13) Precise ephemeris input

(14) Stream data communication library

(15) NTRIP (Networked Transport of RTCM via Internet Protocol) library

(16) RTK‐GPS/GNSS positioning server

(17) RTCM 2.3 and 3.0/3.1 message handling

The following instructions shows the way to utilize the library of RTKLIB in user AP.

(1) Add the following include directive to the source program of user AP.
#include "rtklib.h"

(2) Set the following compiler option to add RTKLIB source directory path to compiler include paths.
-I rtklib_<ver>\src

(3) Add the necessary RTKLIB library source files to source programs set for the AP build. Refer Appendix

C Library APIs for detailed library functions and source programs in RTKLIB.

61
 RTKLIB ver. 2.4.1 Manual

Appendix A Console AP Commands

A.1 RTKRCV

SYNOPSIS
rtkrcv [-s][-p port|-d dev][-o file][-t level]

DESCRIPTION
A command line version of the real-time positioning AP by rtklib. To start or stop

RTK server, to configure options or to print solution/status, login a console and

input commands. As default, stdin/stdout are used for the console. Use -p option

for network login with telnet protocol. To show the available commands, type ? or

help on the console. The initial processing options are loaded from default

configuration file [Link]. To change the file, use -o option. To configure

the processing options, edit the configuration file or use set, load or save command

on the console. To shutdown the program, use shutdown command on the console or

send USR2 signal to the process. For configuration file, refer B.4.

OPTIONS
-s start RTK server on program startup

-p port port number for telnet console

-m port port number for monitor stream

-d dev terminal device for console

-o file configuration file

-r level output solution status file (0:off,1:states,2:residuals)

-t level debug trace level (0:off,1-5:on)

COMMANDS
start

Start RTK server. No need the command if the program runs with -s option.

stop

Stop RTK server.

restart

62
 RTKLIB ver. 2.4.1 Manual

Restart RTK server. If the processing options are set, execute the command to enable

the changes.

solution [cycle]

Show solutions. Without option, only one solution is shown. With option, the

soluiton is displayed at intervals of cycle (s). To stop cyclic display, send break

(ctr-C).

status [cycle]

Show RTK status. Use option cycle for cyclic display.

satellite [cycle]

Show satellite status. Use option cycle for cyclic display.

observ [cycle]

Show observation data. Use option cycle for cyclic display.

navidata [cycle]

Show navigation data. Use option cycle for cyclic display.

stream [cycle]

Show stream status. Use option cycle for cyclic display.

error

Show error/warning messages. To stop messages, send break (ctr-C).

option [opt]

Show the values of processing options. Without option, all options are displayed.

With option, only pattern-matched options are displayed.

set opt [val]

Set the value of a processing option to val. With out option val, prompt message

is shown to input the value. The change of the processing option is not enabled

before RTK server is restarted.

load [file]

63
 RTKLIB ver. 2.4.1 Manual

Load processing options from file. Without option, default file [Link] is used.

To enable the changes, restart RTK server.

save [file]

Save current processing optons to file. Without option, default file [Link]

is used.

log [file|off]

Record console log to file. To stop recording the log, use option off.

help|? [path]

Show the command list. With option path, the stream path options are shown.

exit

Exit and logout console. The status of RTK server is not affected by the command.

shutdown

Shutdown RTK server and exit the program.

!command [arg...]

Execute command by the operating system shell. Do not use the interactive command.

NOTES
Short form of a command is allowed. In case of the short form, the command is

distinguished according to header characters.

64
 RTKLIB ver. 2.4.1 Manual

A.2 RNX2RTKP

SYNOPSIS
rnx2rtkp [option ...] file file [...]

DESCRIPTION
Read RINEX OBS/NAV/GNAV/HNAV/CLK, SP3, SBAS message log files and compute receiver

(rover) positions and output position solutions. The first RINEX OBS file shall

contain receiver (rover) observations. For the relative mode, the second RINEX OBS

file shall contain reference (base station) receiver observations. At least one

RINEX NAV/GNAV/HNAV file shall be included in input files. To use SP3 precise

ephemeris, specify the path in the files. The extension of the SP3 file shall be .sp3

or .eph. All of the input file paths can include wild-cards (*). To avoid command",

line deployment of wild-cards, use "..." for paths with wild-cards. Command line

options are as follows ([]:default). With -k option, the processing options are

input from the configuration file. In this case, command line options precede

options in the configuration file. For configuration file, refer B.4.

OPTIONS
-? print help

-k file input options from configuration file [off]

-o output output file [stdout]

-ts ds ts start day/time (ds=y/m/d ts=h:m:s) [obs start time]

-te de te end day/time (de=y/m/d te=h:m:s) [obs end time]

-ti tint time interval (sec) [all]

-p mode mode (0:single,1:dgps,2:kinematic,3:static,4:moving-base

5:fixed,6:ppp-kinematic,7:ppp-static) [2]

-m mask elevation mask angle (deg) [15]

-f freq number of frequencies for relative mode (1:L1,2:L1+L2,3:L1+L2+L5) [2]

-v thres validation threshold for integer ambiguity (0.0:no AR) [3.0]

-b backward solutions [off]

-c forward/backward combined solutions [off]

-i instantaneous integer ambiguity resolution [off]

-h fix and hold for integer ambiguity resolution [off]

-e output x/y/z-ecef position [latitude/longitude/height]

65
 RTKLIB ver. 2.4.1 Manual

-a output e/n/u-baseline [latitude/longitude/height]

-n output NMEA-0183 GGA sentence [latitude/longitude/height]

-g output latitude/longitude in the form of ddd mm [Link]' [[Link]]

-z output height in geodetic height [ellipsoidal]

-t output time in the form of yyyy/mm/dd hh:mm:[Link] [[Link]]

-u output time in utc [gpst]

-d col columns of time under decimal point [3]

-s sep field separator [' ']

-r x y z reference (base) receiver ecef pos (m) [average of single pos]

-l lat lon hgt reference (base) receiver latitude/longitude/height (deg/m)

-y level output solution status (0:off,1:states,2:residuals) [0]

-x level debug trace level (0:off) [0]

EXAMPLES
Example 1. Kinematic Positioning, L1+L2, output Latitude/Longitude/Height to

STDOUT.

> rnx2rtkp 07590920.05o 30400920.05o 30400920.05n

Example 2. Single Point Positioning, El Mask=15deg, output NMEA GGA to file [Link]

> rnx2rtkp -p 0 -m 15 -n -o [Link] 07590920.05o 30400920.05n

Example 3. Static Positioning, L1, time form yyyy/mm/dd hh:mm:ss, output X/Y/Z-ECEF

positions

> rnx2rtkp -p 3 -f 1 -t -e 07590920.05o 30400920.05o 30400920.05n

Example 4. Kinematic Positioning, Instantaneous AR, validation threshold=2, comma

separator

> rnx2rtkp -i -v 2 -s , 07590920.05o 30400920.05o 30400920.05n

66
 RTKLIB ver. 2.4.1 Manual

A.3 POS2KML

SYNOPSIS
pos2kml [option ...] file [...]

DESCRIPTION
Read position file(s) and convert it to Google Earth KML file. Each line in the

input file shall contain fields of time, position fields (Latitude/Longitude/Height

or X/Y/Z-ECEF), and Quality flag (option). The line started with '%', '#', ';' is

treated as comment. Command options are as follows. ([]:default)

OPTIONS
-h print help

-o file output file [infile + .kml]

-c color track color

(0:off,1:white,2:green,3:orange,4:red,5:yellow) [5]

-p color point color

(0:off,1:white,2:green,3:orange,4:red,5:by qflag) [5]

-a output altitude information [off]

-ag output geodetic altitude [off]

-tg output time stamp of gpst [off]

-tu output time stamp of utc [gpst]

-i tint output time interval (s) (0:all) [0]

-q qflg output q-flags (0:all) [0]

-f n e h add north/east/height offset to position (m) [0 0 0]

67
 RTKLIB ver. 2.4.1 Manual

A.4 CONVBIN

SYNOPSIS
convbin [-ts y/m/d h:m:s] [-te y/m/d h:m:s] [-ti tint] [-r format] [-ro opts]

[-f freq] [-hc comment] [-hm marker] [-hn markno] [-ht marktype]

[-ho observ] [-hr rec] [-ha ant] [-hp pos] [-hd delta] [-v ver] [-od]

[-os] [-x sat] [-y sys] [-d dir] [-c satid] [-o ofile] [-n nfile]

[-g gfile] [-h hfile] [-q qfile] [-s sfile] file

DESCRIPTION
Convert RTCM, receiver raw data log and RINEX file to RINEX and SBAS/LEX

message file. SBAS message file complies with RTKLIB SBAS/LEX messsage

format. It supports the following messages or files.

RTCM 2 : Type 1, 3, 9, 14, 16, 17, 18, 19, 22

RTCM 3 : Type 1002, 1004, 1005, 1006, 1010, 1012, 1019, 1020

NovAtel OEMV/4,OEMStar: RANGECMPB, RANGEB, RAWEPHEMB, IONUTCB, RAWWASSFRAMEB

NovAtel OEM3 : RGEB, REGD, REPB, FRMB, IONB, UTCB

u-blox LEA-4T/LEA-5T : RXM-RAW, RXM-SFRB

NovAtel Superstar II : ID#20, ID#21, ID#22, ID#23, ID#67

Hemisphere : BIN76, BIN80, BIN94, BIN95, BIN96

SkyTraq S1315F : msg0xDD, msg0xE0, msg0xDC

Furuno GW-10-II/III : msg0x08, msg0x03, msg0x27, msg0x20

Javad GRIL/GREIS : [R*],[r*],[*R],[*r],[P*],[p*],[*P],[*p],[D*],[*d]

[E*],[*E],[F*],[TC],[GE],[NE],[EN],[QE],[UO],[IO]

[WD]

RINEX : OBS

If any output file specified, default output files (<file>.obs,

<file>.nav, <file>.gnav, <file>.hnav, <file>.qnav and <file>.sbs) are used.

If receiver type is not specified, type is recognized by the input

file extension as follows.

*.rtcm2 RTCM 2

*.rtcm3 RTCM 3

68
 RTKLIB ver. 2.4.1 Manual

*.gps NovAtel OEMV/4,OEMStar

*.ubx u-blox LEA-4T/LEA-5T

*.log NovAtel Superstar II

*.bin Hemisphere Eclipse/Crescent

*.stq SkyTraq S1315F

*.jps Javad

*.obs,*.*o RINEX OBS

OPTIONS
file input receiver binary log file

-ts y/m/d h:m:s start time [all]

-te y/m/d h:m:s end time [all]

-tr y/m/d h:m:s approximated time for RTCM messages

-ti tint observation data interval (s) [all]

-r format log format type

rtcm2= RTCM 2

rtcm3= RTCM 3

nov = NovAtel OEMV/4,OEMStar

oem3 = NovAtel OEM3

ubx = ublox LEA-4T,5T,6T

ss2 = NovAtel Superstar II

hemis= Hemisphere Eclipse/Crescent

stq = SkyTraq S1315F

javad= Javad GRIL/GREIS

rinex= RINEX OBS

-ro opt receiver options

-f freq number of frequencies [2]

-hc comment rinex header: comment line

-hm marker rinex header: marker name

-hn markno rinex header: marker number

-ht marktype rinex header: marker type

-ho observ rinex header: observer name and agency separated by /

-hr rec rinex header: receiver number, type and version separated by /

-ha ant rinex header: antenna number and type separated by /

-hp pos rinex header: approx position x/y/z separated by /

-hd delta rinex header: antenna delta h/e/n separated by /

69
 RTKLIB ver. 2.4.1 Manual

-v ver rinex version [2.10]

-od include doppler frequency [off]

-os include snr [off]

-x sat exclude satellite

-y sys exclude systems (G:GPS,R:GLONASS,E:Galileo,J:QZSS,S:SBAS)

-d dir output directory [same as input file]

-c staid use RINEX file name convention with staid [off]

-o ofile output RINEX OBS file

-n nfile output RINEX NAV file

-g gfile output RINEX GNAV file

-h hfile output RINEX HNAV file

-q qfile output RINEX QNAV file

-s sfile output SBAS message file

70
 RTKLIB ver. 2.4.1 Manual

A.5 STR2STR

SYNOPSIS
str2str -in stream -out stream [-out stream...] [options]

DESCRIPTION
Input data from a stream and divide and output them to multiple streams. The input

stream can be serial, TCP client, TCP server, NTRIP client, or file. The output

stream can be serial, TCP client, TCP server, NTRIP server, or file. str2str is

a resident type application. To stop it, type ctr-c in console if run foreground

or send signal SIGINT for background process.

OPTIONS
-in stream input stream path

-out stream output stream path

serial://port[:brate[:bsize[:parity[:stopb[:fctr]]]]]

tcpsvr://:port

tcpcli://addr[:port]

ntrip://[user[:passwd]@]addr[:port][/mntpnt]

ntrips://[user[:passwd]@]addr[:port][/mntpnt[:str]]

[Link]

-d msec status display interval (ms) [5000]

-s msec timeout time (ms) [10000]

-r msec reconnect interval (ms) [10000]

-n msec NMEA request cycle (m) [0]

-f sec file swap margin (s) [30]

-c file receiver commands file [no]

-p lat lon NMEA position (latitude/longitude) (deg)

-l local_dir ftp/http local directory []

-x proxy_addr http/ntrip proxy address [no]

-t level trace level [0]

-h print help

71
 RTKLIB ver. 2.4.1 Manual

Appendix B File Formats

B.1 Positioning Solution File

DESCRIPTION

A positioning solution file is just a text file as output of RTKNAVI or RTKPOST. The file is separated to

records or lines by CR/LF. Each records consists of fields. The following table shows the format of the

positioning solution file.

No Record/Field Description Notes

The lines starting with ʺ%ʺ are header lines. The header lines
contains some additional information or processing options as
follows.
% program : program version
% inp file : Input file path
% obs start: Observation data start time in GPS time
% obs end: Observation data end time in GPS time
% pos mode: Positioning mode option
1 File header % freqs: Frequencies option
% solution: Solution type option
% elev mask: Elevation mask angle option
% snr mask: SNR mask option
% ionos est: Ionospheric parameter estimation option
% tropos est: Tropospheric parameters estimation option
% amb res: Integer ambiguity resolution options
% val thres: Integer ambiguity validation option
% ref pos: position of the antenna of the base station
Field indicator starting with ʺ%ʺ line follows after File header.
2 Field indicator To recognize the field formats, RTKLIB uses these lines. Do not
delete them.
Solution body consists of the following fields.
3 Solution body
The field contents are varied according to the positioning options.
The epoch time of the solution indicating the true receiver signal
reception time (not indicates the time by receiver clock). The format
is varied to the options.

yyyy/mm/dd HH:MM:[Link] :
(1) Time Calendar time in GPST, UTC or JST, the time system is indicated in
Field indicator

WWWW [Link] :
GPS week and TOW (time of week) in seconds.

The rover receive antenna or marker position estimated varied

Receiver
(2) according to the positioning options.
Position

72
 RTKLIB ver. 2.4.1 Manual

No Record/Field Description Notes

+[Link] +[Link] [Link] :

Latitude, longitude in degrees and height in m. Minus value means
south latitude or west longitude. The height indicates ellipsoidal or
geodetic according to the positioning options.

+ddd mm [Link] +ddd mm [Link] [Link] :

Latitude, longitude in degree, minute and second and height in m.

+[Link] +[Link] +[Link] :

X/Y/Z components of ECEF frame in m.

+[Link] +[Link] +[Link] :

E/N/U components of baseline vector in m. The local coordinate is
referenced to the rover position.
The flag which indicates the solution quality.
1 : Fixed, solution by carrier‐based relative positioning and the
integer ambiguity is properly resolved.
2 : Float, solution by carrier‐based relative positioning but the
Quality flag
(3) integer ambiguity is not resolved.
(Q)
3 : Reserved
4 : DGPS, solution by code‐based DGPS solutions or single point
positioning with SBAS corrections
5 : Single, solution by single point positioning
Number of
(4) valid satellites The number of valid satellites for solution estimation.
(ns)
The estimated standard deviations of the solution assuming a priori
error model and error parameters by the positioning options.
Standard
The sdn, sde or sdu means N (north), E (east) or U (up)
deviations
component of the standard deviations in m. The absolute value of
(5) (sdn, sde, sdu,
sdne, sdeu or sdun means square root of the absolute value of NE,
sdne, sdeu,
EU or UN component of the estimated covariance matrix. The sign
sdun)
represents the sign of the covariance. With all of the values, user can
reconstruct the full covariance matrix.
Age of
The time difference between the observation data epochs of the
(6) differential
rover receiver and the base station in second.
(age)
The ratio factor of ʺratio‐testʺ for standard integer ambiguity
Ratio factor validation strategy. The value means the ratio of the squared sum of
(7)
(ratio) the residuals with the second best integer vector to with the best
integer vector.

EXAMPLE

% program : RTKLIB ver.2.3.0b

% inp file : G:\rtklibtest\20090831\omre196a.09o
% inp file : G:\rtklibtest\20090831\tevc196a.09o
% inp file : G:\rtklibtest\20090831\omre196a.09n
% obs start : 2009/07/15 07:10:00.0 GPST (week1540 285000.0s)
% obs end : 2009/07/15 07:59:50.0 GPST (week1540 287990.0s)
% pos mode : kinematic
% freqs : L1+L2

73
 RTKLIB ver. 2.4.1 Manual
% solution : forward
% elev mask : 15.0 deg
% snr mask : 0.0 dBHz
% ionos est : on
% tropo est : on
% amb res : continuous
% val thres : 3.0
% ref pos : 32.574831620 -117.126551777 -28.1471
%
% (lat/lon/height=WGS84/ellipsoidal,Q=1:fix,2:float,4:dgps,5:single,ns=# of satellites)
% GPST latitude(deg) longitude(deg) height(m) Q ns sdn(m) sde(m)
sdu(m) sdne(m) sdeu(m) sdun(m) age(s) ratio
2009/07/15 07:10:00.000 32.560273272 -116.953525346 118.6783 1 10 0.0186 0.0202
0.0899 -0.0072 0.0089 -0.0249 0.00 4.5
2009/07/15 07:10:10.000 32.560273266 -116.953525340 118.6877 1 10 0.0144 0.0154
0.0776 -0.0058 0.0082 -0.0199 0.00 5.3
2009/07/15 07:10:20.000 32.560273262 -116.953525365 118.6853 1 10 0.0124 0.0131
0.0720 -0.0051 0.0078 -0.0173 0.00 5.3
2009/07/15 07:10:30.000 32.560273251 -116.953525345 118.6825 1 10 0.0111 0.0117
0.0686 -0.0046 0.0075 -0.0157 0.00 5.6
2009/07/15 07:10:40.000 32.560273275 -116.953525412 118.6827 1 10 0.0103 0.0108
0.0662 -0.0043 0.0073 -0.0146 0.00 4.7
2009/07/15 07:10:50.000 32.560273277 -116.953525429 118.6812 1 10 0.0097 0.0102
0.0644 -0.0041 0.0071 -0.0138 0.00 4.1
2009/07/15 07:11:00.000 32.560273249 -116.953525449 118.6817 1 10 0.0092 0.0097
0.0630 -0.0039 0.0069 -0.0132 0.00 4.2
2009/07/15 07:11:10.000 32.560273271 -116.953525464 118.6729 1 10 0.0088 0.0093
0.0618 -0.0038 0.0067 -0.0127 0.00 5.2
2009/07/15 07:11:20.000 32.560273246 -116.953525468 118.6772 1 10 0.0085 0.0089
0.0607 -0.0037 0.0066 -0.0123 0.00 6.1
2009/07/15 07:11:30.000 32.560273219 -116.953525461 118.6733 1 10 0.0083 0.0087
0.0598 -0.0036 0.0065 -0.0119 0.00 7.9
2009/07/15 07:11:40.000 32.560273216 -116.953525478 118.6771 1 10 0.0081 0.0085
0.0590 -0.0035 0.0064 -0.0117 0.00 9.0
2009/07/15 07:11:50.000 32.560273206 -116.953525489 118.6726 1 10 0.0079 0.0083
0.0582 -0.0035 0.0062 -0.0114 0.00 8.6
2009/07/15 07:12:00.000 32.560273201 -116.953525497 118.6744 1 10 0.0078 0.0081
0.0575 -0.0034 0.0061 -0.0112 0.00 7.5
2009/07/15 07:12:10.000 32.560273212 -116.953525455 118.6731 1 10 0.0077 0.0080
0.0568 -0.0034 0.0060 -0.0110 0.00 7.9

74
 RTKLIB ver. 2.4.1 Manual

B.2 SBAS Log File

DESCRIPTION

A SBAS log file is output of RTKCONV, that is a text file in which a line contains a SBAS message captured

by the GPS/GNSS receiver. The following table shows the format of the SBAS log file.

No Record/Field Description Notes

SBAS A line contains a SBAS navigation data frame, which consists of the
1
messages following fields.
GPS week
(1) GPS week number of SBAS navigation data frame.
number
(2) Time of week Time of week of SBAS navigation data frame in seconds.
(3) PRN number PRN number of SBAS satellite transmitting the navigation data
The type ID of the SBAS message in the frame (0 ‐ 63). Refer SBAS
specifications for details:
(4) Message type RTCA/DO‐229C, Minimum operational performance standards for
Global Positioning System/Wide Area Augmentation system
airborne equipment
(5) Separator :
Hexadecimal dump of a 226‐bit SBAS message without 24‐bit
(6) SBAS message parity field. The message tail is 0‐padded to align to 8‐bit boundary.
Refer SBAS specifications for the detailed message format.

EXAMPLE

1471 349007 137 25 : C666A0A7F1FE6000027F80000003468000000000000000000000000000

1471 349007 129 25 : C666A0A7F4FE6004047F80000003468000000000000000000000000000
1471 349008 129 4 : 53109FFFFF5FFDFFDFFDFFFFC7FA9FFDFFDFFDFFDFFF9BBBBB33FFFFC0
1471 349008 137 4 : 53129FFC001FFDFFDFFDFFFFA0009FFDFFDFFDFFDFFF9BBBBB33FFFFC0
1471 349009 137 3 : 9A0C9FFDFFDFFFFFDFFC017FF9FFDFFC009FFC015FFFBB97B9BB9FBB80
1471 349009 129 2 : 9A0A9FFFFC9FFFFE9FFDFFDFFDFFDFFDFFFFF7F93FFBE79BBBBBB9FA00
1471 349010 137 2 : C60A9FFFFD1FFFFFDFFDFFDFFDFFDFFDFFC003F88003E79FBBFBB9FA00
1471 349010 129 3 : C60E9FFDFFDFFFFE9FFC007FEDFFDFFFFFDFFFFFDFFFBB97B9BB9FBB80
1471 349011 137 26 : 536A0029E0EF0FF05F829C11C076033015A09D047037C1DE14F08FE000
1471 349011 129 26 : 536A0821A0DD05E82B813E0EF0F7897C27C12E08683B419C0BE057E000
1471 349012 137 28 : 9A723440E44E810029FF1F1F379C0BC35D4BE2B8078F15903253960200
1471 349012 129 28 : 9A722CB5D8739087B46B107DA8D9E828694B55F843782100AF146AD980
1471 349013 129 9 : C62434198D3F5D92BA855704800236DFE84FE06FFA47FE7FF0008E0240
1471 349013 137 9 : C6260C198D32310732404C1D40183CDFD187C8F3FF7FFD800FF7D6BE40
1471 349014 129 4 : 53119FFFFF9FFDFFDFFDFFFFD3FA5FFDFFDFFDFFDFFF9BBBBB33FFFFC0
1471 349014 137 4 : 53109FFC005FFDFFDFFDFFFFAFFFDFFDFFDFFDFFDFFF9BBBBB33FFFFC0
1471 349015 129 2 : 9A089FFFFC5FFFFEDFFDFFDFFDFFDFFDFFFFFBF8FFFFE79BBBBBB9FA00
1471 349015 137 3 : 9A0D9FFDFFDFFFFF9FFC017FFDFFDFFC00DFFC015FFFBB97B9BB9FBB80
1471 349016 137 2 : C6089FFFFD5FFC001FFDFFDFFDFFDFFDFFFFFFF8BFFFE79FBBFBB9FA00
1471 349016 129 3 : C60C9FFDFFDFFFFE5FFC007FF1FFDFFC001FFFFFDFFFBB97B9BB9FBB80
1471 349017 137 25 : 5366587803FE3FF0010080FFFF835E8000000000000000000000000000
1471 349017 129 25 : 5366587FFDFEDFF40400800000035E8000000000000000000000000000
1471 349018 129 63 : 9AFC000000000000000000000000000000000000000000000000000000
1471 349018 137 63 : 9AFC000000000000000000000000000000000000000000000000000000
1471 349019 129 26 : C66A0C53E26F09704781DC0DE06702FC19E1EF09F047821C0EF05FE000
1471 349019 137 26 : C66A0431E17E0A704741F80DC05E827815C0EF09F877C2FC15E096E000
1471 349020 137 4 : 53119FFC001FFDFFDFFDFFFF9C001FFDFFDFFDFFDFFF9BBBBB33FFFFC0
1471 349020 129 4 : 53129FFFFF5FFDFFDFFDFFFFC3FA9FFDFFDFFDFFDFFF9BBBBB33FFFFC0

75
 RTKLIB ver. 2.4.1 Manual

B.3 Solution Status File

DESCRIPTION

A solution status file is output of RTKNAVI or RTKPOST, that is a text file which contains the internal status

of the positioning process. The internal status include estimated states of Kalman filter and residuals of

measurements to analyze the solution quality. The following table shows the format of the solution status

file.

No Record/Field Description Notes

Estimated rover position in the filter. The format of a record is as

follows.

$POS,week,tow,stat,posx,posy,posz,posxf,posyf,poszf
1 Position States
week/tow : gps week no/time of week (s)
stat : solution status
posx/posy/posz : position x/y/z ecef (m) float
posxf/posyf/poszf : position x/y/z ecef (m) fixed
Estimated rover velocity and acceleration in the filter. The format of
a record is as follows.

$VELACC,week,tow,stat,vele,veln,velu,acce,accn,accu,velef,velnf,\
Velocity/ veluf,accef,accnf,accuf
2 Acceleration week/tow : gps week no/time of week (s)
States stat : solution status
vele/veln/velu : velocity e/n/u (m/s) float
acce/accn/accu : acceleration e/n/u (m/s^2) float
velef/velnf/veluf : velocity e/n/u (m/s) fixed
accef/accnf/accuf : acceleration e/n/u (m/s^2) fixed
Estimated ionosphere parameter (vertical L1 ionosphere delay
difference). The format of a record is as follows.

$ION,week,tow,stat,sat,az,el,ion,ion‐fixed
Ionosphere
week/tow : gps week no/time of week (s)
3 Parameter
stat : solution status
States
sat : satellite id
az/el : azimuth/elevation angle(deg)
ion : vertical ionospheric delay L1 (m) float
ion‐fixed: vertical ionospheric delay L1 (m) fixed
Estimated troposphere parameter (vertical troposphere delay
residual). The format of a record is as follows.

Troposphere
$TROP,week,tow,stat,rcv,ztd,ztdf
4 Parameter
week/tow : gps week no/time of week (s)
States
stat : solution status
rcv : receiver (1:rover,2:base station)
ztd : zenith total delay (m) float

76
 RTKLIB ver. 2.4.1 Manual

No Record/Field Description Notes

ztdf : zenith total delay (m) fixed

Estimated GLONASS receiver H/W bias difference. The format of a
record is as follows.

$HWBIAS,week,tow,stat,frq,bias,biasf
Receiver H/W
5 week/tow : gps week no/time of week (s)
bias States
stat : solution status
frq : frequency (1:L1,2:L2,3:L5,...)
bias : h/w bias coefficient (m/MHz) float
biasf : h/w bias coefficient (m/MHz) fixed
Residuals of pseudorange and carrier‐phase observables. The
format of a record is as follows.

$SAT,week,tow,sat,frq,az,el,resp,resc,vsat,snr,fix,slip,lock,outc,\
slipc,rejc
week/tow : gps week no/time of week (s)
sat/frq : satellite id/frequency (1:L1,2:L2,3:L5,...)
az/el : azimuth/elevation angle (deg)
resp : pseudorange residual (m)
6 Residuals
resc : carrier‐phase residual (m)
vsat : valid data flag (0:invalid,1:valid)
snr : signal strength (dbHz)
fix : ambiguity flag (0:no data,1:float,2:fixed,3:hold)
slip : cycle‐slip flag (bit1:slip,bit2:parity unknown)
lock : carrier‐lock count
outc : data outage count
slipc : cycle‐slip count
rejc : data reject (outlier) count

EXAMPLE
$POS,1557,432000.000,2,-3869295.9628,3436570.2567,3717367.6546,0.0000,0.0000,0.0000
$HWBIAS,1557,432000.000,2,1,-0.3503,0.0000
$HWBIAS,1557,432000.000,2,2,0.0108,0.0000
$SAT,1557,432000.000,3,1,253.2,64.3,0.3219,-0.0006,1,48,1,1,1,0,1,0
$SAT,1557,432000.000,3,2,253.2,64.3,-0.0629,-0.0006,1,33,1,1,1,0,1,0
$SAT,1557,432000.000,13,1,298.4,24.1,-0.6732,0.0003,1,42,1,1,1,0,1,0
$SAT,1557,432000.000,13,2,298.4,24.1,0.8081,0.0003,1,17,1,1,1,0,1,0
$SAT,1557,432000.000,16,1,42.0,59.5,0.5037,-0.0005,1,47,1,1,1,0,1,0
$SAT,1557,432000.000,16,2,42.0,59.5,-0.5170,-0.0005,1,30,1,1,1,0,1,0
$SAT,1557,432000.000,19,1,229.8,39.0,-0.1948,-0.0003,1,44,1,0,1,0,0,0
$SAT,1557,432000.000,19,2,229.8,39.0,-0.0806,-0.0003,1,28,1,1,1,0,1,0
$SAT,1557,432000.000,21,1,61.1,28.1,-1.0704,0.0001,1,41,1,1,1,0,1,0
$SAT,1557,432000.000,21,2,61.1,28.1,1.0139,0.0001,1,19,1,1,1,0,1,0
$SAT,1557,432000.000,23,1,257.9,29.9,-1.3258,-0.0000,1,45,1,1,1,0,1,0
$SAT,1557,432000.000,23,2,257.9,29.9,0.4155,0.0000,1,23,1,1,1,0,1,0
$SAT,1557,432000.000,25,1,317.0,24.7,0.8868,0.0002,1,41,1,1,1,0,1,0
$SAT,1557,432000.000,25,2,317.0,24.7,0.1811,0.0003,1,19,1,1,1,0,1,0
$SAT,1557,432000.000,31,1,145.1,32.5,0.6140,-0.0001,1,44,1,1,1,0,1,0
$SAT,1557,432000.000,31,2,145.1,32.5,-0.2397,-0.0001,1,26,1,1,1,0,1,0
$SAT,1557,432000.000,R9,1,105.7,78.1,-0.1172,-0.0001,1,45,1,1,1,0,1,0
$SAT,1557,432000.000,R9,2,105.7,78.1,0.0000,0.0000,0,0,0,0,0,1,0,0
$SAT,1557,432000.000,R10,1,331.5,41.7,-0.1425,0.0002,1,43,1,1,1,0,1,0
$SAT,1557,432000.000,R10,2,331.5,41.7,0.0349,0.0001,1,30,1,1,1,0,1,0
$SAT,1557,432000.000,R19,1,18.6,61.2,-0.7708,-0.0000,1,46,1,1,1,0,1,0
$SAT,1557,432000.000,R19,2,18.6,61.2,0.1898,-0.0001,1,39,1,0,1,0,0,0
$SAT,1557,432000.000,R20,1,235.7,55.6,1.0305,-0.0000,1,42,1,1,1,0,1,0
$SAT,1557,432000.000,R20,2,235.7,55.6,-0.2247,-0.0001,1,39,1,1,1,0,1,0

77
 RTKLIB ver. 2.4.1 Manual

B.4 Configuration File

DESCRIPTION

A configuration file containing processing options, solution options and file

options for RTKNAVI, RTKPOST, RTKRCV and RNX2RTKP. That is a text file which contains

the Keyword = Value form records indicating the various options. The line starting

with # and the texts after # in a line are treated as comments. For the contents

of the configuration file, refer 3.5.

EXAMPLE

# RTKNAVI options (2011/06/11 12:06:52, v.2.4.1)

pos1-posmode =single #
(0:single,1:dgps,2:kinematic,3:static,4:movingbase,5:fixed,6:ppp-kine,7:ppp-static)
pos1-frequency =l1+l2 # (1:l1,2:l1+l2,3:l1+l2+l5,4:l1+l2+l5+l6,5:l1+l2+l5+l6+l7)
pos1-soltype =forward # (0:forward,1:backward,2:combined)
pos1-elmask =15 # (deg)
pos1-snrmask =0 # (dBHz)
pos1-dynamics =off # (0:off,1:on)
pos1-tidecorr =off # (0:off,1:on)
pos1-ionoopt =brdc #
(0:off,1:brdc,2:sbas,3:dual-freq,4:est-stec,5:ionex-tec,6:qzs-brdc,7:qzs-lex,8:vtec_sf,9
:vtec_ef,10:gtec)
pos1-tropopt =saas # (0:off,1:saas,2:sbas,3:est-ztd,4:est-ztdgrad)
pos1-sateph =brdc # (0:brdc,1:precise,2:brdc+sbas,3:brdc+ssrapc,4:brdc+ssrcom)
pos1-exclsats = # (prn ...)
pos1-navsys =1 # (1:gps+2:sbas+4:glo+8:gal+16:qzs+32:comp)
pos2-armode =continuous # (0:off,1:continuous,2:instantaneous,3:fix-and-hold)
pos2-gloarmode =off # (0:off,1:on,2:autocal)
pos2-arthres =3
pos2-arlockcnt =0
pos2-arelmask =0 # (deg)
pos2-arminfix =10
pos2-elmaskhold =0 # (deg)
pos2-aroutcnt =5
pos2-maxage =30 # (s)
pos2-slipthres =0.05 # (m)
pos2-rejionno =30 # (m)
pos2-rejgdop =30
pos2-niter =1
pos2-baselen =0 # (m)
pos2-basesig =0 # (m)
out-solformat =llh # (0:llh,1:xyz,2:enu,3:nmea)
out-outhead =off # (0:off,1:on)
out-outopt =off # (0:off,1:on)
out-timesys =gpst # (0:gpst,1:utc,2:jst)
out-timeform =hms # (0:tow,1:hms)
out-timendec =3
out-degform =deg # (0:deg,1:dms)
out-fieldsep =
out-height =ellipsoidal # (0:ellipsoidal,1:geodetic)
out-geoid =internal # (0:internal,1:egm96,2:egm08_2.5,3:egm08_1,4:gsi2000)
out-solstatic =all # (0:all,1:single)
out-nmeaintv1 =0 # (s)
out-nmeaintv2 =0 # (s)
out-outstat =off # (0:off,1:state,2:residual)
stats-eratio1 =100
stats-eratio2 =100

78
 RTKLIB ver. 2.4.1 Manual
stats-errphase =0.003 # (m)
stats-errphaseel =0.003 # (m)
stats-errphasebl =0 # (m/10km)
stats-errdoppler =1 # (Hz)
stats-stdbias =30 # (m)
stats-stdiono =0.03 # (m)
stats-stdtrop =0.3 # (m)
stats-prnaccelh =10 # (m/s^2)
stats-prnaccelv =10 # (m/s^2)
stats-prnbias =0.0001 # (m)
stats-prniono =0.001 # (m)
stats-prntrop =0.0001 # (m)
stats-clkstab =5e-12 # (s/s)
ant1-postype =llh # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm)
ant1-pos1 =90 # (deg|m)
ant1-pos2 =0 # (deg|m)
ant1-pos3 =-6335367.62849036 # (m|m)
ant1-anttype =
ant1-antdele =0 # (m)
ant1-antdeln =0 # (m)
ant1-antdelu =0 # (m)
ant2-postype =llh # (0:llh,1:xyz,2:single,3:posfile,4:rinexhead,5:rtcm)
ant2-pos1 =90 # (deg|m)
ant2-pos2 =0 # (deg|m)
ant2-pos3 =-6335367.62849036 # (m|m)
ant2-anttype =
ant2-antdele =0 # (m)
ant2-antdeln =0 # (m)
ant2-antdelu =0 # (m)
misc-timeinterp =off # (0:off,1:on)
misc-sbasatsel =0 # (0:all)
file-satantfile =
file-rcvantfile =
file-staposfile =
file-geoidfile =
file-ionofile =
file-dcbfile =
file-tempdir =C:\Temp
file-geexefile =
file-solstatfile =
file-tracefile =
#

inpstr1-type =off #
(0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,7:ntripcli,8:ftp,9:http)
inpstr2-type =off #
(0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,7:ntripcli,8:ftp,9:http)
inpstr3-type =off #
(0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,7:ntripcli,8:ftp,9:http)
inpstr1-path =
inpstr2-path =
inpstr3-path =
inpstr1-format =rtcm2 #
(0:rtcm2,1:rtcm3,2:oem4,3:oem3,4:ubx,5:ss2,6:hemis,7:skytraq,8:gw10,9:javad,15:sp3)
inpstr2-format =rtcm2 #
(0:rtcm2,1:rtcm3,2:oem4,3:oem3,4:ubx,5:ss2,6:hemis,7:skytraq,8:gw10,9:javad,15:sp3)
inpstr3-format =rtcm2 #
(0:rtcm2,1:rtcm3,2:oem4,3:oem3,4:ubx,5:ss2,6:hemis,7:skytraq,8:gw10,9:javad,15:sp3)
inpstr2-nmeareq =off # (0:off,1:latlon,2:single)
inpstr2-nmealat =0 # (deg)
inpstr2-nmealon =0 # (deg)
outstr1-type =off # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr)
outstr2-type =off # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr)
outstr1-path =
outstr2-path =
outstr1-format =llh # (0:llh,1:xyz,2:enu,3:nmea)
outstr2-format =llh # (0:llh,1:xyz,2:enu,3:nmea)
logstr1-type =off # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr)
logstr2-type =off # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr)
logstr3-type =off # (0:off,1:serial,2:file,3:tcpsvr,4:tcpcli,6:ntripsvr)
logstr1-path =
logstr2-path =

79
 RTKLIB ver. 2.4.1 Manual
logstr3-path =
misc-svrcycle =10 # (ms)
misc-timeout =10000 # (ms)
misc-reconnect =10000 # (ms)
misc-nmeacycle =5000 # (ms)
misc-buffsize =32768 # (bytes)
misc-navmsgsel =all # (0:all,1:rover,2:base,3:corr)
misc-proxyaddr =
misc-fswapmargin =30 # (s)

80
 RTKLIB ver. 2.4.1 Manual

Appendix C Library APIs (Application Program Interfaces)

The following table shows the list of RTKLIB library functions. For detailed API (calling convention,

description of the function, input and output parameters and types, return value and type) for a library

function, refer the header comment of each function in the source program in rtklib_<ver>\src. The

definition of data types regarding to the APIs, refer the header file rtklib.h in rtklib_<ver>\src.

(Not updated for v.2.4.1.)

RTKLIB API FUNCTION LIST ( *: added in ver. 2.4.1, **: modified in ver. 2.4.1)
Function Description Source Program

Satellite number/system functions

satno() Satellite system and PRN/slot number to satellite number rtkcmn.c
satsys() Satellite number to satellite system rtkcmn.c
satid2no() Satellite ID to satellite number rtkcmn.c
satno2id() Satellite number to satellite ID rtkcmn.c
obs2code() Observation type string to observation code rtkcmn.c
code2obs() Observation code to observation code string rtkcmn.c
Matrix and vector functions
mat() New matrix rtkcmn.c
imat() New integer matrix rtkcmn.c
zeros() New zero matrix rtkcmn.c
eye() New identity matrix rtkcmn.c
dot() Inner Product rtkcmn.c
norm() Euclid norm rtkcmn.c
cross3() Outer product of 3D vector rtkcmn.c
normv3() normalize 3D vector rtkcmn.c
matcpy() Copy matrix rtkcmn.c
matmul() Multiply matrix rtkcmn.c
matinv() Inverse of matrix rtkcmn.c
solve() Solve linear equation rtkcmn.c
lsq() Least square estimation rtkcmn.c
filter() Kalman filter state update rtkcmn.c
smoother() Kalman smoother rtkcmn.c
matprint() Print matrix rtkcmn.c
matfprint() Print matrix to file rtkcmn.c
Time and string functions
str2num() String to number rtkcmn.c
str2time() String to time rtkcmn.c
time2str() Time to string rtkcmn.c
epoch2time() Calendar day/time to time rtkcmn.c
time2epoch() Time to calendar day/time rtkcmn.c
gpst2time() GPSTIME to time rtkcmn.c
time2gpst() Time to GPSTIME rtkcmn.c
gst2time() Galileo System Time to time rtkcmn.c

81
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

time2gst() Time to Galileo System Time rtkcmn.c
time_str() Get Time String rtkcmn.c
timeadd() Add time rtkcmn.c
timediff() Time difference rtkcmn.c
gpst2utc() GPS Time to UTC rtkcmn.c
utc2gpst() UTC to GPS Time rtkcmn.c
timeget() Get current time in UTC rtkcmn.c
timeset() Set current time in UTC rtkcmn.c
time2doy() Time to Day of Year rtkcmn.c
adjgpsweek() Adjust GPS week number rtkcmn.c
tickget() Get current tick time rtkcmn.c
sleepms() Sleep for milliseconds rtkcmn.c
reppath() Replace file path rtkcmn.c
reppaths() Replace file paths rtkcmn.c

Coordinates functions
ecef2pos() ECEF to geodetic position rtkcmn.c
pos2ecef() Geodetic to ECEF position rtkcmn.c
ecef2enu() ECEF to local coordinates rtkcmn.c
enu2ecef() Local to ECEF coordinates rtkcmn.c
covenu() Covariance in local coordinates rtkcmn.c
covecef() Covariance in ECEF coordinates rtkcmn.c
xyz2enu() ECEF to ENU local coordinate transformation matrix rtkcmn.c
eci2ecef() ECI to ECEF transformation matrix preceph.c
deg2dms() Convert degree to deg‐min‐sec rtkcmn.c
dms2deg() Convert deg‐min‐sec to degree rtkcmn.c

Input/output functions
readpos() Read station positions rtkcmn.c
sortobs() Sort observation data rtkcmn.c
uniqnav() Delete duplicated ephemerides in navigation data rtkcmn.c *
screent() Screen data by time and interval rtkcmn.c
readnav() Read navigation data from file rtkcmn.c
savenav() Save navigation data to file rtkcmn.c
freeobs() Free memory for observation data rtkcmn.c *
freenav() Free memory for navigation data rtkcmn.c *

Debug trace functions

traceopen() Open trace file rtkcmn.c
traceclose() Close trace file rtkcmn.c
trace() Output trace rtkcmn.c
tracet() Output trace with time tag rtkcmn.c
tracemat() Output trace as matrix printing rtkcmn.c
traceobs() Output trace as observation data printing rtkcmn.c
traceonav() Output trace as GPS navigation messages rtkcmn.c
tracegnav() Output trace as GLONASS navigation messages rtkcmn.c
tracehnav() Output trace as GEO navigation messages rtkcmn.c
tracepeph() Output trace as precise ephemeris rtkcmn.c
tracepclk() Output trace as precise clock rtkcmn.c
traceb() Output trace as binary dump rtkcmn.c

Platform dependent functions

82
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

execcmd() Execute command rtkcmn.c
expath() Expand file path rtkcmn.c
createdir() Create directory rtkcmn.c
Positioning models
satwavelen() Satellite signal carrier wave length rtkcmn.c
satazel() Satellite azimuth/elevation angle rtkcmn.c
geodist() Geometric distance rtkcmn.c
dops() Compute DOPs rtkcmn.c
csmooth() Carrier smoothing rtkcmn.c
Atmosphere models
ionmodel() Ionospheric model rtkcmn.c
ionppp() Ionospheric pierce point position rtkcmn.c *
ionmapf() Ionospheric mapping function rtkcmn.c
tropmodel() Tropospheric model rtkcmn.c
tropmapf() Tropospheric mapping function (NMF) rtkcmn.c
iontec() Ionosphere model by TEC grid data ionex.c *
readtec() Read IONEX TEC grid file ionex.c *
ionocorr() Ionosphere correction pntpos.c *
tropcorr() Troposphere correction pntpos.c *
Antenna models
readpcv() Read antenna parameters rtkcmn.c
searchpcv() Search antenna parameters rtkcmn.c
antmodel() Receiver antenna model rtkcmn.c
antmodel_s() Satellite antenna model rtkcmn.c
Earth tides models
sunmoonpos() Sun and moon position preceph.c
tidedisp() Displacements by earth tides ppp.c

Geoid model
opengeoid() Open external geoid file geoid.c
closegeoid() Close external geoid file geoid.c
geoidh() Geoid height geoid.c

Datum transformation
loaddatump() Load datum transformation parameter datum.c
tokyo2jgd() Tokyo datum to JGD2000 datum datum.c
jgd2tokyo() JGD2000 datum to Tokyo datum datum.c

RINEX functions
readrnx() Read RINEX file rinex.c **
readrnxt() Read RINEX file in time range/interval rinex.c **
readrnxc() Read RINEX clock file rinex.c
setrnxcodepri() Set RINEX code priority rinex.c
outrnxobsh() Output RINEX OBS header rinex.c
outrnxobsb() Output RINEX OBS body rinex.c
outrnxnavh() Output RINEX NAV header rinex.c **
outrnxgnavh() Output RINEX GNAV header rinex.c **
outrnxhnavh() Output RINEX HNAV header rinex.c *
outrnxlnavh() Output RINEX LNAV header rinex.c *

83
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

outrnxqnavh() Output RINEX QNAV header rinex.c *
outrnxnavb() Output RINEX NAV body rinex.c
outrnxgnavb() Output RINEX GNAV body rinex.c
outrnxhnavb() Output RINEX HNAV body rinex.c *
uncompress() Uncompress file rinex.c
convrnx() RINEX converter convrnx.c

Ephemeris functions
eph2clk() Broadcast ephemeris to satellite clock‐bias ephemeris.c
geph2clk() GLONASS ephemeris to satellite clock‐bias ephemeris.c
seph2clk() GEO ephemeris to satellite clock‐bias ephemeris.c
eph2pos() Broadcast ephemeris to satellite position/clock‐bias ephemeris.c
geph2pos() GLONASS ephemeris to satellite position/clock‐bias ephemeris.c
seph2pos() GEO ephemeris to satellite position/clock‐bias ephemeris.c
peph2pos() Precise ephemeris to satellite position/clock‐bias preceph.c
satantoff() Satellite antenna phase center offset ephemeris.c
satpos() Satellite position/clock‐bias ephemeris.c **
satposs() Satellite positions/clock‐biases ephemeris.c **
readsp3() Read SP3 file preceph.c
readsap() Read satellite antenna phase center parameters preceph.c
readdcb() Read DCB parameters preceph.c
alm2pos() Almanac to satellite position/clock‐bias preceph.c *

Receiver raw data functions

getbitu() Extract unsigned bits rtkcmn.c
getbits() Extract signed bits rtkcmn.c
crc32() CRC32 parity rtkcmn.c
crc24q() CRC24Q parity rtkcmn.c
decode_word() Decode navigation data word rcvraw.c
decode_frame() Decode navigation data frame rcvraw.c **
init_raw() Initialize receiver raw data control rcvraw.c
free_raw() Free receiver raw data control rcvraw.c
input_raw() Input receiver raw data from stream rcvraw.c
input_rawf() Input receiver raw data from file rcvraw.c

Receiver dependent functions

input_oem4() Input OEM4/V raw data from stream rcv/novatel.c
input_oem3() Input OEM3 raw data from stream rcv/novatel.c
input_ubx() Input u‐blox raw data from stream rcv/ublox.c
input_ss2() Input Superstar II raw data from stream rcv/ss2.c
input_cres() Input Crescent raw data from stream rcv/crescent.c
input_stq() Input SkyTraq raw data from stream rcv/skytraq.c
input_gw10() Input Furuno GW‐10‐II/III raw data from stream rcv/gw10.c *
input_javad() Input JAVAD GRIL/GREIS raw data from stream rcv/javad.c *
input_oem3f() Input OEM3 raw data from file rcv/novatel.c
input_oem4f() Input OEM4/V raw data from file rcv/novatel.c
input_ubxf() Input u‐blox raw data from file rcv/ublox.c
input_ss2f() Input Superstar II raw data from file rcv/ss2.c
input_cresf() Input Crescent raw data from file rcv/crescent.c
input_stqf() Input SkyTraq raw data from file rcv/skytraq.c
input_gw10f() Input Furuno GW‐10‐II/III raw data from file rcv/gw10.c *

84
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

input_javadf() Input JAVAD GRIL/GREIS raw data from file rcv/javad.c *
gen_ubx() Generate u‐blox binary command rcv/ublox.c
gen_stq() Generate SkyTraq binary command rcv/skytraq.c

RTCM functions
init_rtcm() Initialize RTCM control rtcm.c
free_rtcm() Free RTCM control rtcm.c
input_rtcm2() Input RTCM2 message from stream rtcm.c
input_rtcm3() Input RTCM3 message from stream rtcm.c
input_rtcm2f() Input RTCM2 message from file rtcm.c
input_rtcm3f() Input RTCM3 message from file rtcm.c
Solution functions
initsolbuf() Initialize solution buffer solution.c
freesolbuf() Free solution buffer solution.c
freesolstatbuf() Free solution status buffer solution.c *
getsol() Get solution data from solution buffer solution.c
addsol() Add solution data to solution buffer solution.c
readsol() Read solution data from solutions files solution.c
readsolt() Read solution data in time range/interval solution.c
readsolstat() Read solution status from file solution.c
readsolstatt() Read solution status in time range/interval solution.c
inputsol() Input solution data from stream solution.c
outprcopts() Output processing options to string solution.c
outsolheads() Output solution header to string solution.c
outsols() Output solution body to string solution.c
outsolexs() Output extended solution to string solution.c
outprcopt() Output processing options to file solution.c
outsolhead() Output solution header to file solution.c
outsol() Output solution body to file solution.c
outsolex() Output extended solution to file solution.c
outnmea_rmc() Output NMEA GPRMC sentence solution.c
outnmea_gga() Output NMEA GPGGA sentence solution.c
outnmea_gsa() Output NMEA GPGSA sentence solution.c
outnmea_gsv() Output NMEA GPGSV sentence solution.c
Convert solutions to Google Earth KML file
convkml() Convert solutions to Google Earth KML file convkml.c

SBAS functions
sbsreadmsg() Read SBAS message file sbas.c
sbsreadsmgt() Read SBAS message file in time range sbas.c
sbsoutmsg() Output SBAS messages sbas.c
sbsdecodemsg() Decode SBAS message sbas.c
sbsupdatecorr() Update SBAS corrections sbas.c
sbssatcorr() SBAS satellite correction sbas.c
sbsioncorr() SBAS ionospheric correction sbas.c
sbstropcorr() SBAS tropospheric correction sbas.c

Options functions
searchopt() Search option options.c
str2opt() String to option value options.c

85
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

opt2str() Option value to string options.c
opt2buf() Option to string options.c
loadopts() Load options from file options.c
saveopts() Save options to file options.c
resetsysopts() Reset system options to default options.c
getsysopts() Get system options options.c
setsysopts() Set system options options.c

Stream data input/output functions

strinitcom() Initialize stream communication environment stream.c
strinit() Initialize stream stream.c
strlock() Lock stream stream.c
strunlock() Unlock stream stream.c
stropen() Open stream stream.c
strclose() Close stream stream.c
strread() Read stream stream.c
strwrite() Write stream stream.c
strsync() Time sync stream stream.c
strstat() Get stream status stream.c
strsum() Get stream statistics summary stream.c
strsetopt() Set stream options stream.c
strgettime() Get current time from stream stream.c
strsendnmea() Send NMEA message to stream stream.c
strsendcmd() Send receiver command to stream stream.c
strsettimeout() Set stream timeout parameters stream.c
strsetdir() Set local directory stream.c
strsetproxy() Set proxy address stream.c *

Integer ambiguity resolution

lambda() LAMBDA/MLAMBDA integer least‐square estimation lambda.c
Standard positioning
pntpos() Standard positioning pntpos.c

Precise positioning
rtkinit() Initialize RTK control struct rtkpos.c
rtkfree() Free RTK control struct rtkpos.c
rtkpos.c
rtkpos() Precise positioning ppp.c
rtkopenstat() Open solution status file rtkpos.c
rtkclosestat() Close solution status file rtkpos.c

Post‐processing positioning
postpos() Post‐processing positioning postpos.c

Stream server functions

strsvrinit() Initialize stream server streamsvr.c
strsvrstart() Start stream server streamsvr.c **
strsvrstop() Stop stream server streamsvr.c
strsvrstat() Get stream server status streamsvr.c

RTK server functions

86
 RTKLIB ver. 2.4.1 Manual

Function Description Source Program

rtksvrinit() Initialize RTK server rtksvr.c
rtksvrstart() Start RTK server rtksvr.c **
rtksvrstop() Stop RTK server rtksvr.c
rtksvropenstr() Open output/log stream rtksvr.c
rtksvrclosestr() Close output/log stream rtksvr.c
rtksvrlock() Lock RTK server rtksvr.c
rtksvrunlock() Unlock RTK server rtksvr.c
rtksvrostat() Get RTK observation data status rtksvr.c **
rtksvrsstat() Get RTK stream status rtksvr.c

87