| [28] | 1 | Manual for rtcm3torinex
|
|---|
| 2 |
|
|---|
| 3 | The program rtcm3torinex is an real-time converter from NTRIP streamed RTCM3
|
|---|
| 4 | data into the RINEX format. The generated RINEX is somewhat limited due to
|
|---|
| 5 | the streaming character of the conversion:
|
|---|
| 6 | - Header records can only represent data, which is known after receiving the
|
|---|
| 7 | very first epoch. Data rate, position, number of observations and any such
|
|---|
| 8 | additional fields cannot be provided.
|
|---|
| 9 | - The number of observables cannot change during the program runtime. Only
|
|---|
| 10 | the observables, which exist in the first epoch are outputted. If there
|
|---|
| 11 | are new observables later on, these are ignored.
|
|---|
| 12 | - Only known data types are interpreted. This means only GPS data at the
|
|---|
| 13 | moment. Send me new RTCM3 data files and data support can be improved.
|
|---|
| 14 | See contact address at the end of this document.
|
|---|
| 15 | - If the ambiguity field in the RTCM3 data is not set, the output will be no
|
|---|
| 16 | valid RINEX. All values will be stored modulo 299792.458. A COMMENT line
|
|---|
| 17 | will tell you, when this happens. It would be necessary to approximately
|
|---|
| 18 | calculate the range to fix the ambiguity (needing ephemeris/alamanac and
|
|---|
| 19 | easy positioning algorithm).
|
|---|
| 20 |
|
|---|
| 21 | Usage: rtcm3torinex -s server -u user ...
|
|---|
| 22 | -d --data the requested data set
|
|---|
| 23 | -f --headerfile file for RINEX header information
|
|---|
| 24 | -s --server the server name or address
|
|---|
| 25 | -p --password the login password
|
|---|
| 26 | -r --port the server port number (default 80)
|
|---|
| 27 | -u --user the user name
|
|---|
| 28 |
|
|---|
| 29 | The fields --user and --password are used to specify the access data for the
|
|---|
| 30 | NTRIP server. The arguments --server and --port are used to specify the NTRIP
|
|---|
| 31 | server itself (defaults to "www.euref-ip.net" port 80). The Argument --data
|
|---|
| 32 | must be used to specify the RTCM3 input data stream. If it is not given, you
|
|---|
| 33 | will be shown the source table of the selected NTRIP caster.
|
|---|
| 34 |
|
|---|
| 35 | Additionally the argument --headerfile can be used to provide additional header
|
|---|
| 36 | information. The file must contain normal RINEX observation file header lines.
|
|---|
| [29] | 37 | The given lines overwrite the automatical generated lines. Overwriting the
|
|---|
| [28] | 38 | lines "# / TYPES OF OBSERV" and "TIME OF FIRST OBS" usually is a bad idea and
|
|---|
| 39 | you will get warned if you do so. The line "END OF HEADER" is ignored.
|
|---|
| 40 | Unknown lines or COMMENT lines will be appended before the "END OF HEADER".
|
|---|
| 41 |
|
|---|
| 42 | NOTE: The tool does not check the input lines for validity. So be sure to
|
|---|
| 43 | use correct RINEX specifiers as well as correct alignment.
|
|---|
| 44 |
|
|---|
| 45 | To stop RINEX output send the program a killing signal. Following signal
|
|---|
| 46 | sources are supported:
|
|---|
| 47 |
|
|---|
| 48 | signal number usual source of the signal
|
|---|
| 49 | ---------------------------------------------------------------------------
|
|---|
| 50 | SIGINT 2 pressing CTRL+C in the shell running the tool
|
|---|
| 51 | SIGQUIT 3 pressing CTRL-\ or sending QUIT signal
|
|---|
| 52 | SIGTERM 15 called kill <num> with the process number of rtcm3torinex
|
|---|
| 53 | SIGPIPE 13 the output or input of rtcm3torinex has been closed
|
|---|
| 54 |
|
|---|
| 55 | The programm will be terminated after the current epoch has been finished.
|
|---|
| 56 | You will not get corrupted RINEX files.
|
|---|
| 57 |
|
|---|
| 58 | Contact me with your comments, suggestions, improvements, patches, ...
|
|---|
| 59 |
|
|---|
| 60 | Dirk Stöcker
|
|---|
| 61 | EuroNav Service GmbH
|
|---|
| 62 | http://www.euronav.de/
|
|---|
| [29] | 63 | stoecker@euronav.de
|
|---|
| [28] | 64 | 2006-01-12
|
|---|
