📄 rinex格式.htm
字号:
src="RINEX格式.files/sendmessage.gif"
border=0></A> <A title="把 测绘人加为好友"
href="http://www.othermap.com/bbs/AddFriend.asp?friend=测绘人"><IMG
src="RINEX格式.files/friend.gif" border=0></A> <A
title=已设置保密
href="http://www.othermap.com/bbs/article.asp?titleid=4547&ntypeid=22#"><IMG
src="RINEX格式.files/email.gif" border=0></A> <A
title=直接回复本主题
href="http://www.othermap.com/bbs/ft.asp?reply=2&ntypeid=22&titleid=4547"><IMG
src="RINEX格式.files/replynow.gif" border=0></A> <A
title=引用回复该帖子
href="http://www.othermap.com/bbs/ft.asp?reply=1&ntypeid=22&titleid=4547"><IMG
src="RINEX格式.files/reply.gif" border=0></A> <IMG
alt=已设置保密 src="RINEX格式.files/ip.gif" border=0><BR>
<HR SIZE=1>
</TD></TR>
<TR>
<TD vAlign=top align=middle width="6%" rowSpan=3><IMG
src="RINEX格式.files/74.gif"></TD></TR>
<TR>
<TD class=p1 vAlign=top>附录<BR>第1节 RINEX格式<BR>RINEX是The
Receiver Independent Exchange
Format（与接收机无关的数据交换格式）的缩写，它是GPS测量领域中的一种广为使用的数据格式，绝大部分的数据处理软件均支持这种格式。<BR>下面是一份有关该格式的文挡：
<P></P>
<P>RINEX: The Receiver Independent Exchange Format Version
2<BR>*********************************************************</P>
<P>(Revision, April 1993)<BR>(Clarification December
1993)<BR>(Doppler Definition: January 1994)<BR>(PR
Clarification: October 1994)<BR>(Wlfact Clarification:
February 1995)<BR>(Event Time Frame Clarification: May
1996)<BR>(Minor errors in the examples A7/A8: May
1996)<BR>(Naming convention for compressed met files; January
1997)<BR>(Continuation line clarifications: April
1997)<BR>(GLONASS Extensions: April 1997)<BR>(Met sensor
description and position records: April 1997)<BR>(Wavelength
factor clarifications: April 1997)</P>
<P><BR>Werner Gurtner<BR>Astronomical Institute<BR>University
of Berne</P>
<P><BR>0. INTRODUCTION</P>
<P>0.1 First Revision</P>
<P>This paper is a revised version of the one published by W.
Gurtner and G.Mader in the CSTG GPS Bulletin of
September/October 1990. The main reasonfor a revision is the
new treatment of antispoofing data by the RINEXformat (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 asks 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).</P>
<P>* The slight modification (or rather the definition of a
bit in the Loss *<BR>* of Lock Indicator unused so far) to
flag AS data is so small a change *<BR>* that we decided to
NOT increase the version number! *</P>
<P>0.2 Later Revisions:</P>
<P>* URA Clarification (10-Dec-93):</P>
<P>The user range accuracy in the Navigation Message File did
not contain a definition of the units: There existed two ways
of interpretation:</P>
<P>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.</P>
<P>* GLONASS Extensions:</P>
<P>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.</P>
<P>The results of the call for comments have been worked into
this document.</P>
<P>A separate document (glonass.txt) summarizes just the
necessary extensions.</P>
<P>* A blank satellite identifier is allowed in pure GPS files
only</P>
<P>* Met sensor description and position records were added to
facilitate the precise use of met values.</P>
<P>* Description and examples for wavelength factors and their
temporary changes</P>
<P>(bit 1 of LLI) clarified.</P>
<P>In order to have all the available information about RINEX
in one place we also included parts of earlier papers and a
complete set of format definiton tables and examples.</P>
<P>1. THE PHILOSOPHY OF RINEX</P>
<P>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:</P>
<P>Most geodetic processing software for GPS data use a
well-defined set of observables:</P>
<P>- 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).</P>
<P>- 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.</P>
<P>- the observation time being the reading of the receiver
clock at the instant of validity of the carrier-phase and/or
the code measurements.</P>
<P>Usually the software assumes that the observation time is
valid for both the phase AND the code measurements, AND for
all satellites observed.<BR>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.</P>
<P>2. GENERAL FORMAT DESCRIPTION</P>
<P>Currently the format consists of four ASCII file
types:<BR>1. Observation Data File<BR>2. Navigation Message
File<BR>3. Meteorological Data File<BR>4. GLONASS Navigation
Message File<BR>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.</P>
<P>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 then be kept as short as possible. The maximum
record length is 80 bytes per record.</P>
<P>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.</P>
<P>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.</P>
<P>The format of the data records of the RINEX Version 1
Navigation Message file is identical to the former NGS
exchange format.</P>
<P>The actual format descriptions as well as examples are
given in the Tables at the end of the paper.</P>
<P>3. DEFINITION OF THE OBSERVABLES</P>
<P>GPS observables include three fundamental quantities that
need to be defined: Time, Phase, and Range.</P>
<P>TIME:</P>
<P>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).</P>
<P>PSEUDO-RANGE:</P>
<P>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):</P>
<P>PR = distance + c * (receiver clock offset - satellite
clock offset + other biases)</P>
<P>so that the pseudo-range reflects the actual behavior of
the receiver and satellite clocks. The pseudo-range is stored
in units of meters.</P>
<P>See also clarifications for pseudoranges in mixed
GPS/GLONASS files in chapter 8.1.</P>
<P>PHASE:</P>
<P>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 section.</P>
<P>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.</P>
<P>The observables are not corrected for external effects like
atmospheric refraction, satellite clock offsets, etc.</P>
<P>If the receiver or the converter software adjusts the
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -