Changeset 318 in ntrip for trunk/rtcm3torinex/rtcm3torinex.txt
- Timestamp:
- Nov 15, 2006, 1:31:31 PM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/rtcm3torinex/rtcm3torinex.txt
r29 r318 2 2 3 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: 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 6 35 - Header records can only represent data, which is known after receiving the 7 36 very first epoch. Data rate, position, number of observations and any such … … 10 39 the observables, which exist in the first epoch are outputted. If there 11 40 are new observables later on, these are ignored. 12 - Only known datatypes are interpreted. This means only GPS data at the41 - Only known message types are interpreted. This means only GPS data at the 13 42 moment. Send me new RTCM3 data files and data support can be improved. 14 43 See contact address at the end of this document. … … 32 61 must be used to specify the RTCM3 input data stream. If it is not given, you 33 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. 34 67 35 68 Additionally the argument --headerfile can be used to provide additional header … … 56 89 You will not get corrupted RINEX files. 57 90 58 Contact me with your comments, suggestions, improvements, patches, ... 91 When compiling the program with older gcc versions running the `make' 92 command, you may receive an informative error message saying 59 93 60 Dirk Stöcker 61 EuroNav Service GmbH 62 http://www.euronav.de/ 63 stoecker@euronav.de 64 2006-01-12 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, ...
Note:
See TracChangeset
for help on using the changeset viewer.