AUSPOS - RINEX Data
Your GPS data should:
- Have been observed in 'static' mode
- Have a data span greater than one hour (preferably two). For best results we recommend six hours of data
- Be geodetic quality and DUAL FREQUENCY (carrier phase and code data)
- Be in RINEX format, and
- While not strictly enforced, the IGS file naming conventions are recommended
NOTE: You should NOT submit the broadcast navigation data.
Under IGS file naming conventions, RINEX files should take the following form:
|XXXX||is a four character site name|
|DDD||is the day of the year i.e. 001 to 365|
|S||is the session identifier i.e. 0 to 9, a to Z|
|YY||is a two digit year i.e. 00 for the year 2000|
The data can be standard uncompressed RINEX or it can be UNIX compressed, GZipped, Bzipped, Zipped and/or Hatanaka compressed RINEX.
The AUSPOS software will determine how the data is compressed based on the filename extension e.g.:
- *.Z for UNIX compression;
- *.YYd for Hatanaka compression;
- *.zip for ZIP compression;
- *.gz for gzip compression.
- *.bz for bzip compression.
NOTE: AUSPOS only accepts one file per zip file. Having more than one file in your zip file will cause the processing job to fail.
The data will be processed at a 30 second observation interval (the IGS standard). If your data hasn't been collected at a 30 second rate, the extra or non-matching observations will be ignored.
RINEX stands for "Receiver INdependent EXchange", and was an ASCII standard developed for the easy exchange of GPS data from different types of GPS receivers. More information on the RINEX format is available here .
Most GPS receiver manufacturers provide software to convert propriety data formats into RINEX, however, there are other options. The UNAVCO software TEQC is an excellent tool for format translation and data validation. TEQC is free software and can be downloaded from the Internet. Executable software is available for a wide variety of computer architectures - for more information see the UNAVCO TEQC software .
Topic contact: firstname.lastname@example.org Last updated: May 8, 2013