source: ntrip/trunk/rtcm3torinex/rtcm3torinex.txt@ 189

Last change on this file since 189 was 29, checked in by stoecker, 19 years ago

typos

File size: 3.1 KB
Line 
1Manual for rtcm3torinex
2
3The program rtcm3torinex is an real-time converter from NTRIP streamed RTCM3
4data into the RINEX format. The generated RINEX is somewhat limited due to
5the 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
21Usage: 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
29The fields --user and --password are used to specify the access data for the
30NTRIP server. The arguments --server and --port are used to specify the NTRIP
31server itself (defaults to "www.euref-ip.net" port 80). The Argument --data
32must be used to specify the RTCM3 input data stream. If it is not given, you
33will be shown the source table of the selected NTRIP caster.
34
35Additionally the argument --headerfile can be used to provide additional header
36information. The file must contain normal RINEX observation file header lines.
37The given lines overwrite the automatical generated lines. Overwriting the
38lines "# / TYPES OF OBSERV" and "TIME OF FIRST OBS" usually is a bad idea and
39you will get warned if you do so. The line "END OF HEADER" is ignored.
40Unknown lines or COMMENT lines will be appended before the "END OF HEADER".
41
42NOTE: The tool does not check the input lines for validity. So be sure to
43use correct RINEX specifiers as well as correct alignment.
44
45To stop RINEX output send the program a killing signal. Following signal
46sources are supported:
47
48signal number usual source of the signal
49---------------------------------------------------------------------------
50SIGINT 2 pressing CTRL+C in the shell running the tool
51SIGQUIT 3 pressing CTRL-\ or sending QUIT signal
52SIGTERM 15 called kill <num> with the process number of rtcm3torinex
53SIGPIPE 13 the output or input of rtcm3torinex has been closed
54
55The programm will be terminated after the current epoch has been finished.
56You will not get corrupted RINEX files.
57
58Contact me with your comments, suggestions, improvements, patches, ...
59
60Dirk Stöcker
61EuroNav Service GmbH
62http://www.euronav.de/
63stoecker@euronav.de
642006-01-12
Note: See TracBrowser for help on using the repository browser.