| 1 | Manual for rtcm3torinex
|
|---|
| 2 |
|
|---|
| 3 | The program rtcm3torinex is an real-time converter from NTRIP streamed RTCM3
|
|---|
| 4 | data into the RINEX format.
|
|---|
| 5 |
|
|---|
| 6 | RTCM3 defines a number of message types. Among them are the following:
|
|---|
| 7 |
|
|---|
| 8 | Message
|
|---|
| 9 | Type Contains information about
|
|---|
| 10 | --------------------------------------------------------------------------
|
|---|
| 11 | 1001 GPS L1 code and phase
|
|---|
| 12 | 1002 GPS L1 code and phase and ambiguities and carrier to noise ratio
|
|---|
| 13 | 1003 GPS L1 and L1 code and phase
|
|---|
| 14 | 1004 GPS L1 and L2 code and phase and ambiguities and carrier to noise ratio
|
|---|
| 15 | 1005 Station coordinates XZY for antenna reference point
|
|---|
| 16 | 1006 Station coordinates XYZ for antenna reference point and antenna height
|
|---|
| 17 | 1007 Antenna descriptor and ID
|
|---|
| 18 | 1008 Antenna serial number
|
|---|
| 19 | 1009 GLONASS L1 code and phase
|
|---|
| 20 | 1010 GLONASS L1 code and phase and ambiguities and carrier to noise ratio
|
|---|
| 21 | 1011 GLONASS L1 and L1 code and phase
|
|---|
| 22 | 1012 GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio
|
|---|
| 23 | 1013 Modified julian date, leep second, configured message types and intervall
|
|---|
| 24 | 1014-1017 Network RTK (MAK) messages (under development)
|
|---|
| 25 | 1019 GPS Ephemeris (under development)
|
|---|
| 26 | 1020 GLONASS Ephemeris (under development)
|
|---|
| 27 | 4088-4095 Proprietary messages (under development)
|
|---|
| 28 |
|
|---|
| 29 | Note that this version of rtcm3torinex only handles RTCM3 message types 1001,
|
|---|
| 30 | 1002, 1003, 1004, 1009, 1010, 1011 and 1012.
|
|---|
| 31 |
|
|---|
| 32 | The generated RINEX is somewhat limited due to the streaming character of the
|
|---|
| 33 | conversion:
|
|---|
| 34 |
|
|---|
| 35 | - Header records can only represent data, which is known after receiving the
|
|---|
| 36 | very first epoch. Data rate, position, number of observations and any such
|
|---|
| 37 | additional fields cannot be provided.
|
|---|
| 38 | - The number of observables cannot change during the program runtime. Only
|
|---|
| 39 | the observables, which exist in the first epoch are outputted. If there
|
|---|
| 40 | are new observables later on, these are ignored.
|
|---|
| 41 | - Only known message types are interpreted. This means only GPS data at the
|
|---|
| 42 | moment. Send me new RTCM3 data files and data support can be improved.
|
|---|
| 43 | See contact address at the end of this document.
|
|---|
| 44 | - If the ambiguity field in the RTCM3 data is not set, the output will be no
|
|---|
| 45 | valid RINEX. All values will be stored modulo 299792.458. A COMMENT line
|
|---|
| 46 | will tell you, when this happens. It would be necessary to approximately
|
|---|
| 47 | calculate the range to fix the ambiguity (needing ephemeris/alamanac and
|
|---|
| 48 | easy positioning algorithm).
|
|---|
| 49 |
|
|---|
| 50 | Usage: rtcm3torinex -s server -u user ...
|
|---|
| 51 | -d --data the requested data set
|
|---|
| 52 | -f --headerfile file for RINEX header information
|
|---|
| 53 | -s --server the server name or address
|
|---|
| 54 | -p --password the login password
|
|---|
| 55 | -r --port the server port number (default 80)
|
|---|
| 56 | -u --user the user name
|
|---|
| 57 |
|
|---|
| 58 | The fields --user and --password are used to specify the access data for the
|
|---|
| 59 | NTRIP server. The arguments --server and --port are used to specify the NTRIP
|
|---|
| 60 | server itself (defaults to "www.euref-ip.net" port 80). The Argument --data
|
|---|
| 61 | must be used to specify the RTCM3 input data stream. If it is not given, you
|
|---|
| 62 | will be shown the source table of the selected NTRIP caster.
|
|---|
| 63 |
|
|---|
| 64 | Alternatively a single text of the form
|
|---|
| 65 | "ntrip:mountpoint[/username[:password]][@server[:port]]"
|
|---|
| 66 | can be used. Everything in brackets is optional.
|
|---|
| 67 |
|
|---|
| 68 | Additionally the argument --headerfile can be used to provide additional header
|
|---|
| 69 | information. The file must contain normal RINEX observation file header lines.
|
|---|
| 70 | The given lines overwrite the automatical generated lines. Overwriting the
|
|---|
| 71 | lines "# / TYPES OF OBSERV" and "TIME OF FIRST OBS" usually is a bad idea and
|
|---|
| 72 | you will get warned if you do so. The line "END OF HEADER" is ignored.
|
|---|
| 73 | Unknown lines or COMMENT lines will be appended before the "END OF HEADER".
|
|---|
| 74 |
|
|---|
| 75 | NOTE: The tool does not check the input lines for validity. So be sure to
|
|---|
| 76 | use correct RINEX specifiers as well as correct alignment.
|
|---|
| 77 |
|
|---|
| 78 | To stop RINEX output send the program a killing signal. Following signal
|
|---|
| 79 | sources are supported:
|
|---|
| 80 |
|
|---|
| 81 | signal number usual source of the signal
|
|---|
| 82 | ---------------------------------------------------------------------------
|
|---|
| 83 | SIGINT 2 pressing CTRL+C in the shell running the tool
|
|---|
| 84 | SIGQUIT 3 pressing CTRL-\ or sending QUIT signal
|
|---|
| 85 | SIGTERM 15 called kill <num> with the process number of rtcm3torinex
|
|---|
| 86 | SIGPIPE 13 the output or input of rtcm3torinex has been closed
|
|---|
| 87 |
|
|---|
| 88 | The programm will be terminated after the current epoch has been finished.
|
|---|
| 89 | You will not get corrupted RINEX files.
|
|---|
| 90 |
|
|---|
| 91 | When compiling the program with older gcc versions running the `make'
|
|---|
| 92 | command, you may receive an informative error message saying
|
|---|
| 93 |
|
|---|
| 94 | rtcm3torinex.c: In function `signalhandler_alarm':
|
|---|
| 95 | rtcm3torinex.c:1240: warning: `noreturn' function does return
|
|---|
| 96 |
|
|---|
| 97 | This is most likely a compiler problem which only concerns the optimization
|
|---|
| 98 | and is thus not critical. New compilers will not show this problem.
|
|---|
| 99 |
|
|---|
| 100 | Program written by
|
|---|
| 101 |
|
|---|
| 102 | Dirk Stoecker
|
|---|
| 103 | Euronik GmbH
|
|---|
| 104 | http://www.euronik.eu/
|
|---|
| 105 |
|
|---|
| 106 | for
|
|---|
| 107 |
|
|---|
| 108 | Federal Agency for Cartography and Geodesy (BKG)
|
|---|
| 109 | Richard-Strauss-Allee 11
|
|---|
| 110 | D-60598 Frankfurt
|
|---|
| 111 | http://igs.bkg.bund.de/index_ntrip.htm
|
|---|
| 112 |
|
|---|
| 113 | Contact Dirk Stoecker [stoecker@euronik.eu] or [euref-ip@bkg.bund.de]
|
|---|
| 114 | with your comments, suggestions, improvements, patches, ...
|
|---|
