#27 closed enhancement (fixed)
hints with respect to RINEX 3.02 default header
Reported by: | stuerze | Owned by: | stuerze |
---|---|---|---|
Priority: | normal | Component: | BNC |
Version: | Keywords: | RINEX observations | |
Cc: | stuerze, fgnievinski@… |
Description
message from fgnievinski@…:
There are a few issues when saving RINEX observation files, though.
(a) Two mandatory header lines are missing (RINEX version 3.02):
"GLONASS SLOT / FRQ #"
"GLONASS COD/PHS/BIS"
(b) The default skeleton includes observation codes that could benefit from some improvement, as follows:
(b.1) C5, D5, L5, S5 are invalid, as they lack the third character, denoting the attribute (tracking mode or channel); most commonly it's "X", thus C5X, D5X, L5X, S5X.
(b.2) The modernized GPS L2 signal ("L2C") is being reported under observation codes C2C, D2C, L2C, S2C. Actually, the "C" attribute is reserved for the C/A signal (as in C1C, D1C, L1C, S1C), whose transmission in the L2 band remains a technical possibility (according to Table 3-III, "Signal Configuration", of the GPS ICD), even in pre-modernized or legacy GPS satellites, although as far as I know it is very rare. The L2C signal normally is reported under C2X, D2X, L2X, S2X.
(b.3) The legacy GPS L2 signal ("L2-P(Y)") is being reported under observation codes C2P, D2P, L2P, S2P. This is only true when anti-spoofing is disabled, which again is very rare. Under encrypted broadcast, observation codes C2W, D2W, L2W, S2W are employed for civilians (and C2Y, D2Y, L2Y, S2Y for military receivers).
(b.4) In summary, may I suggest the following new default GPS observation codes:
G 20 C1C L1C D1C S1C C1W L1W D1W S1W C2X L2X D2X S2X C2W SYS / # / OBS TYPES
L2W D2W S2W C5X D5X L5X S5X SYS / # / OBS TYPES
These correspond to the majority of stations, see, e.g.:
<http://www.bernese.unibe.ch/publist/2013/post/SL_euref2013_rinex3.pdf>
Attachments (0)
Change History (7)
comment:1 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 10 years ago
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 by , 10 years ago
citation from ftp://igs.org/pub/data/format/rinex302.pdf (A8):
SYS / # / OBS TYPES
(Continued)
Attribute:
blank : for types I and X (all) or unknown tracking mode
comment:6 by , 10 years ago
RINEX Version 3.02
REVISION HISTORY
(...)
29-Nov-2012 Removed the option of supporting unknown tracking mode from Section 5.1.
comment:7 by , 9 years ago
So it seems BNC can generate valid RINEX v. 3.01 files but not the latest v. 3.02; at least the version number output should be made consistent.
The following mandatory RINEX V3 Header lines valid for OBS files are added in BNC2.12:
They will be filled with values in case of merging existing RINEX files.
In case of RINEX file generation from RTCM streams these lines are added as well but so far without any values. In a next step, "GLONASS SLOT / FRQ #" information will be available from skeleton files. If so, this line will be filled with values in RINEX files generated from RTCM streams as well. Information required to fill "GLONASS SLOT / FRQ #" "GLONASS COD/PHS/BIS" is neither available from RTCM streams nor from station logfiles. As soon this information is provided in any way it will be filled in RINEX files generated from RTCM streams as well.
Default RINEX 3 Observation types are defined as follows: