The 1Hz RINEX files for 15min intervals as converted from streams are currently made available from the EPN Regional Data Centre BKG only for a guaranteed period of three months. They may be deleted at any time later without prior notice. The files are converted from streams coming either in RTCM Version 2, RTCM Version 3, or RTIGS (to be more precise: SOC) stream format. Which stream and stream conversion tool has been used is described in the RINEX headers. Because of the real-time stream conversion, the provided RINEX files may contain small gaps of a couple of seconds or even become completely unavailable because of a longer lasting communication problem.

Only C1, C2, P1, P2, L1, L2, S1, and S2 observations can be provided. Which observables become available depends on the setup of the receiver and the stream format used. Note the following specifications for the high-rate RINEX files from streams:

(a) RINEX files from RTCM Version 2 streams are based on the message types 18 and 19 only. They do not carry signal-to-noise ratio values.

(b) RINEX files from RTCM Version 3.x streams can only transport one code observable per frequency. The resolution of pseudo-ranges is 0.02 m. The carrier phase resolution is 0.5 mm. The signal-to-noise ratios 'S' are also logged mapped to integer numbers 1 to 9. Only the RTCM Version 3 message types 1002, 1004, 1010, and 1012 are properly converted. If a stream contains message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX because all values will be stored modulo 299792.458 (speed of light).

(c) RINEX files from RTIGS streams can not contain GLONASS or SBAS observations because RTIGS streams are based on the SOC format which does not allow the transport of observations from other systems than GPS. The pseudo-range resolution is 0.001 m and the carrier phase resolution is 0.02 mm.