Changeset 10946 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Jun 24, 2026, 4:39:53 PM (3 weeks ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r10945 r10946 5640 5640 </p> 5641 5641 <p> 5642 For GLONASS satellites, that APC/CoM offset is rotated into the satellite-fixed frame using the satellite's 5643 yaw attitude. BNC assumes the nominal Sun-pointing yaw-steering law used for the other GNSS systems, except 5644 close to the orbit noon and midnight points when the Sun's elevation above the orbital plane (the 'beta' 5645 angle) is small. There, GLONASS-M satellites are known to stop tracking that law and instead hold the yaw 5646 angle fixed, following the model described in Dilssner, Springer, Flohrer, Dow (2011), 'The GLONASS-M 5647 satellite yaw-attitude model', Advances in Space Research 47(1), 160-171. Without that correction, the 5648 converted GLONASS CoM position can be off by several decimeters in the along-track and cross-track 5649 components in that situation. The maximum yaw rate used to decide when GLONASS-M can no longer follow the 5650 nominal law (0.25 deg/s) is taken from the literature and not calibrated against any specific satellite, so 5651 results should be checked against independently known attitude or orbit information where high accuracy on 5652 GLONASS is required. 5653 </p> 5654 <p> 5642 5655 Note that clocks in the SP3 orbit files are not corrected for the conventional periodic relativistic effect. 5643 5656 </p>
Note:
See TracChangeset
for help on using the changeset viewer.
