source: ntrip/trunk/BNS/bnshelp.html@ 2411

Last change on this file since 2411 was 2411, checked in by weber, 12 years ago

* empty log message *

File size: 48.1 KB
Line 
1<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
2<h3>BKG Ntrip State Space Server (BNS) Version 1.1</h3>
3
4<p>
5The BKG Ntrip State Space Server (BNS) is a program for transforming GNSS satellite clocks and orbits into corrections to Broadcast Ephemeris. These corrections are then encode in a (premature) RTCM Version 3.x format and uploaded to NTRIP broadcasters like <u>http://www.euref-ip.net/home</u> or <u>http://www.igs-ip.net/home.</u> BNS is created as a tool for service providers with real-time access to a network of continentally or globally distributed GNSS reference stations.
6</p>
7
8<p>
9BNS has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS PP).
10</p>
11
12<p>
13BNS is released under the GNU General Public License (GPL). Binaries for BNS are available for Windows, 32-bit and 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac OS X systems. The MinGW compiler (Version 5.3.1) is used to produce the Windows binary. It is likely that BNS can be compiled on other systems where a GNU compiler and Qt Version 4.4.3 are available.
14</p>
15
16<p>
17Before running, please ensure that you have installed the latest version available. This can be obtained from <u>http://igs.bkg.bund.de/index_ntrip_down.htm</u>. We are continuously working on the program and would appreciate any comments, suggestions, or bug reports. They can be emailed to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de].
18</p>
19
20<h3>Contents</h3>
21<p>
22<h4>
23<a href=#purpose>1. Purpose</a><br>
24<a href=#function>2. Functioning</a><br>
25<a href=#resources>3. Modes &amp; Resources</a><br>
26<a href=#options>4. Options</a><br>
27<a href=#limits>5. Limitations</a><br>
28<a href=#authors>6. Authors</a><br>
29<a href=#annex>7. Annex</a><br>
30</h4>
31</p>
32
33<p><a name="purpose"><h3>1. Purpose</h3></p>
34<p>
35Differential GNSS and RTK operation using RTCM streams is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning is using 'observation space' information. The representation with the RTCM standard can be called 'Observation Space Representation' (OSR).
36</p>
37<p>
38An alternative to the observation space approach is the so called 'sate space' approach. The principle here is to provide information on individual error sources and can be called 'State Space Representation' (SSR). For a rover position, state space information concerning precise satellite clocks, orbits, ionosphere, troposphere et cetera can be converted into observation space and used to correct the rover observables for more accurate positioning. Alternatively the state information can directly be used in the rover's processing or adjustment model.
39</p>
40
41<p>In order to support applications following the state space approach, the purpose of BNS is to
42
43<ul>
44<li>read GNSS clocks and orbits in a SP3-like format from an IP port. They can be produced by a real-time GNSS engine such as RTNet and should be referenced to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system.</li>
45<li>read GNSS Broadcast Ephemeris in RINEX Navigation format from an IP port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program.</li>
46<li>convert the IGS Earth-Centered-Earth-Fixed clocks and and orbits into corrections to Broadcast Ephemeris with radial, along-track and cross-track components.</li>
47<li>refer the clock and orbit corretions to a specific reference system.</li>
48<li>upload the clock and orbit corrections as an RTCM Version 3.x stream to an NTRIP Broadcaster.</li>
49<li>log the Broadcast Ephemeris clock corrections as files in Clock RINEX files.</li>
50<li>log the Broadcast Ephemeris orbit corrections as files in SP3 files.</li>
51</ul>
52</p>
53
54<p><a name="function"><h3>2. Functioning</h3></p>
55<p>
56The procedures taken by BNS to generate clock and orbit corrections to Broadcast Ephemeris in radial, along-track and cross-track components are as follow:
57</p>
58<p>
59<ul>
60<li>Continuously receive up-to-date Broadcast Ephemeris carrying approximate orbits and clocks for all satellites. Receive them in RINEX Version 3 Navigation file format. Read new Broadcast Ephemeris immediately whenever they become available. Tools like the 'BKG Ntrip Client' (BNC) provide this information.</li>
61</ul>
62</p>
63<p>
64Then, epoch by epoch:
65<ul>
66<li>Continuously receive the best available clock and orbit estimates for all satellites in X,Y,Z Earth-Centered-Earth-Fixed IGS05 reference system. Receive them every epoch in a SP3-like format as provided by a real-time GNSS engine such as RTNet.</li>
67<li>Calculate X,Y,Z coordinates from Broadcast Ephemeris orbits.</li>
68<li>Calculate differences dX,dY,dZ between Broadcast Ephemeris and IGS05 orbits.</li>
69<li>Tranform these differences into radial, along-track and cross-track corrections to Broadcast Ephemeris orbits.</li>
70<li>Calculate corrections to Broadcast Ephemeris clocks as differences between Broadcast Ephemeris and IGS05 clocks.</li>
71<li>Encode Broadcast Ephemeris clock and orbit corrections in RTCM Version 3.x format.</li>
72<li>Upload corrections stream to NTRIP Broadcaster.</li>
73</ul>
74</p>
75<p>
76Although it is not compulsory, because BNS puts a significant load on the communication link, it is recommended that BNS, the Broadcast Ephemeris server (i.e. BNC), and the server providing orbits and clocks (i.e. RTNet) are run on the same host.
77</p>
78
79<p><a name="resources"><h3>3. Modes &amp; Resources</h3></p>
80<p>
81Apart from its regular window mode, BNS can be run as a background job in a 'no window' mode using processing options from a previously saved configuration.
82</p>
83<p>
84BNS requires access to the Internet with a minimum of about 1 kbits/sec per stream depending on the number of GNSS systems. You need to make sure that the connection can sustain the required bandwidth.
85</p>
86<p>
87It requires the clock of the host computer to be properly synchronized.
88</p>
89
90<p><a name="options"><h3>4. Options</h3></p>
91
92<p>
93This section describes BNS's top menu bar, its processing options and its bottom menu bar.
94</p>
95
96<p>
97The usual handling of BNS is that you first select severs for 'RINEX Ephemeris' and 'Clocks &amp; Orbits'. You then select an NTRIP broadcaster for stream upload ('Broadcast Corrections') before you start the program ('Start'). Records of BNS's activities are shown in the 'Logs' canvas in the middle of the main window.
98</p>
99
100<p>
101As a default, configuration files for running BNS on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNS.ini'.
102</p>
103
104<p>
105The default file name 'BNS.ini' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag &amp; Drop a configuration file icon to start BNS. See annexed 'Configuration Example' for a complete set of configuration options.
106</p>
107
108<p>
1094.1. <a href=#topmenu>Top Menu Bar</a><br>
1104.1.1 <a href=#file>File</a><br>
1114.1.2 <a href=#help>Help</a><br>
1124.2. <a href=#proxy>Proxy</a><br>
1134.3. <a href=#general>General</a><br>
114&nbsp; &nbsp; &nbsp; 4.3.1. <a href=#logfile>Logfile</a><br>
115&nbsp; &nbsp; &nbsp; 4.3.2. <a href=#appfile>Append Files</a><br>
116&nbsp; &nbsp; &nbsp; 4.3.3. <a href=#genstart>Auto Start</a><br>
1174.4. <a href=#eph>RINEX Ephemeris</a><br>
118&nbsp; &nbsp; &nbsp; 4.4.1. <a href=#ephserver>Host &amp; Port</a><br>
119&nbsp; &nbsp; &nbsp; 4.4.2. <a href=#ephsave>Save</a><br>
1204.5. <a href=#co>Clocks &amp; Orbits</a><br>
121&nbsp; &nbsp; &nbsp; 4.5.1. <a href=#coport>Listening Port</a><br>
122&nbsp; &nbsp; &nbsp; 4.5.2. <a href=#cosave>Save</a><br>
1234.6. <a href=#ephc>Broadcast Corrections</a><br>
124&nbsp; &nbsp; &nbsp; 4.6.1. <a href=#ephcserver>Host &amp; Port</a><br>
125&nbsp; &nbsp; &nbsp; 4.6.2. <a href=#ephcmount>Mountpoint &amp; Password</a><br>
126&nbsp; &nbsp; &nbsp; 4.6.3. <a href=#ephcsys>System</a><br>
127&nbsp; &nbsp; &nbsp; 4.6.4. <a href=#ephcsave>Save</a><br>
128&nbsp; &nbsp; &nbsp; 4.6.5. <a href=#ephcom>Center of Mass</a><br>
1294.7. <a href=#brdc>Broadcast Ephemeris</a><br>
130&nbsp; &nbsp; &nbsp; 4.7.1. <a href=#brdcserver>Host &amp; Port</a><br>
131&nbsp; &nbsp; &nbsp; 4.7.2. <a href=#brdcmount>Mountpoint &amp; Password</a><br>
132&nbsp; &nbsp; &nbsp; 4.7.3. <a href=#brdcsmpl>Sampling</a><br>
1334.8. <a href=#clkrnx>RINEX Clocks</a><br>
134&nbsp; &nbsp; &nbsp; 4.8.1. <a href=#clkdir>Directory</a><br>
135&nbsp; &nbsp; &nbsp; 4.8.2. <a href=#clkint>Interval &amp; Sampling</a><br>
1364.9. <a href=#orb>SP3 Orbits</a><br>
137&nbsp; &nbsp; &nbsp; 4.9.1. <a href=#orbdir>Directory</a><br>
138&nbsp; &nbsp; &nbsp; 4.9.2. <a href=#orbint>Interval &amp; Sampling</a><br>
1394.10. <a href=#bottom>Bottom Menu Bar</a><br>
1404.10.1 <a href=#start>Start</a><br>
1414.10.2 <a href=#stop>Stop</a><br>
1424.11. <a href=#cmd>Command Line Options</a><br>
1434.11.1 <a href=#nw>No Window</a><br>
1444.11.2 <a href=#conffile>Configuration File</a>
145</p>
146
147<p><a name="topmenu"><h4>4.1. Top Menu Bar</h4></p>
148<p>
149The top menu bar allows to select a font for the BNS windows, save configured options or quit
150 the program execution. It also provides access to a program documentation.
151</p>
152
153<p><a name="file"><h4>4.1.1 File</h4></p>
154
155<p>
156The 'File' button lets you
157<ul>
158<li>
159select an appropriate font.<br>
160Use smaller font size if the BNS main window extends beyond the size of your screen.
161</li>
162<li> save selected options in configuration file.
163</li>
164<li>
165quit the BNS program.
166</li>
167</ul>
168</p>
169
170<p><a name="help"><h4>4.1.2 Help</h4></p>
171
172<p>
173The 'Help' button provides access to
174<ul>
175<li>
176help contents.<br>
177You may keep the 'Help Contents' window open while configuring BNS.
178</li>
179<li>
180a 'Flow Chart' showing BNS linked to tools like BNC and a real-time GNSS engine such as RTNet.
181</li>
182<li>
183general information about BNS.<br>
184Close the 'About BNS' window to continue working with BNS.
185</li>
186</ul>
187</p>
188<p>
189BNS comes with a help system providing online information about its functionality and usage. Short descriptions are available for any widget. Focus to the relevant widget and press Shift+F1 to request help information. A help text will appear immediately; it disappears as soon as the focus is shifted to something else. The dialogs on some operating systems may provide a &quot;?&quot; button that users can click; they then click the relevant widget to pop up the help text.
190</p>
191
192<p><a name="proxy"><h4>4.2. Proxy - for usage in a protected LAN</h4></p>
193
194<p>
195If you are running BNS within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNS. If you don't know the address and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.
196</p>
197<p>
198Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP Casters. If these are not possible, you might need to run BNS outside your LAN on a host that has unobstructed connection to the Internet.
199</p>
200<p><a name="general"><h4>4.3. General Options</h4></p>
201<p>
202The following describes general settings for BNC's logfile, file handling and auto-start.
203</p>
204
205<p><a name="logfile"><h4>4.3.1 Logfile - optional</h4></p>
206<p>
207Records of BNS's activities are shown in the Log section on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers the communication status between BNS and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Log (full path)' is an empty option field, meaning that BNS logs will not saved into a file.
208</p>
209
210<p><a name="appfile"><h4>4.3.2 Append Files</h4></p>
211<p>
212When BNS is started, new files are created by default and any existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNS, a system crash or when BNS had crashed. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNS.
213</p>
214
215<p><a name="genstart"><h4>4.3.3 Auto Start - optional</h4></p>
216<p>
217You may like to auto-start BNS at startup time in window mode with preassigned configuration options. This may be required i.e. immediately after booting your system. Tick 'Autostart' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNS for that in your Autostart directory (Windows systems) or call BNS in a script below directory /etc/init.d (Unix/Linux/Mac systems).
218</p>
219
220<p><a name="eph"><h4>4.4. RINEX Ephemeris</h4></p>
221<p>
222BNS requires GNSS Broadcast Ephemeris in RINEX Version 3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Note that whenever a new set of Broadcast Ephemeris becomes available, BNS needs it immediately.
223</p>
224
225<p>
226The following is an example log of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04:
227</p>
228
229<p>
230<pre>
231G32 2008 07 22 12 00 00 3.08818183839e-04 2.72848410532e-12 0.00000000000e+00
232 1.10000000000e+01 -4.00312500000e+01 4.63269297026e-09 9.74027926504e-01
233 -2.19419598579e-06 1.39143558918e-02 8.25151801109e-06 5.15381674576e+03
234 2.16000000000e+05 -8.56816768646e-08 -3.26801342873e-02 -2.94297933578e-07
235 9.68688494953e-01 2.30468750000e+02 -1.30607654294e+00 -8.26105839196e-09
236 -3.62872257943e-10 1.00000000000e+00 1.48900000000e+03 0.00000000000e+00
237 2.00000000000e+00 0.00000000000e+00 -2.79396772385e-09 1.10000000000e+01
238 0.00000000000e+00 0.00000000000e+00
239R04 2008 07 22 08 15 14 4.76110726595e-05 0.00000000000e+00 2.88600000000e+04
240 -1.76267827148e+04 -4.64202880859e-01 1.86264514923e-09 0.00000000000e+00
241 -1.79631489258e+04 -3.41343879700e-01 -2.79396772385e-09 6.00000000000e+00
242 -4.20270556641e+03 3.50097942352e+00 0.00000000000e+00 0.00000000000e+00
243</pre>
244</p>
245
246<p><a name="ephserver"><h4>4.4.1 Host &amp; Port - mandatory</h4></p>
247<p>
248Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS.
249</p>
250
251<p><a name="ephsave"><h4>4.4.2 Save - optional</h4></p>
252</p>
253Specify the full path to a file where received Broadcast Ephemeris will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
254</p>
255
256<p><a name="co"><h4>4.5. Clocks &amp; Orbits</h4></p>
257<p>
258BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system in a SP3-like format refered to CoM. They can be provided by a real-time GNSS engine such as RTNet. The sampling rate should not be much greater than 10 sec. Note that otherwise in IP streaming involved tools on the NTRIP Broadcaster or client side may respond with a timeout.
259</p>
260
261<p>
262Below you find an example of precise clocks and orbits coming in a SP3-like format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite:
263</p>
264
265<p>
266<ul>
267<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
268<li>X,Y,Z coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T</li>
269<li>Satellite clock error [microsecond]</li>
270<li>2nd order relativistic effect [microsecond]</li>
271<li>DX,DY,DZ [m] in Earth-Centered-Earth-Fixed system for translation CoM-&gt;APC</li>
272<li>Differential Code Bias P1C1 [m]</li>
273<li>Differential Code Bias P1P2 [m]</li>
274<li>Time increment dT [second]</li>
275<li>X,Y,Z coordinates in Earth-Centered-Earth-Fixed system [km] at epoch T+dT</li>
276</ul>
277</p>
278Example:
279</p>
280<p>
281<pre>
282* 2009 12 7 13 11 30.00000000
283PG02 22354.452213 -13767.325289 1772.434231 228.750524 -0.001932 -0.522 0.321 -0.041 0.000 0.000 60.0 22377.342363 -13753.550786 1583.545731
284PG03 -11102.768914 16968.159551 16622.454893 518.437937 0.001957 1.012 -1.908 -1.508 0.000 0.000 60.0 -11129.949019 16837.402637 16736.552194
285PG04 24167.186374 -3628.894484 -11005.210034 19.658309 -0.001319 -2.103 0.034 0.921 0.000 0.000 60.0 24101.853298 -3576.088512 -11164.914026
286PG05 14447.045279 -8140.619149 20744.274083 -7.120008 -0.004342 -0.381 0.215 -0.547 0.000 0.000 60.0 14578.754091 -8053.151311 20686.754446
287...
288...
289</pre>
290</p>
291<p>
292In other words: The clocks in the ASCII stream from a real-time GNSS engine which feeds BNS must not contain the '2nd order relativistic effect'. Furthermore, BNS does not add this effect to the stream.
293</p>
294
295<p><a name="coport"><h4>4.5.1 Listening Port - mandatory</h4></p>
296<p>
297BNS is listening at an IP port for incoming GNSS clocks and orbits in a SP3-like format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS.
298</p>
299
300<p><a name="cosave"><h4>4.5.2 Save - optional</h4></p>
301<p>
302Specify the full path to a file where received clocks and orbits from a real-time engine will be logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
303</p>
304
305<p><a name="ephc"><h4>4.6. Broadcast Corrections</h4></p>
306<p>
307BNS can upload the resulting stream(s) of clock and orbit corrections to Broadcast Ephemeris to an NTRIP Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u> which can be used for stream upload. The stream's format is RTCM Version 3.x.
308</p>
309<p>
310BNS allows to configure two Broadcast Corrections streams refering do different reference systems for upload to different NTRIP broadcasters. You may use this functionality for parallel support of a backup NTRIP broadcaster or for simultaneous support of two reference systems.
311</p>
312
313<p>
314When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the 2nd-order relativistic effect. The 2nd-order relativistic effect is a priodic time correction defined as -2 (R * V) / c^2 and includes the scalar product of satallite position and velocity divided by the speed of light raised to the second power.
315</p>
316
317<p><a name="ephcserver"><h4>4.6.1 Host &amp; Port - optional</h4></p>
318<p>
319Specify the 'Host' IP name or number of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload corrections to Broadcast Ephemeris.
320</p>
321<p>
322Enter the NTRIP Caster's IP 'Port' number for stream upload. Note that NTRIP Casters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
323</p>
324
325<p><a name="ephcmount"><h4>4.6.2 Mountpoint &amp; Password - mandatory if 'Host' is set</h4></p>
326<p>
327Each stream on an NTRIP Caster is defined using a unique source ID called mountpoint. An NTRIP Server like BNS uploads a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify here the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.
328<p>
329</p>
330In NTRIP Version 1.0 stream upload may be protected through an upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint(s).
331</p>
332
333<p><a name="ephcsys"><h4>4.6.3 System - mandatory if 'Host' is set</h4></p>
334<p>
335BNS refers its clock and orbit corrections to a specific reference system. Available options are
336<p>
337<ul>
338<li>IGS05 which stands for the GNSS-based IGS realization of the International Terrestrial Reference Frame 2005 (ITRF2005), and</li>
339<li>ETRF2000 which stands for the European Terestrial Reference Frame 2000 adopted by EUREF, and</li>
340<li>NAD83 which stands for the North American Datum 1983 as adopted for the U.S.A., and</li>
341<li>GDA94 which stands for the Geodetic Datum Australia 1994 as adopted for Australia, and</li>
342<li>SIRGAS2000 which stands for the Geodetic Datum adopted for Brazil, and</li>
343<li>SIRGAS95 which stands for the Geodetic Datum adopted i.e. for Venezuela, and</li>
344<li>'Custom' which allows a transformation of Broadcast Corrections from the IGS05 system to any other system through specifying up to 14 Helmert Transformation Parameters.</li>
345</ul>
346</p>
347
348<p>
349<u>IGS05:</u> As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected.
350</p>
351
352<p>
353<u>ETRF2000:</u> The formulars for the transformation 'ITRF2005-&gt;ETRF2000' are taken from 'Claude Boucher and Zuheir Altamimi 2008: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see <u>http://etrs89.ensg.ign.fr/memo-V7.pdf</u>. The following 14 Helmert Transformation Parameters were introduced:
354</p>
355<p>
356<pre>
357Translation in X at epoch To: 0.0541 m
358Translation in Y at epoch To: 0.0502 m
359Translation in Z at epoch To: -0.0538 m
360Translation rate in X: -0.0002 m/y
361Translation rate in Y: 0.0001 m/y
362Translation rate in Z: -0.0018 m/y
363Rotation in X at epoch To: 0.891 mas
364Rotation in Y at epoch To: 5.390 mas
365Rotation in Z at epoch To: -8.712 mas
366Rotation rate in X: 0.081 mas/y
367Rotation rate in Y: 0.490 mas/y
368Rotation rate in Z: -0.792 mas/y
369Scale at epoch To : 0.00000000040
370Scale rate: 0.00000000008 /y
371To: 2000.0
372</pre>
373</p>
374
375<p>
376<u>NAD83:</u> Formulars for the transformation 'ITRF2005-&gt;NAD83' are taken from 'Chris Pearson, Robert McCaffrey, Julie L. Elliott, Richard Snay 2010: 'HTDP 3.0: Software for Coping with the Coordinate Changes Associated with Crustal Motion', Journal of Surveying Engineering.
377</p>
378<p>
379<pre>
380Translation in X at epoch To: 0.9963 m
381Translation in Y at epoch To: -1.9024 m
382Translation in Z at epoch To: -0.5219 m
383Translation rate in X: 0.0005 m/y
384Translation rate in Y: -0.0006 m/y
385Translation rate in Z: -0.0013 m/y
386Rotation in X at epoch To: 25.915 mas
387Rotation in Y at epoch To: 9.426 mas
388Rotation in Z at epoch To: 11.599 mas
389Rotation rate in X: 0.067 mas/y
390Rotation rate in Y: -0.757 mas/y
391Rotation rate in Z: -0.051 mas/y
392Scale at epoch To : 0.00000000078
393Scale rate: -0.00000000010 /y
394To: 1997.0
395</pre>
396</p>
397
398<p>
399<u>GDA94:</u> The formulars for the transformation 'ITRF2000-&gt;GDA94' are taken from 'John Dawson and Jim Steed 2004: International Terrestrial Reference Frame (ITRF) to GDA94 Coordinate Transformations', see <u>http://www.ga.gov.au/servlet/BigObjFileManager?bigobjid=GA3795 </u>.
400</p>
401<p>
402<pre>
403Translation in X at epoch To: 0.07167 m
404Translation in Y at epoch To: 0.00486 m
405Translation in Z at epoch To: -0.04711 m
406Translation rate in X: -0.00342 m/y
407Translation rate in Y: 0.00055 m/y
408Translation rate in Z: 0.00136 m/y
409Rotation in X at epoch To: 9.1362 mas
410Rotation in Y at epoch To: 9.3086 mas
411Rotation in Z at epoch To: 9.1599 mas
412Rotation rate in X: 1.4652 mas/y
413Rotation rate in Y: 1.1005 mas/y
414Rotation rate in Z: 1.1480 mas/y
415Scale at epoch To : -0.000000008239
416Scale rate: -0.000000000212 /y
417To: 2000.0
418</pre>
419</p>
420
421<p>
422<u>SIRGAS2000:</u> The formulars for the transformation 'ITRF2005-&gt;SIRGAS2000' were provided via personal communication from CGED-Coordenacao de Geodesia, IBGE/DGC - Diretoria de Geociencias, Brazil.</u>.
423</p>
424<p>
425<pre>
426Translation in X at epoch To: -0.0051 m
427Translation in Y at epoch To: -0.0065 m
428Translation in Z at epoch To: -0.0099 m
429Translation rate in X: 0.0000 m/y
430Translation rate in Y: 0.0000 m/y
431Translation rate in Z: 0.0000 m/y
432Rotation in X at epoch To: 0.150 mas
433Rotation in Y at epoch To: 0.020 mas
434Rotation in Z at epoch To: 0.021 mas
435Rotation rate in X: 0.000 mas/y
436Rotation rate in Y: 0.000 mas/y
437Rotation rate in Z: 0.000 mas/y
438Scale at epoch To : 0.000000000000
439Scale rate: -0.000000000000 /y
440To: 2000.0
441</pre>
442</p>
443
444<p>
445<u>SIRGAS95:</u> The formulars for the transformation 'ITRF2005-&gt;SIRGAS95' were provided via personal communication from Gustavo Acuha, Laboratorio de Geodesia Fisica y Satelital at Zulia University (LGFS-LUZ), parameters based on values from Table 4.1 of "Terrestrial Reference Frames (April 10, 2009), Chapter 4" in http://tai.bipm.org/iers/convupdt/convupdt_c4.html.</u>.
446</p>
447<p>
448<pre>
449Translation in X at epoch To: 0.0077 m
450Translation in Y at epoch To: 0.0058 m
451Translation in Z at epoch To: -0.0138 m
452Translation rate in X: 0.0000 m/y
453Translation rate in Y: 0.0000 m/y
454Translation rate in Z: 0.0000 m/y
455Rotation in X at epoch To: 0.000 mas
456Rotation in Y at epoch To: 0.000 mas
457Rotation in Z at epoch To: -0.003 mas
458Rotation rate in X: 0.000 mas/y
459Rotation rate in Y: 0.000 mas/y
460Rotation rate in Z: 0.000 mas/y
461Scale at epoch To : 0.00000000157
462Scale rate: -0.000000000000 /y
463To: 1995.4
464</pre>
465</p>
466
467<p>
468<u>Custom:</u> The default numbers shown as examples are those for a transformation from ITRF2005 to ETRF2000'.
469</p>
470
471
472<p><a name="ephcsave"><h4>4.6.4 Save - optional</h4></p>
473<p>
474The clock and orbit corrections streamed by BNS to the NTRIP Caster can be logged locally. Specify a full 'Save stream' path here to save this information to a local file. Default value for 'Save stream' is an empty option field, meaning that logging is disabled.
475</p>
476<p>
477The file is in plain ASCII format comprising records containing the following set of parameters:
478</p>
479
480<p>
481<ul>
482<li>GPS Week</li>
483<li>Second in GPS Week</li>
484<li>GNSS Indicator and Satellite Vehicle Pseudo Random Number</li>
485<li>IOD referring to Broadcast Ephemeris set</li>
486<li>Clock Correction to Broadcast Ephemeris [m]</li>
487<li>Radial Component of Orbit Correction to Broadcast Ephemeris [m]</li>
488<li>Along-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
489<li>Cross-track Component of Orbit Correction to Broadcast Ephemeris [m]</li>
490</ul>
491</p>
492<p>
493The following is an example file contents based on combined orbit and clock corrections for GPS and GLONASS carried in RTCM Version 3.x message Type 1060 and 1066:
494</p>
495<p>
496<pre>
4971489 325606.0 G31 18 -1.021 0.110 -1.308 -0.120
4981489 412006.0 R10 18 7.342 1.393 4.858 -2.634
4991489 412006.0 R19 18 4.696 2.358 1.707 -2.907
500...
5011489 325607.0 G30 80 6.022 0.591 -0.318 0.022
5021489 325607.0 G31 18 -1.022 0.110 -1.308 -0.120
5031489 412007.0 R10 18 7.341 1.390 4.860 -2.636
5041489 412007.0 R19 18 4.698 2.356 1.706 -2.906
505...
506</pre>
507</p>
508
509<p><a name="ephcom"><h4>4.6.5 Center of Mass - optional</h4></p>
510<p>
511BNS allows to either refer orbit/clock corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM.
512</p>
513
514<p><a name="brdc"><h4>4.7. Broadcast Ephemeris</h4></p>
515<p>
516BNS can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an NTRIP Caster.
517</p>
518
519<p><a name="brdcserver"><h4>4.7.1 Host &amp; Port - optional</h4></p>
520<p>
521Specify the 'Host' IP name or number of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris.
522</p>
523<p>
524Enter the NTRIP Caster's IP 'Port' number for stream upload. Note that NTRIP Casters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
525</p>
526
527<p><a name="brdcmount"><h4>4.7.2 Mountpoint &amp; Password - mandatory if 'Host' is set</h4></p>
528<p>
529Each stream on an NTRIP Caster is defined using a unique source ID called mountpoint. An NTRIP Server like BNS uploads a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify here the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.
530</p>
531
532<p><a name="brdcsmpl"><h4>4.7.3 Sampling - mandatory if 'Host' is set</h4></p>
533Select the Broadcast Ephemeris sampling interval in seconds. Defaut is '5' meaning that a complete set of Broadcast Ephemeris is uploaded every 5 seconds.
534</p>
535
536<p><a name="clkrnx"><h4>4.8. RINEX Clocks</h4></p>
537<p>
538The clock corrections generated by BNS can be logged separately in Clock RINEX format. The file naming follows the RINEX convention.
539<p>
540
541</p>
542Note that clocks in the Clock RINEX files are not corrected for the 2nd-order relativistic effect.
543</p>
544
545<p><a name="clkdir"><h4>4.8.1 Directory - optional</h4></p>
546<p>
547Here you can specify the path to where the Clock RINEX files will be stored. If the specified directory does not exist, BNS will not create Clock RINEX files. Default value for 'Directory' is an empty option field, meaning that logging of Clock RINEX files is disabled.
548</p>
549
550<p><a name="clkint"><h4>4.8.2 Interval &amp; Sampling - mandatory if 'Directory' is set</h4></p>
551<p>
552Select the length of the Clock RINEX file generated. The default value is 1 day.
553</p>
554
555<p>
556Select the Clock RINEX sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into Clock RINEX. This is the default value.
557</p>
558
559<p><a name="orb"><h4>4.9. SP3 Orbits</h4></p>
560<p>
561The orbit corrections generated by BNS can be logged separately in SP3 Orbit files. The file naming follows the IGS convention.
562</p>
563</p>
564Note that clocks in the SP3 Orbit files are not corrected for the 2nd-order relativistic effect.
565</p>
566
567<p><a name="orbdir"><h4>4.9.1 Directory - optional</h4></p>
568<p>
569Here you can specify the path to where the SP3 Orbit files will be stored. If the specified directory does not exist, BNS will not create SP3 Orbit files. Default value for 'Directory' is an empty option field, meaning that logging of SP3 Orbit files is disabled.
570</p>
571
572<p><a name="orbint"><h4>4.9.2 Interval &amp; Sampling - mandatory if 'Directory' is set</h4></p>
573<p>
574Select the length of the SP3 Orbit file generated. The default value is 1 day.
575</p>
576<p>
577Select the SP3 Orbit file sampling interval in seconds. A value of zero '0' tells BNS to store all received epochs into SP3 Orbit files. This is the default value.
578</p>
579
580<p><a name="bottom"><h4>4.10. Bottom Menu Bar</h4></p>
581<p>
582The bottom menu bar allows to start or stop the execution of BNS and provides access to BNC's online help funtion.
583</p>
584
585<p><a name="start"><h4>4.10.1 Start</h4></p>
586<p>
587Hit 'Start' to start receiving IGS orbits and clocks and convert them into corrections to Broadcast Ephemeris. Note that when started, BNS by default will begin with new files which might overwrite existing files when necessary unless the option 'Append files' is ticked.
588</p>
589
590<p><a name="stop"><h4>4.10.2 Stop</h4></p>
591<p>
592Hit the 'Stop' button in order to stop BNS.
593</p>
594
595<p><a name="cmd"><h4>4.11. Command Line Options</h4></p>
596<p>
597Command line options are available to run BNS in 'no window' mode or let it read a specific configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNS.ini'.
598</p>
599
600<p><a name="nw"><h4>4.11.1 No Window - optional</h4></p>
601<p>
602Apart from its regular windows mode, BNS can be started on all systems as a background job with command line option '-nw'. BNS will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNS using Windows Task Manager when running it in 'no window' mode on Windows systems.
603</p>
604<p>
605Example:<br><br>
606bns.exe -nw
607</p>
608
609<p><a name="conffile"><h4>4.11.2 Configuration File - optional</h4></p>
610The default configuration file name is 'BNS.ini'. You may change this name at startup time using the command line option '--conf &#060;<u>confFileName</u>&#062;'. This allows to run several BNS jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a file name. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNS is started.
611</p>
612<p>
613Example:<br><br>
614./bns --conf MyConfig.ini
615</p>
616<p>
617This leads to a BNS job using configuration file 'MyConfig.ini'. The configuration file will be saved in the current working directory.
618</p>
619
620
621</p>
622<p><a name="limits"><h3>5. Limitations</h3></p>
623<ul>
624<li>
625In Qt-based desktop environments (such as KDE) on Unix/Linux/Mac platforms users may experience a crash at startup even when BNS is run in the background using the '-nw' option. This is a known bug most likely resulting from an incompatibility of Qt libraries in the environment and in BNS. Entering the command 'unset SESSION_MANAGER' before running BNS may help as a work-around.
626</li>
627<li>
628Currently BNS can only generate premature RTCM Version 3.x message Type 1057-1068 (see RTCM document 091-2009-SC104-542 'Version 3 Proposed Messages â&#8364;&#8220; Set 10') . Note that what is implemented in BNS is just a temporary solution.
629</li>
630<li>
631We experienced some limitation with the Standard Version of Microsoft Windows related to socket communication where sockets are not always handled properly. Since BNS makes intensive use of communication through sockets, we recommend to use the Server Version of Microsoft Windows when running BNS continuously for extended period on a Windows platform.
632</li>
633<li>
634Once BNS has been started, its configuration can not be changed unless without a restart. An on-the-fly reconfiguration is not implemented.
635</li>
636<br>
637</ul>
638<p><a name="authors"><h3>6. Authors</h3></p>
639<p>
640The BKG Ntrip State Space Server (BNS) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Geodesy. BNS includes a GNU GPL open source RTCM 3.x encoder, written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld.
641</p>
642<p>
643Georg Weber<br>
644Federal Agency for Cartography and Geodesy (BKG)<br>
645Frankfurt, Germany<br>
646[euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
647</p>
648
649<p><a name="annex"><h3>7. Annex</h3></p>
650<p>
6517.1. <a href=#history>Revision History</a><br>
6527.2. <a href=#rtcm>RTCM</a><br>
653&nbsp; &nbsp; &nbsp; 7.2.1 RTCM <a href=#ntrip>NTRIP</a><br>
654&nbsp; &nbsp; &nbsp; 7.2.2 RTCM <a href=#rtcm3>Version 3.x</a><br>
6557.3. <a href=#config>Configuration Example</a><br>
6567.4. <a href=#links>Links</a><br>
657</p>
658
659<p><a name=history><h4>7.1 Revision History</h4></p>
660</p>
661<table>
662<tr></tr>
663
664<tr>
665<td>Dec 2008 &nbsp;</td><td>Version 1.0 &nbsp;</td>
666<td>[Add] Source code and binaries published.</td>
667</tr>
668
669<tr>
670<td>Marc 2010 &nbsp;</td><td>Version 1.1 &nbsp;</td>
671<td>[Add] Upgrade to Qt Version 4.4.3<br> [Add] Enable/disable tab widgets<br> [Add] User defined configuration file name<br> [mod] Switch to configuration files in ini-Format<br> [Add] Auto start<br> [Add] Drag and drop ini files<br> [Add] Optional reference to Center of Mass<br> [Mod] Update following RTCM 091-2009-SC104-542 document<br> [Add] NAD, GDA, SIRGAS transformations</td>
672</tr>
673
674</table>
675</p>
676
677<p><a name="rtcm"><h4>7.2. RTCM</h4></p>
678
679<p>
680The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which governmental and non-governmental members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104.
681</p>
682<p>
683Personal copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>.
684</p>
685
686<p><a name="ntrip"><h4>7.2.1 NTRIP</h4></p>
687
688<p>
689'Networked Transport of RTCM via Internet Protocol' Version 1.0 (NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
690</p>
691
692<p>
693NTRIP Version 1.0 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
694</p>
695
696<p>
697NTRIP is implemented in three system software components: NTRIP clients, NTRIP servers and NTRIP broadcasters. The NTRIP broadcaster is the actual HTTP server program whereas NTRIP client and NTRIP server are acting as HTTP clients. The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request.
698</p>
699
700<p>
701NTRIP is an open none-proprietary protocol. Major characteristics of NTRIP's dissemination technique are:
702<ul>
703<li>Based on the popular HTTP streaming standard; comparatively easy to implement when having limited client and server platform resources available.</li>
704<li>Application not limited to one particular plain or coded stream content; ability to distribute any kind of GNSS data.</li>
705<li>Potential to support mass usage; disseminating hundreds of streams simultaneously for thousands of users possible when applying modified Internet Radio broadcasting software.</li>
706<li>Considering security needs; stream providers and users don't necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks.</li>
707<li>Enables streaming over mobile IP networks because of using TCP/IP.</li>
708</ul>
709</p>
710
711<p>
712The NTRIP Version 2 transport protocol is not implemented in BNS.
713</p>
714
715<p><a name="rtcm3"><h4>7.2.2 RTCM Version 3.x</h4></p>
716<p>
717RTCM Version 3.x has been developed as a better alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be efficient, easy to use, and easily adaptable to new situations.
718</p>
719RTCM is in the process of developing new Version 3 message types to carry satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following premature messages currently under discussion of relevance to BNS are listed here:
720<p>
721<ul>
722<li>Message type 1057: GPS orbit corrections to Broadcast Ephemeris</li>
723<li>Message type 1058: GPS clock corrections to Broadcast Ephemeris</li>
724<li>Message type 1059: GPS code biases</li>
725<li>Message type 1060: Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>
726<li>Message type 1061: GPS User Range Accuracy (URA)</li>
727<li>Message type 1062: High-rate GPS clock corrections to Broadcast Ephemeris</li>
728<li>Message type 1063: GLONASS orbit corrections to Broadcast Ephemeris</li>
729<li>Message type 1064: GLONASS clock corrections to Broadcast Ephemeris</li>
730<li>Message type 1065: GLONASS code biases</li>
731<li>Message type 1066: Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>
732<li>Message type 1067: GLONASS User Range Accuracy (URA)</li>
733<li>Message type 1068: High-rate GLONASS clock corrections to Broadcast Ephemeris</li>
734</ul>
735</p>
736<p>
737RTCM Version 3.x streams carrying these messages may be used for example to support real-time Precise Point Positioning (PPP) applications using the 'state space' approach.
738</p>
739
740<p><a name="config"><h4>7.3. Configuration Example</h4></p>
741<p>
742The following table's left column is an example for the contents of a configuration file 'BNS.ini'. It enables the upload of streams CLCK1 and CLCK2 to www.igs-ip.net. Clock RINEX files and SP3 Orbit files are saved to a directory /home/weber/rinex :
743</p>
744<table>
745<tr></tr>
746<tr><td><b>Option</b></td><td><b>Affiliation</b></td></tr>
747<tr><td>[General]</td><td>Settings: Group</td></tr>
748<tr><td>proxyHost=</td><td>Proxy: Host</td></tr>
749<tr><td>proxyPort=</td><td>Proxy: Port</td></tr>
750<tr><td>logFile=/home/weber/rinex/bns.log</td><td>General: Logfile (full path)</td></tr>
751<tr><td>fileAppend=0</td><td>General: Append files</td></tr>
752<tr><td>autoStart=0</td><td>General: Auto start</td></tr>
753<tr><td>ephHost=clock-ip.bkg.bund.de</td><td>RINEX Ephemeris: Host</td></tr>
754<tr><td>ephPort=6000</td><td>RINEX Ephemeris: Port</td></tr>
755<tr><td>ephEcho=/home/weber/rinex/eph.rnx</td><td>RINEX Ephemeris: Save (full path)</td></tr>
756<tr><td>clkPort=7000</td><td>Clocks &amp; Orbits: Listening port</td></tr>
757<tr><td>inpEcho=/home/weber/rinex/ClocksOrbits.dat</td><td>Clocks &amp; Orbits: Save (full path)</td></tr>
758<tr><td>outHost1=www.igs-ip.net</td><td>Broadcast Corrections I: Host</td></tr>
759<tr><td>outPort1=2101</td><td>Broadcast Corrections I: Port</td></tr>
760<tr><td>mountpoint_1=CLCK1</td><td>Broadcast Corrections I: Mountpoint</td></tr>
761<tr><td>password1=pw</td><td>Broadcast Corrections I: Password</td></tr>
762<tr><td>refSys_1=IGS05</td><td>Broadcast Corrections I: System</td></tr>
763<tr><td>outFile_1=/home/weber/rinex/CLCK1</td><td>Broadcast Corrections I: Save (full path)</td></tr>
764<tr><td>CoM_1=2</td><td>Broadcast Corrections I: Center of Mass</td></tr>
765<tr><td>outHost2=www.igs-.net</td><td>Broadcast Corrections II: Host</td></tr>
766<tr><td>outPort2=2101</td><td>Broadcast Corrections II: Port</td></tr>
767<tr><td>mountpoint_2=CLCK2</td><td>Broadcast Corrections II: Mountpoint</td></tr>
768<tr><td>password2=pw</td><td>Broadcast Corrections II: Password</td></tr>
769<tr><td>refSys_2=ETRF2000</td><td>Broadcast Corrections II: System</td></tr>
770<tr><td>outFile_2=/home/weber/rinex/CLCK2</td><td>Broadcast Corrections II: Save (full path)</td></tr>
771<tr><td>CoM_2=0</td><td>Broadcast Corrections II: Center of Mass</td></tr>
772
773<tr><td>outHost3=www.igs-.net</td><td>Broadcast Corrections III: Host</td></tr>
774<tr><td>outPort3=2101</td><td>Broadcast Corrections III: Port</td></tr>
775<tr><td>mountpoint_3=CLCK3</td><td>Broadcast Corrections III: Mountpoint</td></tr>
776<tr><td>password3=pw</td><td>Broadcast Corrections III: Password</td></tr>
777<tr><td>refSys_3=ETRF2000</td><td>Broadcast Corrections III: System</td></tr>
778<tr><td>outFile_3=/home/weber/rinex/CLCK3</td><td>Broadcast Corrections III: Save (full path)</td></tr>
779<tr><td>CoM_3=0</td><td>Broadcast Corrections III: Center of Mass</td></tr>
780
781<tr><td>outHost4=www.igs-.net</td><td>Broadcast Corrections IV: Host</td></tr>
782<tr><td>outPort4=2101</td><td>Broadcast Corrections IV: Port</td></tr>
783<tr><td>mountpoint_4=CLCK4</td><td>Broadcast Corrections IV: Mountpoint</td></tr>
784<tr><td>password4=pw</td><td>Broadcast Corrections IV: Password</td></tr>
785<tr><td>refSys_4=ETRF2000</td><td>Broadcast Corrections IV: System</td></tr>
786<tr><td>outFile_4=/home/weber/rinex/CLCK4</td><td>Broadcast Corrections IV: Save (full path)</td></tr>
787<tr><td>CoM_4=0</td><td>Broadcast Corrections IV: Center of Mass</td></tr>
788
789<tr><td>outHost5=www.igs-.net</td><td>Broadcast Corrections V: Host</td></tr>
790<tr><td>outPort5=2101</td><td>Broadcast Corrections V: Port</td></tr>
791<tr><td>mountpoint_5=CLCK5</td><td>Broadcast Corrections V: Mountpoint</td></tr>
792<tr><td>password5=pw</td><td>Broadcast Corrections V: Password</td></tr>
793<tr><td>refSys_5=ETRF2000</td><td>Broadcast Corrections V: System</td></tr>
794<tr><td>outFile_5=/home/weber/rinex/CLCK5</td><td>Broadcast Corrections V: Save (full path)</td></tr>
795<tr><td>CoM_5=0</td><td>Broadcast Corrections V: Center of Mass</td></tr>
796
797<tr><td>outHost6=www.igs-.net</td><td>Broadcast Corrections VI: Host</td></tr>
798<tr><td>outPort6=2101</td><td>Broadcast Corrections VI: Port</td></tr>
799<tr><td>mountpoint_6=CLCK6</td><td>Broadcast Corrections VI: Mountpoint</td></tr>
800<tr><td>password6=pw</td><td>Broadcast Corrections VI: Password</td></tr>
801<tr><td>refSys_6=ETRF2000</td><td>Broadcast Corrections VI: System</td></tr>
802<tr><td>outFile_6=/home/weber/rinex/CLCK6</td><td>Broadcast Corrections VI: Save (full path)</td></tr>
803<tr><td>CoM_6=0</td><td>Broadcast Corrections VI: Center of Mass</td></tr>
804
805<tr><td>outHostEph=www.igs-ip.net</td><td>Broadcast Ephemeris: Host</td></tr>
806<tr><td>outPortEph=2101</td><td>Broadcast Ephemeris: Port</td></tr>
807<tr><td>mountpoint_Eph=BRDC0</td><td>Broadcast Ephemeris: Mountpoint</td></tr>
808<tr><td>passwordEph=pass</td><td>Broadcast Ephemeris: Password</td></tr>
809<tr><td>samplEph=5</td><td>Broadcast Ephemeris: Sampling</td></tr>
810<tr><td>trafo_dx=0.0541</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
811<tr><td>trafo_dy=0.0502</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
812<tr><td>trafo_dz=-0.0538</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
813<tr><td>trafo_dxr=-0.0002</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
814<tr><td>trafo_dyr=0.0001</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
815<tr><td>trafo_dzr=-0.0018</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
816<tr><td>trafo_ox=0.000891</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
817<tr><td>trafo_oy=0.005390</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
818<tr><td>trafo_oz=-0.008712</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
819<tr><td>trafo_oxr=0.000081</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
820<tr><td>trafo_oyr=0.000490</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
821<tr><td>trafo_ozr=-0.000792</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
822<tr><td>trafo_sc=0.40</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
823<tr><td>trafo_scr=0.08</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
824<tr><td>trafo_t0=2000.0</td><td>Broadcast Corrections: System &gt; Custom</td></tr>
825<tr><td>rnxPath=/home/weber/rinex</td><td>RINEX Clocks: Directory</td></tr>
826<tr><td>rnxIntr=1 day</td><td>RINEX Clocks: Interval</td></tr>
827<tr><td>rnxSampl=30</td><td>RINEX Clocks: Sampling</td></tr>
828<tr><td>sp3Path=/home/weber/rinex</td><td>SP3 Orbits: Directory</td></tr>
829<tr><td>sp3Intr=1 day</td><td>SP3 Orbits: Interval</td></tr>
830<tr><td>sp3Sampl=300</td><td>SP3 Orbits: Sampling</td></tr>
831<tr><td>startTab=0</td><td>Internal memory: Top tab</td></tr>
832<tr><td>font=&quot;Helvetica [Adobe],8,-1,5,75,0,0,0,0,0&quot;</td><td>Internal memory: Used font</td></tr>
833</table>
834
835<p><a name="links"><h4>7.4 Links</h4></p>
836<table>
837<tr></tr>
838<tr><td>NTRIP &nbsp;</td><td><u>http://igs.bkg.bund.de/index_ntrip.htm</u></td></tr>
839<tr><td>EUREF-IP NTRIP broadcaster &nbsp;</td><td><u>http://www.euref-ip.net/home</u></td></tr>
840<tr><td>IGS-IP NTRIP broadcaster &nbsp;</td><td><u>http://www.igs-ip.net/home</u></td></tr>
841<tr><td>NTRIP broadcaster overview &nbsp;</td><td><u>http://www.rtcm-ntrip.org/home</u></td></tr>
842<tr><td>EUREF-IP Project &nbsp;</td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr>
843<tr><td>Real-time IGS Pilot Project &nbsp;</td><td><u>http://www.rtigs.net/pilot</u></td></tr>
844<tr><td>Radio Technical Commission<br>for Maritime Services &nbsp;</td><td><u>http://www.rtcm.org</u>
845</table>
846
Note: See TracBrowser for help on using the repository browser.