- Timestamp:
- Jul 16, 2009, 3:30:47 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
TabularUnified trunk/BNC/bnchelp.html ¶
r1870 r1871 410 410 </p> 411 411 <p> 412 When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it isimportant 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.412 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 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. 413 413 </p> 414 414 … … 482 482 </pre> 483 483 <p> 484 In case of RTCM message types 1058 or 1064 the first f ourparameters are followed by484 In case of RTCM message types 1058 or 1064 the first five parameters are followed by 485 485 </p> 486 486 <ul> … … 505 505 </p> 506 506 <p> 507 In case of RTCM message types 1060 or 1066 the first f ourparameters are followed by507 In case of RTCM message types 1060 or 1066 the first five parameters are followed by 508 508 <p> 509 509 <ul> … … 537 537 </p> 538 538 <p> 539 In case of RTCM message types 1059 or 1065 the first f ourparameters are followed by539 In case of RTCM message types 1059 or 1065 the first five parameters are followed by 540 540 <ul> 541 541 <li>Number of Code Biases</li>
Note:
See TracChangeset
for help on using the changeset viewer.