Rinex数据格式说明
观测文件的文件头
带*的内容为可选内容，在格式中，以类型开头，紧跟所占字节数。
F（float）表示浮点数，如F9.2理解为9位（含小数点）浮点数，保留到小数点后两位；
X表示空格，如11X表示11位空位；
A（ASCII）表示ASCII字码，如A1表示1位ASCII字码；
I（integer）表示整数，如I6表示，6位整数；
数据和数据之间以“，”隔开；
连续多个相同类型则在类型前面加上总个数，如2I6表示两组6位整数。
RINEX-2.10 Format
--------------------------------------------------------------------------------
Get DATA
June 8, 2001
RINEX: The Receiver Independent Exchange Format Version 2.10
************************************************************
Werner Gurtner
Astronomical Institute
University of Berne
Contents:
********
Revision History
0.1 Revision Summary
0.2 First Revision
0.3 Later Revisions
0.4 Version 2.10 Modifications
0.5 Version 2.10 Revisions
THE PHILOSOPHY OF RINEX
GENERAL FORMAT DESCRIPTION
DEFINITION OF THE OBSERVABLES
THE EXCHANGE OF RINEX FILES:
RINEX VERSION 2 FEATURES
5.1 Satellite Numbers:
5.2 Order of the Header Records:
5.3 Missing Items, Duration of the Validity of Values
5.4 Event Flag Records
5.5 Receiver Clock Offset
ADDITIONAL HINTS AND TIPS
6.1 Version 1 / Version 2
6.2 Leading Blanks in CHARACTER fields
6.3 Variable-length Records
6.4 Blank Fields
6.5 2-Digit Years
6.6 Fit Interval
6.7 Satellite Health
6.8 Transmission Time of Message (Navigation message file)
RINEX UNDER ANTISPOOFING (AS)
GLONASS Extensions
8.1 RINEX Observation File
8.1.1 Time System Identifier
8.1.2 Pseudorange Definition
8.1.3 More Than 12 Satellites per Epoch
8.2 RINEX Navigation Files for GLONASS
RINEX Extensions for Geostationary Satellites (GPS Signal Payloads)
9.1 RINEX Observation Files for GEO Satellites
9.2 RINEX Navigation Message Files for GEO Satellites
10. REFERENCES
11. RINEX VERSION 2.10 FORMAT DEFINITIONS AND EXAMPLES
GPS OBSERVATION DATA FILE - HEADER SECTION DESCRIPTION
GPS OBSERVATION DATA FILE - DATA RECORD DESCRIPTION
GPS NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
GPS NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
METEOROLOCICAL DATA FILE - HEADER SECTION DESCRIPTION
METEOROLOGICAL DATA FILE - DATA RECORD DESCRIPTION
GPS OBSERVATION DATA FILE - EXAMPLE
GPS NAVIGATION MESSAGE FILE - EXAMPLE
METEOROLOGICAL DATA FILE - EXAMPLE
GLONASS NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
GLONASS NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
GLONASS NAVIGATION MESSAGE FILE - EXAMPLE
GLONASS OBSERVATION FILE - EXAMPLE
MIXED GPS/GLONASS OBSERVATION FILE - EXAMPLE
GEOSTATIONARY NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
GEOSTATIONARY NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
MIXED GPS/GEO OBSERVATION FILE - EXAMPLE
GEO NAVIGATION MESSAGE FILE - EXAMPLE
0. REVISION HISTORY
0.1 Revision Summary
First Revision, April 1993
Clarification December 1993
Doppler Definition: January 1994
PR Clarification: October 1994
Wlfact Clarification: February 1995
Event Time Frame Clarification: May 1996
Minor errors in the examples A7/A8: May 1996
Naming convention for
January 1997
Continuation line clarifications: April 1997
GLONASS Extensions: April 1997
Met sensor description and position records: April 1997
Wavelength factor clarifications: April 1997
Error in example A12: CORR TO SYSTEM TIME, April 1997
Redefinition of sv clock params in GLONASS Nav Mess Files: March 1998
Naming conventions for compressed RINEX obs files: March 1998
GPS week: No roll-over, continuous number: March 1998
Error in compressed DOS file naming convention: July 1998
Table A13 contained blank satellite identifiers: Sept 1998
Discrepancy between Tables A5 and A9 removed: Sept 1998
Phase data format overflow: Clarification: Oct 1998
Message frame time Table A11: Clarification: Oct 1998
RINEX Version 2.10 Modifications: July 1999
Typo in paragraph 0.4 (epoch flag &1): Nov 1999
Clarification regarding trailing blanks: Dec 1999
Clarification regarding units of ZD,ZT, URA(GEO)
Clarification regarding time system identifier of GEO obs files
Clarification regarding time system identifier in TIME OF LAST record: Feb 2000
Addition of GEO examples: February 2000
Clarification of epoch field for event flag records: May 2000
Table A6: Typos in format definition of epoch: May 2000
Clarification of the GLONASS satellite identifier: June 2001
0.2 First Revision
The first documentation of the RINEX Version 2 Format was published by
W. Gurtner and G. Mader in the CSTG GPS Bulletin of September/October 1990.
The main reason for a revision is the new treatment of antispoofing data by
the RINEX format (see chapter 7). Chapter 4 gives a recommendation for data
compression procedures, especially useful when large amounts of data are
exchanged through computer networks. In Table A3 in the original paper the
definiton of the &PGM / RUN BY / DATE& navigation header record was
missing, although the example showed it. The redefinition of AODE/AODC to
IODE/IODC also asked for an update of the format description. For consistency
reasons we also defined a Version 2 format for the Meteorological Data files
(inclusion of a END OF HEADER record and an optional MARKER NUMBER record).
The slight modification (or rather the definition of a bit in the Loss of Lock
Indicator unused so far) to flag AS data is so small a change that we decided
to NOT increase the version number!
0.3 Later Revisions
* URA Clarification (10-Dec-93):
The user range accuracy in the Navigation Message File did not contain
a definition of the units: There existed two ways of interpretation:
Either the 4 bit value from the original message or the converted value
in meters according to GPS ICD-200. In order to simplify the interpretation
for the user of the RINEX files I propose the bits to be converted into
meters prior to RINEX file creation.
* GLONASS Extensions:
In March 1997 a proposal for extensions to the current RINEX definitions
based on experiences collected with GLONASS only and mixed GPS/GLONASS data
files was circulated among several instrument manufacturers and software
developers.
The results of the call for comments have been worked into this document.
A separate document (glonass.txt) summarizes just the necessary extensions.
* A blank satellite identifier is allowed in pure GPS files only
* Met sensor description and position records were added to facilitate the
precise use of met values.
* Description and examples for wavelength factors and their temporary changes
(bit 1 of LLI) clarified.
* The RINEX documentation distributed in spring 1997 contained definitions for
the GLONASS satellite clock offset and drift with the intention to have them
defined identically to the GPS values. Unfortunately the GLONASS Interface
Document consulted had a sign error in one of the formulae.
The values should be stored into the RINEX file as -TauN, +GammaN, -TauC.
The original definition asked for -TauN, -GammaN, +TauC. See paragraph 8.2.
To avoid problems with files created with the original definitions a real
valued version number (2.01) has been introduced for GLONASS nav mess files.
* IGS decided to use the Hatanaka compression scheme for RINEX observation
files. Below the corresponding RINEX file name conventions are included
as recommendations. The DOS naming (extension .yyE) was wrongly set to
.yyY in the March 1998 version of the document.
* GPS week: The GPS week number in all RINEX files is a continuous number
not affected by the 1024 roll-over, it runs from 1023 over 1024 to 1025 etc.
* A descrepancy between the definition of the header line fields of met sensor
description and position in Table A5 and the example in Table A9 was removed.
The latter was correct.
* Clarification for phase data format overflows: Add or subtract a suitable
number of cycles, set LLI flag.
* Clarification for the GLONASS satellite identifier: &Almanac number& was
somewhat ambiguous. It has been replaced by &slot number& within the
satellite constellation.
0.4 Version 2.10 Modifications
The modifications leading to Version 2.10 include:
- Fractional version number
- Zero padding of 2-digit year values (years
--& 00-09)
- Field length of time of first obs (1/10 microsecond resolution)
- Non-integer sampling rate (INTERVAL header record)
- Header records now allowed after all epoch flags &1
|
- Additional obs types in obs files: S1, S2 (raw signal strength values)
- Receiver clock offset header line to clarify applied corrections
- Default wavelength factor header line mandatory
- Inmarsat GPS payloads: New satellite system definition, new nav mess files
- Curve fit interval in GPS nav mess file
- Redefinition of SV health value in GPS nav mess file
- Additional obs types in met files (ZD, ZT)
0.5 Version 2.10 Revisions
* &Header records now allowed after all epoch flags &2& in paragraph 0.4
should read &&1&
* The original intention of the RINEX format was to allow for variable record
lengths of the ASCII files to minimize the file size. Empty fields or
unknown values can either be represented by zeroes or blank space. Most
RINEX converters removed trailing blank to further reduce the file size. The
documentation was not clear enough to explicitely allow for this practice
(paragraphs 2, 5.3, 9.1).
* The time system identifier of GPS observations generated by GEO payloads
defaults to GPS (explicitly stated now in paragraph 9.1)
* The time system identifier in the TIME OF LAST OBS header record has to
be identical to the one in the TIME OF FIRST OBS record
* Clarification of Table A2 to be compatible with examples of Table A7:
For event flags without significant epoch the epoch fields can be left blank.
Table A6: Format for epoch contained obvious errors
1. THE PHILOSOPHY OF RINEX
The first proposal for the &Receiver Independent Exchange Format& RINEX has
been developed by the Astronomical Institute of the University of Berne for
the easy exchange of the GPS data to be collected during the large European
GPS campaign EUREF 89, which involved more than 60 GPS receivers of 4
different manufacturers. The governing aspect during the development was
the following fact:
Most geodetic processing software for GPS data use a well-defined set of
observables:
- the carrier-phase measurement at one or both carriers (actually being a
measurement on the beat frequency between the received carrier of the
satellite signal and a receiver-generated reference frequency).
- the pseudorange (code) measurement, equivalent to the difference of the
time of reception (expressed in the time frame of the receiver) and the
time of transmission (expressed in the time frame of the satellite) of a
distinct satellite signal.
- the observation time being the reading of the receiver clock at the
instant of validity of the carrier-phase and/or the code measurements.
Usually the software assumes that the observation time is valid for both
the phase AND the code measurements, AND for all satellites observed.
Consequently all these programs do not need most of the information that is
usually stored by the receivers:
They need phase, code, and time in the
above mentioned definitions, and some station-related information like
station name, antenna height, etc.
2. GENERAL FORMAT DESCRIPTION
Currently the format consists of six ASCII file types:
1. Observation Data File
2. Navigation Message File
3. Meteorological Data File
4. GLONASS Navigation Message File
5. GEO Navigation Message File
6. Satellite and Receiver Clock Date File
(The format definition of the clock files has been published in 1998
in a separate document by Jim Ray and Werner Gurtner, available at the IGS
Central Bureau Information System: ftp://igscb.jpl.nasa.gov/igscb/data/
format/rinex_clock.txt).
Each file type consists of a header section and a data section. The header
section contains global information for the entire file and is placed at
the beginning of the file. The header section contains header labels in
columns 61-80 for each line contained in the header section. These labels
are mandatory and must appear exactly as given in these descriptions and
examples.
The format has been optimized for mimimum space requirements independent
from the number of different observation types of a specific receiver by
indicating in the header the types of observations to be stored. In
computer systems allowing variable record lengths the observation records
may be kept as short as possible. Trailing blanks can be removed from the
|
records. The maximum record length is 80 bytes per record.
Each Observation file and each Meteorological Data file basically contain
the data from one site and one session. RINEX Version 2 also allows to
include observation data from more than one site subsequently occupied by
a roving receiver in rapid static or kinematic applications. Although Version 2
allows to insert header records into the data field we do not recommend to
concatenate data of more than one receiver (or antenna) into the same file,
even if the data do not overlap in time.
If data from more than one receiver has to be exchanged it would not be
economical to include the identical satellite messages collected by the
different receivers several times. Therefore the Navigation Message File
from one receiver may be exchanged or a composite Navigation Message File
created containing non-redundant information from several receivers in
order to make the most complete file.
The format of the data records of the RINEX Version 1 Navigation Message
file is identical to the former NGS exchange format.
The actual format descriptions as well as examples are given in the Tables
at the end of the paper.
3. DEFINITION OF THE OBSERVABLES
GPS observables include three fundamental quantities that need to be defined:
Time, Phase, and Range.
The time of the measurement is the receiver time of the received signals.
It is identical for the phase and range measurements and is identical for
all satellites observed at that epoch. It is expressed in GPS time (not
Universal Time).
PSEUDO-RANGE:
The pseudo-range (PR) is the distance from the receiver antenna to the
satellite antenna including receiver and satellite clock offsets (and
other biases, such as atmospheric delays):
distance +
c * (receiver clock offset - satellite clock offset +
other biases)
so that the pseudo-range reflects the actual behavior of the receiver
and satellite clocks. The pseudo-range is stored in units of meters.
See also clarifications for pseudoranges in mixed GPS/GLONASS files in
chapter 8.1.
The phase is the carrier-phase measured in whole cycles at both L1 and
L2. The half-cycles measured by sqaring-type receivers must be converted
to whole cycles and flagged by the wavelength factor in the header
The phase changes in the same sense as the range (negative doppler). The
phase observations between epochs must be connected by including the
integer number of cycles. The phase observations will not contain any
systematic drifts from intentional offsets of the reference oscillators.
The observables are not corrected for external effects like atmospheric
refraction, satellite clock offsets, etc.
If the receiver or the converter software adjusts the measurements using
the real-time-derived receiver clock offsets dT(r), the consistency of the
3 quantities phase / pseudo-range / epoch must be maintained, i.e. the
receiver clock correction should be applied to all 3 observables:
Time(corr)
phase(corr) = phase(r) -
dT(r)*freq
The sign of the doppler shift as additional observable is defined as usual:
Positive for approaching satellites.
4. THE EXCHANGE OF RINEX FILES:
We recommend using the following naming convention for RINEX files:
ssssdddf.yyt
4-character station name designator
day of the year of first record
file sequence number within day
0: file contains all the existing
data of the current day
file type:
O: Observation file
N: Navigation file
M: Meteorological data file
G: GLONASS Navigation file
H: Geostationary GPS payload nav mess file
When data transmission times or storage volumes are critical we recommend
compressing the files prior to storage or transmission using the UNIX
&compress& und &uncompress& programs. Compatible routines are available on
VAX/VMS and PC/DOS systems, as well.
Proposed naming conventions for the compressed files:
File Types
ssssdddf.yyO.Z
ssssdddf.yyO_Z
ssssdddf.yyY
Obs Files (Hatanaka compr)
ssssdddf.yyD.Z
ssssdddf.yyD_Z
ssssdddf.yyE
GPS Nav Files
ssssdddf.yyN.Z
ssssdddf.yyN_Z
ssssdddf.yyX
GLONASS Nav File
ssssdddf.yyG.Z
ssssdddf.yyG_Z
ssssdddf.yyV
GEO Nav Files
ssssdddf.yyH.Z
ssssdddf.yyH_Z
ssssdddf.yyU
Met Data Files
ssssdddf.yyM.Z
ssssdddf.yyM_Z
ssssdddf.yyW
Clock Files (see sep.doc.)
ssssdddf.yyC.Z
ssssdddf.yyC_Z
References for the Hatanaka compression scheme: See e.g.
http://sopac.ucsd.edu/dataArchive/hatanaka.html
IGSMails 26,
5. RINEX VERSION 2 FEATURES
The following section contains features that have been introduced for RINEX
Version 2:
5.1 Satellite Numbers:
Version 2 has been prepared to contain GLONASS or other satellite systems'
observations. Therefore we have to be able to distinguish the satellites
of the different systems:
We precede the 2-digit satellite number with a
system identifier.
satellite system identifier
G or blank : GPS
: Geostationary signal payload
- PRN (GPS), slot number (GLONASS)
- PRN-100 (GEO)
- two-digit Transit satellite number
Note: G is mandatory in mixed GPS/GLONASS files
(blank default modified in April 1997)
5.2 Order of the Header Records:
As the record descriptors in columns 61-80 are mandatory, the programs
reading a RINEX Version 2 header are able to decode the header records with
formats according to the record descriptor, provided the records have been
first read into an internal buffer.
We therefore propose to allow free ordering of the header records, with the
following exceptions:
- The &RINEX VERSION / TYPE& record must be the first record in a file
- The default &WAVELENGTH FACT L1/2& record must precede all records defining
wavelength factors for individual satellites
- The &# OF SATELLITES& record (if present) should be immediately followed
by the corresponding number of &PRN / # OF OBS& records. (These records
may be handy for documentary purposes. However, since they may only be
created after having read the whole raw data file we define them to be
5.3 Missing Items, Duration of the Validity of Values
Items that are not known at the file creation time can be set to zero or
blank or the respective record may be completely omitted. Consequently
items of missing header records will be set to zero or blank by the program
reading RINEX files. Trailing blanks may be truncated from the record.
Each value remains valid until changed by an additional header record.
5.4 Event Flag Records
The &number of satellites& also corresponds to the number of records of the
same epoch followed. Therefore it may be used to skip the appropriate
number of records if certain event flags are not to be evaluated in detail.
5.5 Receiver Clock Offset
A large number of users asked to optionally include a receiver-derived
clock offset into the RINEX format. In order to remove uncertainties if
the data (epoch, pseudorange, phase) have been previously corrected or not
by the reported clock offset, RINEX Version 2.10 requests a clarifying (new)
header record.
It would then be possible to reconstruct the original observations if
necessary.
As the output format for the receiver-derived clock offset is limited to
nanoseconds the offset should be rounded to the nearest nanosecond before it
is used to correct the observables in order to guarantee correct
reconstruction.
6. ADDITIONAL HINTS AND TIPS
6.1 Version 1 / Version 2
Programs developed to read RINEX Version 1 files have to verify the version
number. Version 2 files may look different (version number, END OF HEADER
record, receiver and antenna serial number alphanumeric) even if they do
not use any of the new features
6.2 Leading Blanks in CHARACTER fields
We propose that routines to read RINEX Version 2 files automatically delete
leading blanks in any CHARACTER input field. Routines creating RINEX
Version 2 files should also left-justify all variables in the CHARACTER
fields.
6.3 Variable-length Records
DOS, and other, files may have variable record lengths, so we recommend to
first read each observation record into a 80-character blank string and
decode the data afterwards. In variable length records, empty data fields
at the end of a record may be missing, especially in the case of the
optional receiver clock offset.
6.4 Blank Fields
In view of future modifications we recommend to carefully skip any fields
currently defined to be blank (Format fields nX), because they may be assigned
to new contents in future versions.
6.5 2-Digit Years
RINEX version 2 stores the years of data records with two digits only. The
header of observation files contains a TIME OF FIRST OBS record with the full
four-digit year, the GPS nav messages contain the GPS week numbers. From these
two data items the unambiguous year can easily be reconstructed.
A hundred-year ambiguity occurs in the met data and GLONASS and GEO nav
messages: Instead of introducing a new TIME OF FIRST OBS header line it is
safeto stipulate that any two-digit years in RINEX Version 1 and Version 2.xx
files are understood to represent
Full 4-digit year fields could then be defined by a future RINEX version 3.
6.6 Fit Interval
Bit 17 in word 10 of subframe 2 is a &fit interval& flag which indicates the
curve-fit interval used by the GPS Control Segment in determining the
ephemeris parameters, as follows (see ICD-GPS-200, 20.3.3.4.3.1):
0 = 4 hours
1 = greater than 4 hours.
Together with the IODC values and Table 20-XII the actual fit interval can be
determined. The second value in the last record of each message shall contain
the fit interval in hours determined using IODC, fit flag, and Table 20-XII,
according to the Interface Document ICD-GPS-200.
6.7 Satellite Health
The health of the signal components (bits 18 to 22 of word three in subframe
one) are now (Version 2.10) included into the health value reported in the
second field of the sixth nav mess records.
A program reading RINEX files could easily decide if bit 17 only or all bits
(17-22) have been written:
RINEX Value:
Health OK
RINEX Value:
Health not OK (bits 18-22 not stored)
RINEX Value: &32
Health not OK (bits 18-22 stored)
6.8 Transmission Time of Message (Navigation message file)
The transmission time of message can be shortly before midnight
Saturday/Sunday, the TOE and TOC of the message already in the next week.
As the reported week in the RINEX nav message (BROADCAST ORBIT - 5 record)
goes with ToE (this is different from the GPS week in the original satellite
message!), the transmission time of message should be reduced by 604800
(i.e., will become negative) to also refer to the same week.
7. RINEX UNDER ANTISPOOFING (AS)
Some receivers generate code delay differences between the first and second
frequency using cross-correlation techniques when AS is on and may recover
the phase observations on L2 in full cycles. Using the C/A code delay on
L1 and the observed difference it is possible to generate a code delay
observation for the second frequency.
Other receivers recover P code observations by breaking down the Y code
into P and W code.
Most of these observations may suffer from an increased noise level. In
order to enable the postprocessing programs to take special actions, such
AS-infected observations are flagged using bit number 2 of the Loss of Lock
Indicators (i.e. their current values are increased by 4).
8. GLONASS Extensions
8.1 RINEX Observation File
8.1.1 Time System Identifier
The original RINEX Version 2 needed one major supplement, the explicit
definition of the time system:
GLONASS is basically running on UTC (or, more precisely, GLONASS system time
linked to UTC(SU)), i.e. the time tags are given in UTC and not GPS time.
In order to remove possible misunderstandings and ambiguities, the header
records &TIME OF FIRST OBS& and (if present) &TIME OF LAST OBS& in GLONASS and
GPS observation files _can_, in mixed GLONASS/GPS observation files _must_
contain a time system identifier defining the system that all time tags in the
file are referring to: &GPS& to identify GPS time, &GLO& to identify the
GLONASS UTC time system. Pure GPS files default to GPS and pure GLONASS files
default to GLO.
Format definitions see Table A1.
Hence, the two possible time tags differ by the current number of leap seconds.
In order to have the current number of leap seconds available we recommend
to include a LEAP SECOND line into the RINEX header.
If there are known non-integer biases between the &GPS receiver clock&
and &GLONASS receiver clock& in the same receiver, they should be applied.
In this case the respective code and phase observations have to be corrected,
too (c * bias if expressed in meters).
Unknown such biases will have to be solved for during the post processing
The small differences (modulo 1 second) between GLONASS system time, UTC(SU),
UTC(USNO) and GPS system time have to be dealt with during the post-processing
and not before the RINEX conversion. It may also be necessary to solve for
remaining differences during the post-processing.
8.1.2 Pseudorange Definition
The pseudorange (code) measurement is defined to be equivalent to the
difference of the time of reception (expressed in the time frame of the
receiver) and the time of transmission (expressed in the time frame of the
satellite) of a distinct satellite signal.
If a mixed-mode GPS/GLONASS receiver refers all pseudorange observations to
one receiver clock only,
- the raw GLONASS pseudoranges will show the current number of leap seconds
between GPS time and GLONASS time if the receiver clock is running in the
GPS time frame
- the raw GPS pseudoranges will show the negative number of leap seconds
between GPS time and GLONASS time if the receiver clock is running in the
GLONASS time frame
In order to avoid misunderstandings and to keep the code observations within
the format fields, the pseudoranges must be corrected in this case as follows:
PR(GPS) := PR(GPS) + c * leap_seconds
if generated with a receiver clock
running in the GLONASS time frame
PR(GLO) := PR(GLO) - c * leap_seconds
if generated with a receiver clock
running in the GPS time frame
to remove the contributions of the leap seconds from the pseudoranges.
&leap_seconds& is the actual number of leap seconds between GPS and GLONASS
(UTC) time, as broadcast in the GPS almanac and distributed in Circular T
of BIPM.
8.1.3 More Than 12 Satellites per Epoch
The format of the epoch / satellite line in the observation record part of
the RINEX Observation files has only been defined for up to 12 satellites
per epoch. We explicitly define now the format of the continuation lines,
see Table A2.
8.2 RINEX Navigation Files for GLONASS
As the GLONASS navigation message differs in contents from the GPS message
too much, a special GLONASS navigation message file format has been defined.
The header section and the first data record (epoch, satellite clock
information) is similar to the GPS navigation file. The following records
contain the satellite position, velocity and acceleration, the clock and
frequency biases as well as auxiliary information as health, satellite
frequency (channel), age of the information.
The corrections of the satellite time to UTC are as follows:
: Tutc = Tsv - af0
*(Tsv-Toc) - ... -
- ... - leap_sec
GLONASS: Tutc = Tsv + TauN - GammaN*(Tsv-Tb)
In order to use the same sign conventions for the GLONASS corrections
as in the GPS navigation files,
the broadcast GLONASS values are
stored as:
-TauN, +GammaN, -TauC.
The time tags in the GLONASS navigation files are given in UTC (i.e. _not_
Moscow time or GPS time).
Filenaming convention: See above.
RINEX Extensions for Geostationary Satellites (GPS Signal Payloads)
With the implementation of GNSS programs, GPS-like ranging measurements can be
performed on geostationary navigation payloads.
RINEX Version 2.10 defines the necessary extensions to handle such data in
RINEX files for data exchange and postprocessing purposes.
9.1 RINEX Observation Files for GEO Satellites
A new satellite system identifier has been defined for the geostationary
GPS signal payloads: &S&, to be used in the RINEX VERSION / TYPE header line
and in the satellite identifier 'snn', nn being the GEO PRN number minus 100.
e.g.: PRN = 120 --& 'snn' = &S20&
In mixed dual frequency GPS satellite / single frequency GEO payload
observation files the fields for the second frequency observations of GEO
satellites remain blank, are set to zero values or (if last in the record)
|
can be truncated.
The time system identifier of GEO satellites generating GPS signals defaults
|
to GPS time.
9.2 RINEX Navigation Message Files for GEO Satellites
As the GEO broadcast orbit format differs from the GPS message a special GEO
navigation message file format has been defined which is nearly identical with
the GLONASS nav mess file format.
The header section contains informations about the generating program,
comments, and the difference between the GEO system time and UTC.
The first data record contains the epoch and satellite clock information,
the following records contain the satellite position, velocity and
acceleration and auxiliary information such as health, age of the data, etc.
The time tags in the GEO navigation files are given in the GPS time frame,
i.e. not UTC.
The corrections of the satellite time to UTC are as follows:
: Tutc = Tsv - aGf0
aGf1 *(Tsv-Toe) -
- leap_sec
W0 being the correction to transform the GEO system time to UTC. Toe, aGf0,
aGf1 see below in the format definition tables.
References for the definition of the accuracy and health codes still have *
*
to be defined.
Help is needed here by colleagues working with such GEO data!
10. REFERENCES
Evans, A. (1989): &Summary of the Workshop on GPS Exchange Formats.&
Proceedings of the Fifth International Geodetic Symposium on Satellite
Systems, pp. 917ff, Las Cruces.
Gurtner, W., G. Mader, D. Arthur (1989):
&A Common Exchange Format for
GPS Data.& CSTG GPS Bulletin Vol.2 No.3, May/June 1989, National Geodetic
Survey, Rockville.
Gurtner, W., G. Mader (1990): &The RINEX Format: Current Status, Future
Developments.& Proceedings of the Second International Symposium of Precise
Positioning with the Global Positioning system, pp. 977ff, Ottawa.
Gurtner, W., G. Mader (1990):
&Receiver Independent Exchange Format
Version 2.& CSTG GPS Bulletin Vol.3 No.3, Sept/Oct 1990, National Geodetic
Survey, Rockville.
Gurtner, W. (1994): &RINEX: The Receiver-Independent Exchange Format.&
GPS World, Volume 5, Number 7, July 1994.
11. RINEX VERSION 2.10 FORMAT DEFINITIONS AND EXAMPLES
+----------------------------------------------------------------------------+
GPS OBSERVATION DATA FILE - HEADER SECTION DESCRIPTION
+--------------------+------------------------------------------+------------+
HEADER LABEL
DESCRIPTION
(Columns 61-80)
+--------------------+------------------------------------------+------------+
|RINEX VERSION / TYPE| - Format version (2.10)
| F9.2,11X,
| - File type ('O' for Observation Data)
| - Satellite System: blank or 'G': GPS
'R': GLONASS
'S': Geostationary
signal payload
'T': NNSS Transit
'M': Mixed
+--------------------+------------------------------------------+------------+
|PGM / RUN BY / DATE | - Name of program creating current file
| - Name of agency
creating current file
| - Date of file creation
+--------------------+------------------------------------------+------------+
*|COMMENT
| Comment line(s)
+--------------------+------------------------------------------+------------+
|MARKER NAME
| Name of antenna marker
+--------------------+------------------------------------------+------------+
*|MARKER NUMBER
| Number of antenna marker
+--------------------+------------------------------------------+------------+
|OBSERVER / AGENCY
| Name of observer / agency
+--------------------+------------------------------------------+------------+
|REC # / TYPE / VERS | Receiver number, type, and version
| (Version: e.g. Internal Software Version)|
+--------------------+------------------------------------------+------------+
|ANT # / TYPE
| Antenna number and type
+--------------------+------------------------------------------+------------+
|APPROX POSITION XYZ | Approximate marker position (WGS84)
+--------------------+------------------------------------------+------------+
|ANTENNA: DELTA H/E/N| - Antenna height: Height of bottom
surface of antenna above marker
| - Eccentricities of antenna center
relative to marker to the east
and north (all units in meters)
+--------------------+------------------------------------------+------------+
|WAVELENGTH FACT L1/2| - Default wavelength factors for
Full cycle ambiguities
Half cycle ambiguities (squaring)
0 (in L2): Single frequency instrument |
| - zero or blank
| The default wavelength factor line is
| required and must preceed satellite-
| specific lines.
+--------------------+------------------------------------------+------------+
*|WAVELENGTH FACT L1/2| - Wavelength factors for L1 and L2
Full cycle ambiguities
Half cycle ambiguities (squaring)
0 (in L2): Single frequency instrument |
| - Number of satellites to follow in list |
for which these factors are valid.
| - List of PRNs (satellite numbers with
| 7(3X,A1,I2)|
system identifier)
| These opional satellite specific lines
| may follow, if they identify a state
| different from the default values.
| Repeat record if necessary.
+--------------------+------------------------------------------+------------+
|# / TYPES OF OBSERV | - Number of different observation types
stored in the file
| - Observation types
If more than 9 observation types:
Use continuation line(s)
|6X,9(4X,A2) |
| The following observation types are
| defined in RINEX Version 2.10:
| L1, L2: Phase measurements on L1 and L2
: Pseudorange using C/A-Code on L1 |
| P1, P2: Pseudorange using P-Code on L1,L2|
| D1, D2: Doppler frequency on L1 and L2
| T1, T2: Transit Integrated Doppler on
150 (T1) and 400 MHz (T2)
| S1, S2: Raw signal strengths or SNR
values as given by the receiver
for the L1,L2 phase observations |
| Observations collected under Antispoofing|
| are converted to &L2& or &P2& and flagged|
| with bit 2 of loss of lock indicator
| (see Table A2).
| Units : Phase
: full cycles
Pseudorange : meters
: receiver-dependent |
| The sequence of the types in this record |
| has to correspond to the sequence of the |
| observations in the observation records
+--------------------+------------------------------------------+------------+
*|INTERVAL
| Observation interval in seconds
+--------------------+------------------------------------------+------------+
|TIME OF FIRST OBS
| - Time of first observation record
| 5I6,F13.7, |
(4-digit-year, month,day,hour,min,sec) |
| - Time system: GPS (=GPS time system)
GLO (=UTC time system)
Compulsory in mixed GPS/GLONASS files
Defaults: GPS for pure GPS files
GLO for pure GLONASS files
+--------------------+------------------------------------------+------------+
*|TIME OF LAST OBS
| - Time of last
observation record
| 5I6,F13.7, |*
(4-digit-year, month,day,hour,min,sec) |
| - Time system: Same value as in
TIME OF FIRST OBS record
+--------------------+------------------------------------------+------------+
*|RCV CLOCK OFFS APPL | Epoch, code, and phase are corrected by
| applying the realtime-derived receiver
| clock offset: 1=yes, 0= default: 0=no |
| Record required if clock offsets are
| reported in the EPOCH/SAT records
+--------------------+------------------------------------------+------------+
*|LEAP SECONDS
| Number of leap seconds since 6-Jan-1980
| Recommended for mixed GPS/GLONASS files
+--------------------+------------------------------------------+------------+
*|# OF SATELLITES
| Number of satellites, for which
| observations are stored in the file
+--------------------+------------------------------------------+------------+
*|PRN / # OF OBS
| PRN (sat.number), number of observations |3X,A1,I2,9I6|*
| for each observation type indicated
| in the &# / TYPES OF OBSERV& - record.
If more than 9 observation types:
Use continuation line(s)
| This record is (these records are)
| repeated for each satellite present in
| the data file
+--------------------+------------------------------------------+------------+
|END OF HEADER
| Last record in the header section.
+--------------------+------------------------------------------+------------+
Records marked with * are optional
+----------------------------------------------------------------------------+
GPS OBSERVATION DATA FILE - DATA RECORD DESCRIPTION
+-------------+-------------------------------------------------+------------+
| OBS. RECORD | DESCRIPTION
+-------------+-------------------------------------------------+------------+
| EPOCH/SAT
| - Epoch :
- year (2 digits, padded with 0 if necessary) |
| EVENT FLAG
- month,day,hour,min,
4(1X,I2), |
| - Epoch flag 0: OK
1: power failure between
previous and current epoch
&1: Event flag
| - Number of satellites in current epoch
| - List of PRNs (sat.numbers with system
| 12(A1,I2), |
identifier, see 5.1) in current epoch
| - receiver clock offset (seconds, optional)
If more than 12 satellites: Use continuation
| 12(A1,I2)
| If epoch flag
- Event flag:
2: start moving antenna
3: new site occupation (end of kinem. data) |
(at least MARKER NAME record follows)
4: header information follows
5: external event (epoch is significant,
same time frame as observation time tags)|
- &Number of satellites& contains number of
special records to follow.
Maximum number of records: 999
- For events without significant epoch the
epoch fields can be left blank
| If epoch flag = 6:
6: cycle slip records follow to optionally
report detected and repaired cycle slips |
(same format as OBSERVATIONS
slip in LLI and
signal strength blank or zero)
+-------------+-------------------------------------------------+------------+
|OBSERVATIONS | - Observation
| rep. within record for
| each obs.type (same seq
| - Signal strength
| as given in header)
| If more than 5 observation types (=80 char):
| continue observations in next record.
| This record is (these records are) repeated for |
| each satellite given in EPOCH/SAT - record.
| Observations:
: Units in whole cycles of carrier
: Units in meters
| Missing observations are written as 0.0
| or blanks.
| Phase values overflowing the fixed format F14.3 |
| have to be clipped into the valid interval (e.g.|
| add or subtract 10**9), set LLI indicator.
| Loss of lock indicator (LLI). Range: 0-7
0 or blank: OK or not known
Bit 0 set : Lost lock between previous and
current observation: cycle slip
Bit 1 set : Opposite wavelength factor to the
one defined for the satellite by a |
previous WAVELENGTH FACT L1/2 line.|
Valid for the current epoch only.
Bit 2 set : Observation under Antispoofing
(may suffer from increased noise)
Bits 0 and 1 for phase only.
| Signal strength projected into interval 1-9:
1: minimum possible signal strength
5: threshold for good S/N ratio
9: maximum possible signal strength
0 or blank: not known, don't care
+-------------+-------------------------------------------------+------------+
+----------------------------------------------------------------------------+
GPS NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
+--------------------+------------------------------------------+------------+
HEADER LABEL
DESCRIPTION
(Columns 61-80)
+--------------------+------------------------------------------+------------+
|RINEX VERSION / TYPE| - Format version (2.10)
| F9.2,11X,
| - File type ('N' for Navigation data)
+--------------------+------------------------------------------+------------+
|PGM / RUN BY / DATE | - Name of program creating current file
| - Name of agency
creating current file
| - Date of file creation
+--------------------+------------------------------------------+------------+
*|COMMENT
| Comment line(s)
+--------------------+------------------------------------------+------------+
*|ION ALPHA
| Ionosphere parameters A0-A3 of almanac
2X,4D12.4 |*
| (page 18 of subframe 4)
+--------------------+------------------------------------------+------------+
*|ION BETA
| Ionosphere parameters B0-B3 of almanac
2X,4D12.4 |*
+--------------------+------------------------------------------+------------+
*|DELTA-UTC: A0,A1,T,W| Almanac parameters to compute time in UTC| 3X,2D19.12,|*
| (page 18 of subframe 4)
| A0,A1: terms of polynomial
: reference time for UTC data
: UTC reference week number.
Continuous number, not mod(1024)! |
+--------------------+------------------------------------------+------------+
*|LEAP SECONDS
| Delta time due to leap seconds
+--------------------+------------------------------------------+------------+
|END OF HEADER
| Last record in the header section.
+--------------------+------------------------------------------+------------+
Records marked with * are optional
+----------------------------------------------------------------------------+
GPS NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
+--------------------+------------------------------------------+------------+
OBS. RECORD
| DESCRIPTION
+--------------------+------------------------------------------+------------+
|PRN / EPOCH / SV CLK| - Satellite PRN number
| - Epoch: Toc - Time of Clock
year (2 digits, padded with 0
if necessary)
| - SV clock bias
| - SV clock drift
| - SV clock drift rate (sec/sec2)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 1| - IODE Issue of Data, Ephemeris
| 3X,4D19.12 |
| - Delta n
(radians/sec)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 2| - Cuc
| 3X,4D19.12 |
| - e Eccentricity
| - sqrt(A)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 3| - Toe Time of Ephemeris
| 3X,4D19.12 |
(sec of GPS week)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 4| - i0
| 3X,4D19.12 |
| - OMEGA DOT
(radians/sec)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 5| - IDOT
(radians/sec)
| 3X,4D19.12 |
| - Codes on L2 channel
| - GPS Week # (to go with TOE)
Continuous number, not mod(1024)!
| - L2 P data flag
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 6| - SV accuracy
| 3X,4D19.12 |
| - SV health
(bits 17-22 w 3 sf 1) |
| - IODC Issue of Data, Clock
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 7| - Transmission time of message
*) | 3X,4D19.12 |
(sec of GPS week, derived e.g.
from Z-count in Hand Over Word (HOW)
| - Fit interval
(see ICD-GPS-200, 20.3.4.4)
Zero if not known
+--------------------+------------------------------------------+------------+
*) Adjust the Transmission time of message by -604800 to refer to the reported
week, if necessary
+----------------------------------------------------------------------------+
METEOROLOCICAL DATA FILE - HEADER SECTION DESCRIPTION
+--------------------+------------------------------------------+------------+
HEADER LABEL
DESCRIPTION
(Columns 61-80)
+--------------------+------------------------------------------+------------+
|RINEX VERSION / TYPE| - Format version (2.10)
| F9.2,11X,
| - File type ('M' for Meteorological Data)|
+--------------------+------------------------------------------+------------+
|PGM / RUN BY / DATE | - Name of program creating current file
| - Name of agency
creating current file
| - Date of file creation
+--------------------+------------------------------------------+------------+
*|COMMENT
| Comment line(s)
+--------------------+------------------------------------------+------------+
|MARKER NAME
| Station Name
| (preferably identical to MARKER NAME in
the associated Observation File)
+--------------------+------------------------------------------+------------+
*|MARKER NUMBER
| Station Number
| (preferably identical to MARKER NUMBER in|
the associated Observation File)
+--------------------+------------------------------------------+------------+
|# / TYPES OF OBSERV | - Number of different observation types
stored in the file
| - Observation types
| The following meteorological observation |
| types are defined in RINEX Version 2:
| PR : Pressure (mbar)
| TD : Dry temperature (deg Celsius)
| HR : Relative Humidity (percent)
| ZW : Wet zenith path delay (millimeters) |
(for WVR data)
| ZD : Dry component of zenith path delay
(millimeters)
| ZT : Total zenith path delay
(millimeters)
| The sequence of the types in this record |
| must correspond to the sequence of the
| measurements in the data records
| If more than 9 observation types are
| being used, use continuation lines with
| format (6X,9(4X,A2))
+--------------------+------------------------------------------+------------+
|SENSOR MOD/TYPE/ACC | Description of the met sensor
| - Model (manufacturer)
| - Accuracy (same units as obs values)
F7.1,4X, |
| - Observation type
| Record is repeated for each observation
| type found in # / TYPES OF OBSERV record |
+--------------------+------------------------------------------+------------+
|SENSOR POS XYZ/H
| Approximate position of the met sensor
| - Geocentric coordinates X,Y,Z
| - Ellipsoidal height H
or WGS-84)|
| - Observation type
| Set X,Y,Z to zero if not known.
| Make sure H refers to ITRF or WGS-84!
| Record required for barometer,
| recommended for other sensors.
+--------------------+------------------------------------------+------------+
|END OF HEADER
| Last record in the header section.
+--------------------+------------------------------------------+------------+
Records marked with * are optional
+----------------------------------------------------------------------------+
METEOROLOGICAL DATA FILE - DATA RECORD DESCRIPTION
+-------------+-------------------------------------------------+------------+
| OBS. RECORD | DESCRIPTION
+-------------+-------------------------------------------------+------------+
| EPOCH / MET | - Epoch in GPS time (not local time!)
year (2 digits, padded with 0 if necessary) |
month,day,hour,min,sec
| 5( 1X,I2), |
The 2-digit years in RINEX Version 1 and 2.xx |
files are understood to represent
| - Met data in the same sequence as given in the |
| More than 8 met data types: Use continuation
|4X,10F7.1,3X|
+-------------+-------------------------------------------------+------------+
+------------------------------------------------------------------------------+
|
GPS OBSERVATION DATA FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
OBSERVATION DATA
RINEX VERSION / TYPE
BLANK OR G = GPS,
R = GLONASS,
T = TRANSIT,
COMMENT
XXRINEXO V9.9
24-MAR-01 14:43
PGM / RUN BY / DATE
EXAMPLE OF A MIXED RINEX FILE
COMMENT
A 9080
MARKER NAME
MARKER NUMBER
BILL SMITH
ABC INSTITUTE
OBSERVER / AGENCY
X
REC # / TYPE / VERS
234
ANT # / TYPE
APPROX POSITION XYZ
ANTENNA: DELTA H/E/N
WAVELENGTH FACT L1/2
WAVELENGTH FACT L1/2
RCV CLOCK OFFS APPL
# / TYPES OF OBSERV
36.0000000
TIME OF FIRST OBS
END OF HEADER
3 24 13 10 36.
3G12G 9G 6
3 24 13 10 50.
WAVELENGTH FACT L1/2
*** WAVELENGTH FACTOR CHANGED FOR 2 SATELLITES ***
NOW 8 SATELLITES HAVE WL FACT 1 AND 2!
3 24 13 10 54.
5G12G 9G 6R21R22
3 24 13 11
*** FROM NOW ON KINEMATIC DATA! ***
3 24 13 11 48.
4G16G12G 9G 6
MARKER NAME
MARKER NUMBER
ANTENNA: DELTA H/E/N
--& THIS IS THE START OF A NEW SITE &--
3 24 13 12
4G16G12G 6G 9
3 24 13 13
(AN EVENT FLAG WITH SIGNIFICANT EPOCH)
3 24 13 14 12.
4G16G12G 9G 6
*** ANTISPOOFING ON G 16 AND LOST LOCK
3 24 13 14 12.
---& CYCLE SLIPS THAT HAVE BEEN APPLIED TO
THE OBSERVATIONS
3 24 13 14 48.
4G16G12G 9G 6
SATELLITE G 9
THIS EPOCH ON WLFACT 1 (L2)
*** G 6 LOST LOCK AND THIS EPOCH ON WLFACT 2 (L2)
(OPPOSITE TO PREVIOUS SETTINGS)
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+------------------------------------------------------------------------------+
|
GPS NAVIGATION MESSAGE FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
N: GPS NAV DATA
RINEX VERSION / TYPE
XXRINEXN V2.10
3-SEP-99 15:22
PGM / RUN BY / DATE
EXAMPLE OF VERSION 2.10 FORMAT
-.1192D-06
-.1192D-06
-.1310D+06
-.1966D+06
1025 DELTA-UTC: A0,A1,T,W
LEAP SECONDS
END OF HEADER
2 17 51 44.0 -.D-03 -.D-10
.D+06 -.D-07
.D+00 -.D-07
.D+01 -.D-08
.D+00
13 99
.D+03 -.D+02
.D+06 -.D-07
.D+01 -.D-07
.D+03 -.D+01 -.D-08
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+------------------------------------------------------------------------------+
|
METEOROLOGICAL DATA FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
METEOROLOGICAL DATA
RINEX VERSION / TYPE
XXRINEXM V9.9
3-APR-96 00:10
PGM / RUN BY / DATE
EXAMPLE OF A MET DATA FILE
COMMENT
A 9080
MARKER NAME
# / TYPES OF OBSERV
PAROSCIENTIFIC
PR SENSOR MOD/TYPE/ACC
HAENNI
TD SENSOR MOD/TYPE/ACC
ROTRONIC
HR SENSOR MOD/TYPE/ACC
PR SENSOR POS XYZ/H
END OF HEADER
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+----------------------------------------------------------------------------+
GLONASS NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
+--------------------+------------------------------------------+------------+
HEADER LABEL
DESCRIPTION
(Columns 61-80)
+--------------------+------------------------------------------+------------+
|RINEX VERSION / TYPE| - Format version (2.10)
| F9.2,11X,
| - File type ('G' = GLONASS nav mess data)|
+--------------------+------------------------------------------+------------+
|PGM / RUN BY / DATE | - Name of program creating current file
| - Name of agency
creating current file
| - Date of file creation (dd-mmm-yy hh:mm)|
+--------------------+------------------------------------------+------------+
*|COMMENT
| Comment line(s)
+--------------------+------------------------------------------+------------+
*|CORR TO SYSTEM TIME | - Time of reference for system time corr |
(year, month, day)
| - Correction to system time scale (sec)
3X,D19.12 |
to correct GLONASS system time to
+--------------------+------------------------------------------+------------+
*|LEAP SECONDS
| Number of leap seconds since 6-Jan-1980
+--------------------+------------------------------------------+------------+
|END OF HEADER
| Last record in the header section.
+--------------------+------------------------------------------+------------+
Records marked with * are optional
+----------------------------------------------------------------------------+
GLONASS NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
+--------------------+------------------------------------------+------------+
OBS. RECORD
| DESCRIPTION
+--------------------+------------------------------------------+------------+
|PRN / EPOCH / SV CLK| - Satellite number:
Slot number in sat. constellation
| - Epoch of ephemerides
- year (2 digits, padded with 0,
1X,I2.2, |
if necessary)
- month,day,hour,minute,
4(1X,I2), |
| - SV clock bias (sec)
| - SV relative frequency bias
(+GammaN)|
| - message frame time
(0 .le. tk .lt. 86400 sec of day UTC)
The 2-digit years in RINEX 1 and 2.xx
files are understood to represent
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 1| - Satellite position X
| 3X,4D19.12 |
velocity X dot
X acceleration
health (0=OK)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 2| - Satellite position Y
| 3X,4D19.12 |
velocity Y dot
Y acceleration
frequency number (1-24)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 3| - Satellite position Z
| 3X,4D19.12 |
velocity Z dot
Z acceleration
| - Age of oper. information
+--------------------+------------------------------------------+------------+
+------------------------------------------------------------------------------+
|
GLONASS NAVIGATION MESSAGE FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
GLONASS NAV DATA
RINEX VERSION / TYPE
ASRINEXG V1.1.0 VM
19-FEB-98 10:42
PGM / RUN BY / DATE
STATION ZIMMERWALD
CORR TO SYSTEM TIME
END OF HEADER
0.0 0.D-03 0.D-11 0.D+05
0.D+05-0.D+00 0.D-09 0.D+00
-0.D+04 0.D+01 0.D-09 0.D+02
0.D+05 0.D+01-0.D-08 0.D+01
0.0 0.D-03 0.D-11 0.D+05
0.D+04-0.D+00-0.D-09 0.D+00
-0.D+05 0.D+01 0.D-09 0.D+02
0.D+04 0.D+01 0.D+00 0.D+01
11 98
0.0-0.D-04-0.D-11 0.D+05
-0.D+04-0.D+01 0.D-09 0.D+00
0.D+05-0.D+01 0.D+00 0.D+01
0.D+05 0.D+00-0.D-08 0.D+01
12 98
0.0 0.D-04-0.D-11 0.D+05
0.D+05-0.D+01 0.D-08 0.D+00
0.D+05-0.D+01 0.D-09 0.D+02
0.D+05 0.D+01-0.D-09 0.D+01
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+------------------------------------------------------------------------------+
|
GLONASS OBSERVATION FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
OBSERVATION DATA
R (GLONASS)
RINEX VERSION / TYPE
XXRINEXO V1.1
27-AUG-93 07:23
PGM / RUN BY / DATE
TST1
MARKER NAME
VIEWEG
BRAUNSCHWEIG
OBSERVER / AGENCY
100
XX-RECEIVER
REC # / TYPE / VERS
101
XX-ANTENNA
ANT # / TYPE
APPROX POSITION XYZ
ANTENNA: DELTA H/E/N
WAVELENGTH FACT L1/2
# / TYPES OF OBSERV
40.0490000
TIME OF FIRST OBS
END OF HEADER
8 23 14 24 40.
8 23 14 24 50.
8 23 14 25
8 23 14 25 10.
2R05R17R01R21
8 23 14 25 20.
2R05R17R01R21
8 23 14 25 30.
2R05R17R01R21
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+------------------------------------------------------------------------------+
|
MIXED GPS/GLONASS OBSERVATION FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
OBSERVATION DATA
RINEX VERSION / TYPE
YYRINEXO V2.8.1 VM
6-FEB-00 13:59
PGM / RUN BY / DATE
TST2
MARKER NAME
001-02-A
MARKER NUMBER
JIM
OBSERVER / AGENCY
1
YY-RECEIVER
REC # / TYPE / VERS
1
GEODETIC L1
ANT # / TYPE
APPROX POSITION XYZ
ANTENNA: DELTA H/E/N
WAVELENGTH FACT L1/2
# / TYPES OF OBSERV
LEAP SECONDS
TIME OF FIRST OBS
END OF HEADER
0. 14G23G07G02G05G26G09G21R20R19R12R02R11
6 11 53 10. 14G23G07G02G05G26G09G21R20R19R12R02R11
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+----------------------------------------------------------------------------+
GEOSTATIONARY NAVIGATION MESSAGE FILE - HEADER SECTION DESCRIPTION
+--------------------+------------------------------------------+------------+
HEADER LABEL
DESCRIPTION
(Columns 61-80)
+--------------------+------------------------------------------+------------+
|RINEX VERSION / TYPE| - Format version (2.10)
| F9.2,11X,
| - File type ('H' = GEO nav mess data)
+--------------------+------------------------------------------+------------+
|PGM / RUN BY / DATE | - Name of program creating current file
| - Name of agency
creating current file
| - Date of file creation (dd-mmm-yy hh:mm)|
+--------------------+------------------------------------------+------------+
*|COMMENT
| Comment line(s)
+--------------------+------------------------------------------+------------+
*|CORR TO SYSTEM TIME | - Time of reference for system time corr |
(year, month, day)
| - Correction to transform the GEO system | 3X,D19.12
time to UTC
+--------------------+------------------------------------------+------------+
*|LEAP SECONDS
| Number of leap seconds since 6-Jan-1980
+--------------------+------------------------------------------+------------+
|END OF HEADER
| Last record in the header section.
+--------------------+------------------------------------------+------------+
Records marked with * are optional
+----------------------------------------------------------------------------+
GEOSTATIONARY NAVIGATION MESSAGE FILE - DATA RECORD DESCRIPTION
+--------------------+------------------------------------------+------------+
OBS. RECORD
| DESCRIPTION
+--------------------+------------------------------------------+------------+
|PRN / EPOCH / SV CLK| - Satellite number (PRN - 100)
| - Epoch of ephemerides (GPS)
- year (2 digits, padded with 0
if necessary)
1X,I2.2, |
- month,day,hour,minute,
4(1X,I2), |
| - SV clock bias (sec)
| - SV relative frequency bias
| - message frame time (sec of day GPS)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 1| - Satellite position X
| 3X,4D19.12 |
velocity X dot
X acceleration
health (0=OK)
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 2| - Satellite position Y
| 3X,4D19.12 |
velocity Y dot
Y acceleration
| - Accuracy code
(URA, meters)|
+--------------------+------------------------------------------+------------+
| BROADCAST ORBIT - 3| - Satellite position Z
| 3X,4D19.12 |
velocity Z dot
Z acceleration
+--------------------+------------------------------------------+------------+
+------------------------------------------------------------------------------+
|
MIXED GPS/GEO OBSERVATION FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
OBSERVATION DATA
RINEX VERSION / TYPE
RinExp V.2.0.2
00-02-04 09:30
PGM / RUN BY / DATE
COMMENT
The file contains L1 pseudorange and phase data of the
COMMENT
geostationary AOR-E satellite (PRN 120 = S20)
COMMENT
TLSE D
MARKER NAME
ESTB
TESTAGENCY
OBSERVER / AGENCY
SGL
Novatel Millennium
HW3-1 SW 4.45/2.3
REC # / TYPE / VERS
ANT # / TYPE
APPROX POSITION XYZ
ANTENNA: DELTA H/E/N
WAVELENGTH FACT L1/2
# / TYPES OF OBSERV
TIME OF FIRST OBS
TIME OF LAST OBS
RCV CLOCK OFFS APPL
END OF HEADER
00 01 13 14 45
8G25G17G06G05G24G29G30S20
00 01 13 14 45
8G25G17G06G05G24G29G30S20
00 01 13 14 45
8G25G17G06G05G24G29G30S20
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
+------------------------------------------------------------------------------+
|
GEO NAVIGATION MESSAGE FILE - EXAMPLE
|
+------------------------------------------------------------------------------+
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
H: GEO NAV MSG DATA
RINEX VERSION / TYPE
SuP v. 1.4
04-02-00 10:04
PGM / RUN BY / DATE
COMMENT
The file contains navigation message data of the
COMMENT
geostationary AOR-E satellite (PRN 120 = S20)
END OF HEADER
20 00 01 13 14 46 24.0
.D-07 -.D-11
.D+01 -.D-03
.D+01 -.D-03
.D+00
20 00 01 13 14 48 00.0
.D-07 -.D-11
.D+01 -.D-03
.D+01 -.D-03
.D+00
20 00 01 13 14 49 36.0
.D-07 -.D-11
.D+01 -.D-03
.D+01 -.D-03
.D+00
20 00 01 13 14 51 12.0
.D-07 -.D-11
.D+01 -.D-03
.D+01 -.D-03
----|---1|0---|---2|0---|---3|0---|---4|0---|---5|0---|---6|0---|---7|0---|---8|
If you have any comments or suggestions, feel free to e-mail us.
更多相关文档