Changeset 502 in ntrip for trunk/rtcm3torinex/rtcm3torinex.txt
- Timestamp:
- Oct 8, 2007, 2:51:24 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/rtcm3torinex/rtcm3torinex.txt
r318 r502 22 22 1012 GLONASS L1 and L2 code and phase and ambiguities and carrier to noise ratio 23 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)24 1014-1017 Network RTK (MAK) messages 25 1019 GPS Ephemeris 26 1020 GLONASS Ephemeris 27 27 4088-4095 Proprietary messages (under development) 28 28 29 29 Note that this version of rtcm3torinex only handles RTCM3 message types 1001, 30 1002, 1003, 1004, 1009, 1010, 1011 and 1012.30 1002, 1003, 1004, 1009, 1010, 1011, 1012, 1019 and 1020. 31 31 32 32 The generated RINEX is somewhat limited due to the streaming character of the … … 37 37 additional fields cannot be provided. 38 38 - The number of observables cannot change during the program runtime. Only 39 the observables, which exist in the first epoch are output ted. If there39 the observables, which exist in the first epoch are output. If there 40 40 are new observables later on, these are ignored. 41 41 - Only known message types are interpreted. This means only GPS data at the … … 48 48 easy positioning algorithm). 49 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 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 2101) 56 -t --timeout timeout in seconds (default 60) 57 -u --user the user name 58 -E --gpsephemeris output file for GPS ephemeris data 59 -G --glonassephemeris output file for GLONASS ephemeris data 60 -3 --rinex3 output RINEX type 3 data 61 -S --proxyhost proxy name or address 62 -R --proxyport proxy port, optional (default 2101) 63 -n --nmea NMEA string for sending to server 64 -M --mode mode for data request 65 Valid modes are: 66 1, h, http NTRIP Version 2.0 Caster in TCP/IP mode 67 2, r, rtsp NTRIP Version 2.0 Caster in RTSP/RTP mode 68 3, n, ntrip1 NTRIP Version 1.0 Caster 69 4, a, auto automatic detection (default) 57 70 58 71 The fields --user and --password are used to specify the access data for the 59 72 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 --data73 server itself (defaults to "www.euref-ip.net" port 2101). The Argument --data 61 74 must be used to specify the RTCM3 input data stream. If it is not given, you 62 75 will be shown the source table of the selected NTRIP caster. 63 76 64 77 Alternatively a single text of the form 65 "ntrip: mountpoint[/username[:password]][@server[:port]]"78 "ntrip:data[/user[:password]][@[server][:port][@proxyhost[:proxyport]]][;nmea]" 66 79 can be used. Everything in brackets is optional. 67 80 … … 101 114 102 115 Dirk Stoecker 103 EuronikGmbH104 http://www. euronik.eu/116 Alberding GmbH 117 http://www.alberding.eu/ 105 118 106 119 for … … 111 124 http://igs.bkg.bund.de/index_ntrip.htm 112 125 113 Contact Dirk Stoecker [stoecker@ euronik.eu] or [euref-ip@bkg.bund.de]126 Contact Dirk Stoecker [stoecker@alberding.eu] or [euref-ip@bkg.bund.de] 114 127 with your comments, suggestions, improvements, patches, ...
Note:
See TracChangeset
for help on using the changeset viewer.