-Differential 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 'ObservationSpace Representation' (OSR). +Differential 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).
@@ -1341,8 +1341,11 @@
@@ -1362,27 +1365,23 @@
-The orbit and clock corrections do not include local effects (like Ocean Loading or Solid Earth Tides) or atmospheric effects (Ionosphere and/or troposphere). Depending on the accuracy of your application you should correct for such effects by other means. There is currently no RTCM SSR message for ionospheric state parameters. Such messages are needed for accurate single frequency applications. The development of Iono messages will be the next step in the schedule of the RTCM State Space Representation Working Group. -
- --Broadcast Corrections can be saved by BNC in files. The file name convention for Broadcast Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C". -
- --Saved files contain blocks of records in plain ASCII format where - separate for each GNSS, message type, stream, and epoch - the begin of a block is indicated by a line like (examples): -
-
-! Orbits/Clocks: 30 GPS 0 Glonass CLK11
-or
-! Orbits/Clocks: 0 GPS 19 Glonass CLK11
-
-Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next. -
--The first five parameters in each Broadcast Corrections record are: -
--
+While we have a plain ASCII standard for saving broadcast ephemeris in RINEX Navigation files, we don't have an equivalent standard for corrections to broadcast ephemeris. Hence BNC saves Broadcast Corrections files following its own format definition. The file name convention for Broadcast Correction files follows the convention for RINEX Version 2 files except for the last character of the file name suffix which is set to "C". +
+ ++Saved files contain blocks of records in plain ASCII format. The first record in each block contains the following 10 parameters: +
++
+Example for block 'ORBIT' carrying orbit corrections +
++> ORBIT 2015 06 17 11 43 35.0 2 53 CLK93 +G01 9 0.5134 0.3692 0.6784 0.0000 -0.0000 -0.0000 +G02 25 57.6817 139.0492 -91.3456 0.5436 -0.6931 1.0173 +G03 79 -32.1768 191.8368 -121.6540 0.2695 0.2296 0.4879 +... +G32 82 1.8174 1.1704 0.2200 -0.0002 -0.0000 -0.0001 +R01 59 0.7819 -0.6968 0.7388 -0.0001 0.0004 0.0004 +R02 59 0.5816 -0.5800 -0.2004 0.0001 -0.0006 0.0001 +R03 59 0.4635 -0.9104 -0.3832 0.0001 0.0001 0.0005 +... +R24 59 0.5935 2.0732 -0.6884 -0.0000 0.0004 0.0003 ++ +
+The 'satellite records' in this block provide the following information: +
-In case of RTCM message types 1057 or 1063 (see Annex) these parameters are followed by -
--
-
-Undefined parameters would be set to zero "0.000".
Example:
-
-... -1057 0 1686 283200.0 G02 21 1.062 -0.791 1.070 -0.00025 -0.00031 -0.00005 -1057 0 1686 283200.0 G03 25 1.765 -2.438 -0.290 -0.00009 -0.00060 0.00028 -1057 0 1686 283200.0 G04 14 1.311 -0.862 0.334 0.00005 -0.00038 -0.00015 - -... -1063 0 1686 283200.0 R01 39 0.347 1.976 -1.418 0.00048 -0.00091 0.00008 -1063 0 1686 283200.0 R02 39 0.624 -2.092 -0.155 0.00005 -0.00054 0.00053 -1063 0 1686 283200.0 R03 39 0.113 5.655 -1.540 0.00003 -0.00079 -0.00003 -1063 0 1686 283200.0 R05 39 0.237 1.426 -1.282 0.00054 -0.00020 0.00027 -... --
+ +
+ +
+TBC
In case of RTCM message types 1058 or 1064 (see Annex) the first five parameters in each record are followed by