Or have some numerical value if a numerical value (even if it is zero) is expected,īut these other header lines must be present with or without non-blank information. The rest of theįields in other header records can be blank if a descriptor string is expected The number and types of observations must be specified on the # / TYPES OF OBSERV record line,Īnd default values for the L1 and L2 wavelength factors must be given. Satellite system = ' ', 'G', 'R', 'S', 'T', or 'M') must be present in the first line, Where valid information (i.e., format version = 1, 2, or 2.XX file type = 'O' RINEX VERSION / TYPE (must be first line)ĮND OF HEADER (must be last line of header for version 2.XX) Is read and recognized and converted to RINEX VERSION / TYPE on RINEX output).Įach RINEX OBS file must have a header with header lines (startingĪt the 61st character in the line) that end with: Lines are recognized and converted to uppercase if output (e.g. Also, lowercase versions of the following header RINEX version 1 files can be read with teqc and are converted to RINEX (Note: There are no current plans for support of RINEX 3.00.) The non-optional header records specified in the RINEX version 2.10 document.
Independent Exchange Format Version 2" available from the University of BerneĪ minimum set of header records must be present for each file. In order to have a valid RINEX version 2.XX file, theįile must conform to the specifications in the document "RINEX: The Receiver RINEX version 2.XX (2.10) files are the default type of files that teqc is expecting
Of contact at UNAVCO for other questions, unresolved problems, or possible bug reports. To send a message to the teqc email forum: To subscribe or unsubscribe to the teqc email forum, use the above URL. You can search the teqc emails, or list the teqc emails either by date or by thread (email subject).
#Rinex converter leica geo office archive
There is also a teqc Email Forum and email archive in place.A listing of release notes for each official release, covering details which might not be in this tutorial.The teqc development & release log (including bug fixes for the next release).FAQs ("frequently asked questions") on teqc.If your primary interest is qc-ing RINEX or native binary data, goĭirectly to the section on the qc mode (Section 11) of teqc. If your primary interest is translating native binary formats to RINEX, goĭirectly to the sections on translation ( Section 15ĭirectly to the section on metadata editing/extraction (Section 9), or RINEX formatting (Section 8), or windowing (cutting) (Section 13)/ splicing (Section 14) operations. To a RINEX version 2.XX (specifically 2.10) file. Though an attempt to edit a RINEX version 1 file will result in the automatic conversion Shorthand for the three basic kinds of RINEX formats is used throughoutĪlso, teqc currently handles RINEX version 1 and 2 files (through to version 2.10), Is the RINEX format, either as input, or output, or both. The most common type of data format that will probably be used by most users The capabilities of teqc extend beyond using just RINEX files, This document describes and serves as a tutorial for the main features Differences Between teqc's qc Mode and Original UNAVCO QC Using teqc in Scripts: Substitution for Batch Mode Wavelength Factors: What teqc Does With Them Special Translator Considerations and Options Using teqc with Multiple File Input or File Names Including a, (comma) Using teqc for Quality Checking (qc) Mode Configuration Options and Command Line Options Using teqc for RINEX Header Editing & Extraction Introduction to Configuration Options and Files and the teqc Option Hierarchy
#Rinex converter leica geo office verification
Using teqc for RINEX Formatting & RINEX Format Verification Standard Input, Standard Output, and Standard Error UNAVCO World Wide Web Support & Contact