|
@@ -1269,5 +1269,5 @@
-8.2. RTCM
+6.2. RTCM
@@ -1277,5 +1277,5 @@
-8.2.1 NTRIP Version 1
+6.2.1 NTRIP Version 1
@@ -1316,5 +1316,5 @@
-8.2.1 NTRIP Version 2
+6.2.1 NTRIP Version 2
@@ -1334,5 +1334,5 @@
-8.2.3 RTCM Version 2.x
+6.2.3 RTCM Version 2.x
Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
@@ -1372,5 +1372,5 @@
-
8.2.4 RTCM Version 3.x
+6.2.4 RTCM Version 3.x
RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3.x standard is intended to correct these weaknesses.
@@ -1400,5 +1400,5 @@
-
8.3. RTIGS
+6.3. RTIGS
RTIGS stands for a data format and transport protocol for GPS observations. It was defined by the Real-Time IGS Working Group (RTIGS WG). Its definition is based on the SOC format. Every RTIGS record has one of the following numbers:
@@ -1453,5 +1453,5 @@
-8.3.1 SOC
+6.3.1 SOC
The SOC format has been designed in July 1999 by the Jet Propulsion Laboratory (JPL) and the California Institute of Technology (CalTech) to transport 1Hz GPS data with minimal bandwidth over the open Internet. SOC follows the 'little-endian' byte order meaning that the low-order byte of a number is stored in memory at the lowest address, and the high-order byte at the highest address. Because the transport layer is UDP, the format does not include sync bits, a checksum, or cyclic redundancy checksum (CRC). SOC allows to transport the GPS observable CA, P1, P2, L1, and L2, efficiently compressed down to 14 bytes with 1 mm range resolution and 0.02 mm phase resolution. SOC contains epochs for cycle slips, a stand-alone time-tag per epoch, a minimum representation of the receiver's clock solution, 3 SNR numbers, a unique site id, a modulo 12 hour sequence number and flags for receiver type and GPS health. SOC's simple structure comprises an 8 byte header, a 9 byte overhead for timetag, number of gps, etc., plus 21 data bytes per gps.
@@ -1462,5 +1462,5 @@
-8.4. Configuration Example
+6.4. Configuration Example
The following table's left column is an example for the contents of a configuration file 'BNC.ini'. It enables the retrieval of stream ACOR0 form www.euref-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :
@@ -1528,5 +1528,5 @@
-8.5 Links
+6.5 Links