TEQC：GPS数据预处理与质量检查工具

需积分: 10 129 浏览量更新于2024-07-25 收藏 436KB PDF 举报

"TEQC操作手册是一份详细指导如何使用TEQC软件进行GPS观测数据预处理的文档。TEQC主要用于处理GPS观测文件，提供编辑、质量检查和格式转换等功能。该手册涵盖了从软件介绍到高级操作的多个方面，包括UNAVCO的支持与联系方式、数据类型、基本操作模式、操作系统与硬件需求、输入输出标准、语法概念、RINEX格式的处理与验证、RINEX头文件的编辑与提取、配置选项、质量检查模式、多文件处理、时间窗口操作、数据拼接、翻译功能、特殊翻译选项、波长因素处理、基本命令回顾、脚本使用以及TEQC与其他程序的区别。" 在TEQC操作手册中，用户将了解到： 1. 简介：TEQC的基本功能和用途，它是一个用于处理GPS观测数据的工具，能够对数据进行预处理，确保数据的质量和准确性。 2. 数据类型：手册详细解释了TEQC支持的各种GPS数据类型，以便用户知道如何处理不同来源的数据。 3. 基本操作模式：这部分介绍了如何启动和操作TEQC，包括标准输入、输出和错误信息的管理。 4. 操作系统和硬件要求：用户可以了解TEQC在哪些操作系统上运行，以及对硬件的最低要求。 5. RINEX（Receiver Independent Exchange Format）处理：TEQC可以将原始GPS观测数据转换成RINEX格式，同时也可以验证RINEX文件的正确性。 6. 配置选项和命令行选项：这部分详细列出了可用的配置参数和命令行选项，帮助用户自定义处理过程。 7. 质量检查模式：TEQC提供了内置的质量检查功能，允许用户检测并修复数据中的问题。 8. 多文件处理：对于包含逗号的文件名或需要处理多个文件的情况，手册提供了相应处理方法。 9. 时间窗口操作：用户可以指定特定的时间段来处理数据，这对于数据分析非常有用。 10. 数据拼接：TEQC能将不同时间段的观测数据拼接成一个连续的文件。 11. 翻译功能：TEQC不仅转换数据格式，还能处理数据内容，比如波长因素的调整。 12. 脚本使用：手册还教授如何将TEQC集成到批处理脚本中，以自动化处理大量数据。通过这份手册，用户可以全面掌握TEQC的各项功能，从而有效地管理和优化GPS观测数据。无论是初学者还是经验丰富的专业人员，都能从中获得宝贵的指导。

... | teqc {options}

The file or files listed at the end of the command line, or stdin, are the targets which are to be

processed for each execution of teqc. This is mentioned since other file names may be

present in the options, but any files listed in the options are part of the processing configuration

and are not considered to be targets of the processing.

Even executing just

teqc

(i.e., no targets present) is allowed; this returns teqc's best guess as to which GPS week it

currently is based on the CPU's clock (but how good this guess is depends on how well the

CPU's time is set).

There is a mnemonic governing the use of - and + preceding each option:

leading -:

indicates intent to input something (besides stdin or target file list),

or indicates intent to turn off some option

leading +:

indicates intent to output something, (besides stdout and/or stderr),

or indicates intent to turn on some option

For some options, a leading - and + do the same thing. To get help, for example,

teqc -help

and

teqc +help

both dump an extensive usage to stderr. (Following the mnemonic, only the +help should give

help, but why further confuse the issue when the user is requesting for help? For this reason,

both work here.) Also, the

RINEX header editing option flags work the same way: e.g., -O.mo

is the same as +O.mo. You can either think of -O.mo as inputting some header information

(the monument name), or using +O.mo as forcing what you want the output header

information to be.

In order to try to detect possible command line input errors, target file names at the end of the

command line starting with the character '-' or '+' are currently disallowed. Anything starting

with the characters '-' or '+' is always assumed to be a command line option.

Sometimes, especially with new features (e.g., new translators) as they are being added and

debugged, you may be inundated with warning messages going to stderr. Most of these can

usually be suppressed by including the -warn option:

teqc -warn {rest of command}

Using teqc for RINEX Formatting & RINEX Format Verification

Section 8.

Suppose you have three RINEX files (using the Berne-recommended naming conventions):

fbar0010.97o, fbar0010.97n, and fbar0010.97m being your

OBS, NAV, and MET filenames

respectively. Let us suppose that you first wish to verify that your fbar* files can be interpreted

as RINEX version 2.XX format compliant, i.e. that their format is such that they have all the bits

and pieces in them to make them look like a RINEX file (but not that the information in them is

necessarily valid). One way of doing this is to execute:

teqc fbar0010.97o

teqc fbar0010.97n

teqc fbar0010.97m

What you see being dumped to the screen is a re-processed RINEX version 2.XX format. All

information originally in the target file will be retained in the output version (--and if its not,

there's a bug, so please

report this).

Or you could execute:

teqc fbar0010.97o > temp0010.97o

teqc fbar0010.97n > temp0010.97n

teqc fbar0010.97m > temp0010.97m

in which case the re-processed RINEX files are redirected (stdout) and saved as a set of

temp* files.

After doing the above three commands, it might also be instructive to do something like:

diff fbar0010.97o temp0010.97o | more

to see what some of the differences between the original target file and the re-processed file

might be. If the original file were produced by teqc, you shouldn't see any differences (--and,

again, if you do, there's a bug, so please

report this).

If, in fact, there is some format problem with any of the above input RINEX files fbar0010.97*,

teqc will output stdout (either to the screen as in the first set of examples, or redirected to files

as in the second set of examples) until the problem is encountered, at which point it will report

the problem using stderr and terminate. teqc makes few guesses about what a RINEX file is

supposed to be; if a file has a problem, a human or some other program must be used to fix it

before teqc will proceed further.

Now suppose that you have a list of RINEX files that you wish to check for RINEX version 2.XX

format compliancy, but don't want to save any re-processed stdout. There are several ways to

do this (e.g., in UNIX):

teqc fbar0010.97o > /dev/null

teqc fbar0010.97n > /dev/null

teqc fbar0010.97m > /dev/null

or, using the command line option +v (any shell):

teqc +v fbar0010.97o

teqc +v fbar0010.97n

teqc +v fbar0010.97m

or:

teqc +v fbar0010.97o fbar0010.97n fbar0010.97m

or (UNIX shell regular expressions):

teqc +v fbar0010.97[m-o]

or even (e.g., if using ksh):

teqc +v `ls fbar0010.97*`

Essentially the +v option does three things:

剩余48页未读，继续阅读

成功之母

粉丝: 0

TEQC：GPS数据预处理与质量检查工具

TEQC使用手册(中文版)

teqc软件及其说明书

Windows 版TEQC软件及使用说明书

TEQC操作手册.docx

TEQC软件手册：GPS/GLONASS数据预处理指南

GPS数据预处理软件TEQC操作教程

TEQC.rar_teqc_teqc官方网站_斯托利gps

TEQC.rar_TEQC教程_site:www.pudn.com_teqc

GPS数据预处理 teqc+gfzrnx

GPS卫星数据分析工具teqc（含中英文说明）

最新资源