Changeset 2535 in ntrip

Timestamp:

Aug 4, 2010, 10:16:57 AM (14 years ago)

Author:

weber

Message:

More precise offline PPP description

File:

• trunk/BNC/bnchelp.html (modified) (4 diffs)

trunk/BNC/bnchelp.html

@@ -293 +293 @@
 </p>
 <p>
+Note that streams in a 'Raw output file' which shall later be used in an offline PPP calculation must all be encoded in the same format.
+</p>
+<p>
 The default value for 'Raw output file (full path)' is an empty option field, meaning that BNC will not save raw data into a file.
 </p>
@@ -479 +482 @@
 </p>
 <p>
-When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may beimportant to understand that they are not corrected for the 2nd-order relativistic effect. The 2nd-order relativistic effect is a periodic time correction defined as -2 (R * V) / c^2 where R * V is the scalar product of the satellite position and velocity and c is the speed of light.
+When 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 conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as dt =  -2 (R * V) / c^2 where R * V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006.
 </p>
 
@@ -1065 +1068 @@
 
 <p>
-Note that BNC's 'PPP Client' option can also be used in 'Offline Mode'. Apply the 'Offline Mode' command line options for that to read a file containing synchronized observations, orbit and clock corretors, and broadcast ephemeris. Such a file can be generated using BNC's 'Raw Output File' option. The first five characters of the file name read in 'Offline Mode' must then be the same as the specified PPP 'Mounpoint': If you produce a 'Raw Output File' named 'FFMJ1' then the PPP 'Mountpoint' needs to be also specified as 'FFMJ1' and the command line to execute BNC on a Windows system in 'Offline Mode' could look like:
+Note that BNC's 'PPP Client' option can also be used in 'Offline Mode'. Apply the 'Offline Mode' command line options for that to read a file containing synchronized observations, orbit and clock corretors, and broadcast ephemeris. Such a file can be generated using BNC's 'Raw output file' option. The first five characters of the file name read in 'Offline Mode' must then be the same as the specified PPP 'Mounpoint': If you produce a 'Raw output file' named 'FFMJ1' then the PPP 'Mountpoint' needs to be also specified as 'FFMJ1' and the command line to execute BNC on a Windows system in 'Offline Mode' could look like:
 </p>
 
 <p>
 bnc.exe --conf c:\temp\BNC.ppp --file c:\temp\FFMJ1 --format RTCM_3
+</p>
+
+<p>
+Streams in a 'Raw output file' which shall later be used in an offline PPP calculation must all be encoded in the same format.
 </p>
 
@@ -1440 +1447 @@
 </p>
 <p>
-Note that when running BNC in offline mode, it will use options for file saving, interval, sampling, PPP etc. from its configuration file.
+Note that when running BNC in offline mode, it will use options for file saving, interval, sampling, PPP etc. from its configuration file. Note further that only those data in the file will be processd offline which are encoded as specified with the --format option. 
 </p>