RINEX 3.04更新概述：新增信号与改进内容

3星 · 超过75%的资源需积分: 41 110 浏览量更新于2024-07-17 2 收藏 1.69MB PDF 举报

RINEX 3.04是Receiver Independent Exchange Format（接收机独立交换格式）的最新版本，由国际GNSS服务（IGS）的RINEX工作小组和无线电技术委员会海上服务特别委员会104（RTCM-SC104）于2018年11月23日发布。此更新旨在增强和标准化全球导航卫星系统（GNSS）数据交换，以便于不同接收设备间的互操作性。 1. **新增信号支持**: - 在RINEX 3.04中，新增了GLONASS、QZSS II（增强版）和BeiDou III星座的信号表（见Table 5, 8, 和 9），扩展了信号覆盖范围。这些变化反映了全球定位系统技术的发展和可用性。 2. **信号描述与对比**: - 新增了Section 9.12，专门介绍GLONASS、QZSS II和BeiDou III的新信号，并区分了QZSS I和QZSS II之间的差异，帮助用户理解不同信号的特性和用途。 3. **信号代码表**: - 表A23得到了更新，同时在Appendix Table A2 SYS/#/OBS TYPES中添加了GLONASS、QZSS II和BeiDou III的新信号代码，以便接收器能准确识别和处理这些信号。 4. **时间系统澄清**: - 修改了Appendix Table A5 TIME SYSTEM CORR部分，以更清晰地定义GNSS时间系统以及UTC（协调世界时）的差值，增强了时间同步的准确性。 5. **文本改进**: - 文件中包含了许多小的纠正和文字改进，这些改动可能涉及格式、术语或描述的细微调整，以提高文档的准确性和易读性。具体更改在RINEX 3.04修订历史部分列出。 RINEX 3.04的核心目标是保持格式的一致性和通用性，确保接收机能够在不同GNSS系统间无缝切换，减少数据处理过程中的误解和误差。随着全球卫星系统的持续发展和更新，RINEX协议也会相应进化，以适应新的技术和应用场景。对于GNSS研究人员、工程师和用户来说，掌握RINEX 3.04的这些新特性至关重要，这将有助于他们优化接收和分析数据，提高定位精度和应用效率。

RINEX Version 3.04

RINEX 3.04.IGS.RTCM.doc 2018-11-23

2. GENERAL FORMAT DESCRIPTION

The RINEX version 3.XX format consists of three ASCII file types:

1. Observation data file

2. Navigation message file

3. Meteorological data file

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 minimum space requirements independent from the number of

different observation types of a specific receiver or satellite system by indicating in the header the

types of observations to be stored for this receiver and the satellite systems having been observed.

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. There is no maximum record length

limitation for the observation records.

Each Observation file and each Meteorological Data file basically contain the data from one site

and one session. Starting with Version 2 RINEX also allows including observation data from more

than one site subsequently occupied by a roving receiver in rapid static or kinematic applications.

Although Version 2 and higher allow insertion of certain header records into the data section, it is

not recommended to concatenate data from 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 have to be exchanged, it would not be economical to include

the identical satellite navigation 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 was identical to

the former NGS exchange format. RINEX Version 3 navigation message files may contain

navigation messages of more than one satellite system (GPS, GLONASS, Galileo, Quasi Zenith

Satellite System (QZSS), BeiDou System (BDS), Indian Regional Navigation Satellite System

(IRNSS) and SBAS).

The actual format descriptions as well as examples are given in the Appendix Tables at the end of

the document.

RINEX Version 3.04

RINEX 3.04.IGS.RTCM.doc 2018-11-23

3. BASIC DEFINITIONS

GNSS observables include three fundamental quantities that need to be defined: Time, Phase, and

Range.

3.1 Time

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. For single-

system data files, it is by default expressed in the time system of the respective satellite system.

For mixed files, the actual time system used must be indicated in the TIME OF FIRST OBS header

record.

3.2 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):

PR = distance + c * (receiver clock offset –satellite clock offset + other biases)

so that the pseudo-range reflects the actual behaviour of the receiver and satellite clocks. The

pseudo-range is stored in units of meters.

See also clarifications for pseudoranges in mixed GPS/GLONASS/Galileo/QZSS/BDS files in

chapter 8.2.

3.3 Phase

The phase is the carrier-phase measured in whole cycles. The half-cycles measured by squaring-

type receivers must be converted to whole cycles and flagged by the respective observation code

(see Table 4 and Section 5.4, GPS only).

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 observables are not corrected for external effects such as: atmospheric refraction, satellite

clock offsets, etc.

If necessary, phase observations are corrected for phase shifts needed to guarantee consistency

between phases of the same frequency and satellite system based on different signal channels (See

Section 9.1 and Appendix A23).

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:

RINEX Version 3.04

RINEX 3.04.IGS.RTCM.doc 2018-11-23

All elements of the main body of the file name must contain capital ASCII letters or numbers

and all elements are fixed length and are separated by an underscore “_”.The file type and

compression fields (extension) use a period “.” as a separator and must be ASCII characters and

lower case. Fields must be padded with zeros to fill the field width. The file compression field is

optional. See Appendix A1 for a detailed description of the RINEX 3.02 (and subsequent

versions) file naming convention. Table 2 below lists sample file names for GNSS observation

and navigation files.

File Name

Comments

ALGO00CAN_R_20121601000_01H_01S_MO.rnx

Mixed RINEX GNSS observation file

containing 1 hour of data, with an

observation every second

ALGO00CAN_R_20121601000_15M_01S_GO.rnx

GPS RINEX observation file

containing 15 minutes of data, with an

observation every second

ALGO00CAN_R_20121601000_01H_05Z_MO.rnx

Mixed RINEX GNSS observation file

containing 1 hour of data, with 5

observations per second

ALGO00CAN_R_20121601000_01D_30S_GO.rnx

GPS RINEX observation file

containing 1 day of data, with an

observation every 30 seconds

ALGO00CAN_R_20121601000_01D_30S_MO.rnx

Mixed RINEX GNSS observation file

containing 1 day of data, with an

observation every 30 seconds

ALGO00CAN_R_20121600000_01D_GN.rnx

RINEX GPS navigation file, containing

one day’s data

ALGO00CAN_R_20121600000_01D_RN.rnx

RINEX GLONASS navigation file,

containing one day’s data

ALGO00CAN_R_20121600000_01D_MN.rnx

RINEX mixed navigation file, containing

one day’s data

Table 2: Description of Filename Parameters

In order to further reduce the size of observation files, Yuki Hatanaka developed a compression

scheme that takes advantage of the structure of the RINEX observation data by forming higher-

order differences in time between observations of the same type and satellite. This compressed file

is also an ASCII file that is subsequently compressed again using standard compression programs.

More information on the Hatanaka compression scheme can be found in:

http://terras.gsi.go.jp/ja/crx2rnx.html

 IGSMails 1525,1686,1726,1763,1785,4967,4969,4975

剩余99页未读，继续阅读

yuanye6666

粉丝: 4
资源: 9

RINEX 3.04更新概述：新增信号与改进内容

Rinex3.04协议标准.pdf

RINEX_格式中文详解

天宝convert to rinex

读取gps观测数据rinex3.04文件的matlab编程,读取GPS观测数据O文件的matlab编程

matlab读取3.04版本的rinex观测文件并绘制所有GPS卫星的信噪比

C++读取3.04版本的rinex观测文件并绘制所有GPS卫星的信噪比

C++读取3.04版本的rinex观测文件并计算单频点观测数据完整率和单系统观测数据完整率

设计Rinex O文件和Rinex N文件读取类，实现对Rinex文件内容的读取和显示.

rinex文件3转2

rinex 3.05 中文版本

最新资源