08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

7.7 Special Applications<br />

may be imported into the <strong>Bernese</strong> environment. Program QLRINEXO converts QL-files into<br />

RINEX format. The RINEX files may then be converted into <strong>Bernese</strong> binary format using<br />

RXOBV3.<br />

QLRINEXO is not available through the menu but may be executed using the RUN<strong>GPS</strong> command<br />

(see Section 18.8). The program reads QL-files and writes observation and meteorological<br />

RINEX files for each ILRS station present in the QL-file. The ILRS station names<br />

read from the QL-file may be renamed. Section TYPE 001: RENAMING OF STATIONS of the<br />

station information file (description in Section 22.8.3) is used for renaming. The station<br />

information file has to be specified in the input field “Station information”. The naming of the<br />

output files follows the usual convention: ccccssss.yyO and ccccssss.yyM for RINEX observation<br />

and RINEX meteo files, respectively. The 4-character station abbreviation cccc<br />

is taken from the abbreviation table (description in Section 22.8.2). The session ssss is<br />

specified in option “Session ID used for RINEX observation file names”, the year yy is specified<br />

in option “Year ID used for RINEX observation file names”. The station needs to be listed in the<br />

abbreviation table. Otherwise the writing of the output files is skipped for the corresponding<br />

station.<br />

The format of the RINEX file holding SLR observations is not an official format, but it<br />

closely follows the RINEX conventions. The observation types “R1” and “R2” indicate range<br />

measurements, which are not provided by the RINEX format definition. The observation<br />

records written to the RINEX file are the observed SLR ranges, but adapted to consider<br />

only the one-way light travel time. Thus, the observation epoch refers to the time of signal<br />

reception (as for <strong>GNSS</strong> measurements), and not to the time of signal reflection. The observation<br />

epochs in the RINEX file refer to <strong>GPS</strong> time. If epochs given in the QL-file refer to<br />

UTC, they have to be converted from UTC to <strong>GPS</strong> time by applying leap seconds. The file<br />

${X}/GEN/<strong>GPS</strong>UTC. containing the list of leap seconds (see Section 22.4.7) is available at the<br />

ftp account of AIUB (http://www.aiub.unibe.ch/download/BSWUSER50/GEN/<strong>GPS</strong>UTC.).<br />

The RINEX observation file contains only SLR observations for selected satellites. To specify<br />

these satellites, set the option “LIST OF SATELLITES” accordingly, by listing the satellite<br />

numbers. The satellite numbering corresponds to the numbering in the satellite information<br />

file (e.g., ${X}/GEN/SATELLLIT.I05, description in Section 22.4.5).<br />

Import from RINEX to <strong>Bernese</strong> Files<br />

The RINEX range observation files may be converted to <strong>Bernese</strong> observation files using program<br />

RXOBV3 (see Section 4.2.3 for details). Enable “Range” in option “Measurement types<br />

to save”. <strong>Bernese</strong> code binary observation and header files 2 are created. The antenna and<br />

receiver names read from RINEX are both SLR. You may rename these names using section<br />

TYPE 002: STATION INFORMATION of the station information file. In the same section of<br />

this file station eccenter vectors may be specified. Alternatively an eccenter file (see Section<br />

22.8.6) may be specified for the processing programs. For technical reasons the “antenna<br />

name” (SLR) has to be included in the phase center eccentricity file (see Section 22.4.4).<br />

Offsets and phase pattern should be set to zero.<br />

2 Specify the same extensions as for <strong>Bernese</strong> code observation files in “DATA STRUCTURE 4: Campaign<br />

Data, Observation Files”. Programs which do not have separate entry fields for range observations use<br />

path and extensions specified for code observation files instead.<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 161

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!